Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
31
Installation and Upgrades / Duplicate Services, Unable to Remove
« on: July 17, 2010, 08:14:32 am »
eBox 1.4.8
I've been using eBox since 1.0 on this same machine through beta 1.1, version 1.2, beta 1.3, and version 1.4 updated fully. In my Services area, I recently noticed a lot of duplicates. Is there a way to run a clean-up utility or should I do it manually through editing the eBox config files?
Picture Evidence: http://badmarkup.com/ebox/duplicate-services.png
And I'm unable to say SSH is internal.
I've been using eBox since 1.0 on this same machine through beta 1.1, version 1.2, beta 1.3, and version 1.4 updated fully. In my Services area, I recently noticed a lot of duplicates. Is there a way to run a clean-up utility or should I do it manually through editing the eBox config files?
Picture Evidence: http://badmarkup.com/ebox/duplicate-services.png
And I'm unable to say SSH is internal.
32
Installation and Upgrades / eBox-to-eBox tunnel requiring optional RIP password
« on: July 02, 2010, 04:34:35 am »
eBox 1.4.8
:: PROBLEM ::
Where it says Allow eBox-to eBox-tunnels, it also says the password field is optional but it's not. I had this same issue in a much older version of eBox, and it doesn't look like it was fixed yet.
:: MISC ::
My other complaint is the error text is spelled incorrectly.
:: PROBLEM ::
Where it says Allow eBox-to eBox-tunnels, it also says the password field is optional but it's not. I had this same issue in a much older version of eBox, and it doesn't look like it was fixed yet.
:: MISC ::
My other complaint is the error text is spelled incorrectly.
33
Installation and Upgrades / eBox package dependency list
« on: June 30, 2010, 04:44:57 pm »
I was hoping I could find a list of each eBox package and the dependencies therein such that the DHCP server uses dhcpd3 as the backbone and the DNS server uses bind9. If I can gather all of this information, I'd like to do a usability report with another similar distribution with a completely different audience. I wanna see where the differences lie and then write back to everyone of my findings. Before I can do that though, I need to have someone help me develop a list of what I'd need to download on the other machine. I have configured eBox so many times but I've only one configured this other platform. I even already have two VMs setup already designed for me to emulate the setup of my own two current eBox machines so that I may make a reasonable comparison between the two platforms.
34
Installation and Upgrades / Migrating eBox to ARM from x86
« on: June 30, 2010, 01:18:48 am »
Since Ubuntu has an ARM version, I'd assume most if not all of the eBox software is already written for ARM. If I run Ubuntu ARM in Qemu or something and do apt-get ebox^* or add the eBox repo or however I'm supposed to do it, will it work? Has anyone tried this? I want to transition to the Guruplug or some other Marvell Kirkwood chip machine and while there was discussion about this before, there was no information on a configuration change. I am curious if I can just up an' import my current eBox config file into eBox on ARM and just switch out some cables and change the MAC addresses to have my network working as it should.
Has anyone tried or would like to try this? I might do it myself, but I'm not quite familiar with Qemu nor do I know anything about Ubuntu ARM if I have to compile it myself or not.
Has anyone tried or would like to try this? I might do it myself, but I'm not quite familiar with Qemu nor do I know anything about Ubuntu ARM if I have to compile it myself or not.
35
Installation and Upgrades / eBox File Locations
« on: April 26, 2010, 01:54:01 pm »
I'm starting this thread because I wanted all eBox users to be able to find a way to know what files eBox uses, which files do what, and where they're stored.
As people post where files are located and what they do, I'll update this post and give thanks to those who contributed.
/etc/ebox
Some simple configuration files.
These configuration files do not control eBox or most any of its functions; as such, most users will never need to make changes in these files.
/var/lib/ebox
Linux "ebox" user home directory.
A bunch or stuff used by eBox is stored here.
/var/lib/ebox-usercorner
Linux "ebox" user home directory.
A bunch or stuff used by eBox is stored here.
/var/lib/ebox/gconf/ebox
In the event changes need to be reverted in eBox, this entire directory or parts of it could be restored to revert back to older configuration settings.
%gconf.xml
Contains information for eBox's configuration settings such as those for statically-assigned IPs to machines by MAC address on the DHCP page.
Contributors
Javier Amor Garcia - eBox Staff
As people post where files are located and what they do, I'll update this post and give thanks to those who contributed.
/etc/ebox
Some simple configuration files.
These configuration files do not control eBox or most any of its functions; as such, most users will never need to make changes in these files.
/var/lib/ebox
Linux "ebox" user home directory.
A bunch or stuff used by eBox is stored here.
/var/lib/ebox-usercorner
Linux "ebox" user home directory.
A bunch or stuff used by eBox is stored here.
/var/lib/ebox/gconf/ebox
In the event changes need to be reverted in eBox, this entire directory or parts of it could be restored to revert back to older configuration settings.
%gconf.xml
Contains information for eBox's configuration settings such as those for statically-assigned IPs to machines by MAC address on the DHCP page.
Contributors
Javier Amor Garcia - eBox Staff
36
Installation and Upgrades / Found a possible eBox-mail bug in my logs
« on: April 23, 2010, 12:31:23 pm »
Apr 23 05:27:49 main postfix/trivial-rewrite[7115]: warning: dict_ldap_lookup: valiases: Search base 'ou=mailalias,ou=postfix, dc=grubber' not found: 32: No such object
I don't think the space after the comma and before dc= should be there. Is that an internal eBox issue? It might be why I haven't been able to send mail out of this machine since February.
I don't think the space after the comma and before dc= should be there. Is that an internal eBox issue? It might be why I haven't been able to send mail out of this machine since February.
37
Installation and Upgrades / Moving an eBox image around to other rigs
« on: April 08, 2010, 10:33:42 am »
Let's say I dd an image of my current eBox rig onto another machine. Will I be able to fix around things in eBox 1.5/2.0 if the Ethernet adapter names change? I used to have 4 Ethernet adapters in my rig for various reasons and now only have two. The problem is, they are labeled eth0 and eth3 in Linux. Is it possible those numbers would change to eth4 and eth5 should I boot onto a separate set of hardware and are those numbers changeable? I know eBox would have a hayday if it tried to bot up and eth0 and eth3 were missing.
Maybe eBox needs to be hardware-aware in some instances so you can just say the new eth4 is the old eth0 and the new eth5 is the old eth3. In fact, it would be easier on pretty much anyone if eBox had the ability to rename interfaces too so the eth3 I have can be eth1 and not be difficult for any sysadmin to figure out what's going on with missing Ethernet adapters or holes in the interface names.
I would personally like to move my server to a different set of hardware but don't have a good enough knowledge of eBox or Linux to do this without screwing up how eBox works.
Maybe eBox needs to be hardware-aware in some instances so you can just say the new eth4 is the old eth0 and the new eth5 is the old eth3. In fact, it would be easier on pretty much anyone if eBox had the ability to rename interfaces too so the eth3 I have can be eth1 and not be difficult for any sysadmin to figure out what's going on with missing Ethernet adapters or holes in the interface names.
I would personally like to move my server to a different set of hardware but don't have a good enough knowledge of eBox or Linux to do this without screwing up how eBox works.
38
Installation and Upgrades / eBox to eBox VPN password not optional (needs correcting)
« on: March 27, 2010, 12:14:23 pm »
The web interface states the eBox to eBox VPN password is optional whereas it is not because it will not allow you to enable the option without a password.
A question, it says a RIP password is needed. Does it use RIP as in the very insecure routing protocol instead of something like OSPF or IS IS? What about RIPv2 at least? Not much of an upgrade though.
A question, it says a RIP password is needed. Does it use RIP as in the very insecure routing protocol instead of something like OSPF or IS IS? What about RIPv2 at least? Not much of an upgrade though.
39
Installation and Upgrades / Getting eBox to work on ARM
« on: March 05, 2010, 05:54:54 am »
http://www.globalscaletechnologies.com/p-31-guruplug-server-standard.aspx Does anyone know if it would be at all possible to install eBox into something like this provided an ARM-compiled Ubuntu Server? Would it even work reasonably? I think it would be fantastic to use for so many reasons.
40
Installation and Upgrades / Non-WINS-server eBoxes cannot access by hostnames or configure WINS server
« on: February 21, 2010, 04:29:11 am »
For all eBox client machines, ones that are not the WINS server, they are unable to ping by NetBIOS hostname and have no way to add a WINS server to the Samba smb configuration.
41
Installation and Upgrades / Backup VPN'd machines using BackupPC
« on: February 13, 2010, 09:25:16 pm »
While VPN client machines can ping inside of the advertised networks, you might've noticed you cannot ping those same VPN clients from inside of the network not matter what you do. The only machine which can ping those VPN clients inside your network is the VPN server/gateway.
I found a way to backup machines online using this trick. Make a virtual adapter in eBox on your VPN server machine. Then go to the firewall and forward all requests on that IP to the VPN client's IP. Now you can backup machines over a VPN. Another method is just forwarding a specific port or set of ports.
I found a way to backup machines online using this trick. Make a virtual adapter in eBox on your VPN server machine. Then go to the firewall and forward all requests on that IP to the VPN client's IP. Now you can backup machines over a VPN. Another method is just forwarding a specific port or set of ports.
42
Installation and Upgrades / Active Directory access via FreeNAS almost works
« on: February 10, 2010, 04:17:36 pm »
I finally got Active Directory working in FreeNAS. I figured out you can put an IP address where it asks for the hostname. It's one less DNS lookup which is fine by me.
http://badmarkup.com/ebox/freenas/ebox-active-directory-working-in-freenas.png
Now while Active Directory works, Samba doesn't seem to understand this as you can see by this error from these settings: http://badmarkup.com/ebox/freenas/samba-settings-in-freenas.png. Maybe I'm doing something wrong, but at least the Active Directory users show up. If you're wondering about LDAP, it seems impossible at the moment as I've not seen anyone able to get it to work.
http://badmarkup.com/ebox/freenas/ebox-active-directory-working-in-freenas.png
Code: [Select]
MS Active Directory informations
Results for net rpc testjoin:
Password:
Join to 'OCTEN' is OK
Ping winbindd to see if it is alive:
Ping to winbindd succeeded on fd 4
Check shared secret:
checking the trust secret via RPC calls succeeded
List of imported users
Blah
Fake
Name
Here
Now while Active Directory works, Samba doesn't seem to understand this as you can see by this error from these settings: http://badmarkup.com/ebox/freenas/samba-settings-in-freenas.png. Maybe I'm doing something wrong, but at least the Active Directory users show up. If you're wondering about LDAP, it seems impossible at the moment as I've not seen anyone able to get it to work.
43
Installation and Upgrades / Ping NetBIOS hostnames (not completely fool-proof)
« on: February 07, 2010, 03:50:10 pm »
While this only worked on three of the four machines I tried, it's better than nothing. The machines I tired this on were, two are eBox 1.4, one Ubuntu Karmic Server, and FreeNAS 0.71 on FreeBSD 7.2.
DONE! It should immediately start working. Funny thing is, the machine it doesn't work in for me is the only machine I actually need it working in bleh
.
In FreeBSD, /etc/nsswitch.conf is located in /var/etc/nsswitch.conf <- correct me if I'm wrong, the machine's offline at the moment.
Code: [Select]
apt-get install winbind (eBox 1.4 has its own version)
nano /etc/nsswitch.conf
hosts: files dns => hosts: files dns wins
winbindd
DONE! It should immediately start working. Funny thing is, the machine it doesn't work in for me is the only machine I actually need it working in bleh
.In FreeBSD, /etc/nsswitch.conf is located in /var/etc/nsswitch.conf <- correct me if I'm wrong, the machine's offline at the moment.
44
Installation and Upgrades / Weird ping reports when pinging machines on an eBox network
« on: February 07, 2010, 11:18:22 am »
Both grubber and main are eBox servers. Soyver and grubber are apparently setup in DNS somehow. I have the DHCP server setup to do DDNS for octen in this subnet, but not all of the machine are apparently on octen. Colissio is the local machine I was pinging from, kevin-top was offline. Notice how when I ping grubber, it is all caps. I wonder if that is a mistake somehow. 1.1.1.1 (main) is the PDC as well as the WINS and DNS and everything else; although, it doesn't even respond as if it's part of the domain octen.
ping grubber
Pinging GRUBBER.octen [1.1.1.11] with 32 bytes of data:
Reply from 1.1.1.11: bytes=32 time=1ms TTL=64
Reply from 1.1.1.11: bytes=32 time=1ms TTL=64
Ping statistics for 1.1.1.11:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
ping soyver
Pinging soyver.octen [1.1.3.2] with 32 bytes of data:
Reply from 1.1.3.2: bytes=32 time=2ms TTL=128
Reply from 1.1.3.2: bytes=32 time=1ms TTL=128
Reply from 1.1.3.2: bytes=32 time<1ms TTL=128
Reply from 1.1.3.2: bytes=32 time=1ms TTL=128
Ping statistics for 1.1.3.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 2ms, Average = 1ms
ping main
Pinging main [1.1.1.1] with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=1ms TTL=64
Reply from 1.1.1.1: bytes=32 time=1ms TTL=64
Reply from 1.1.1.1: bytes=32 time<1ms TTL=64
Reply from 1.1.1.1: bytes=32 time<1ms TTL=64
Ping statistics for 1.1.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
ping colissio
Pinging Colissio [fe80::c184:c233:950c:e9ad%9] from fe80::c184:c233:950c:e9ad%9
with 32 bytes of data:
Reply from fe80::c184:c233:950c:e9ad%9: time<1ms
Reply from fe80::c184:c233:950c:e9ad%9: time<1ms
Reply from fe80::c184:c233:950c:e9ad%9: time<1ms
Reply from fe80::c184:c233:950c:e9ad%9: time<1ms
Ping statistics for fe80::c184:c233:950c:e9ad%9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
ping kevin-top
Pinging kevin-top [1.1.4.1] with 32 bytes of data:
Reply from 1.1.3.1: Destination host unreachable.
Reply from 1.1.3.1: Destination host unreachable.
Ping statistics for 1.1.4.1:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss)
ping grubber
Pinging GRUBBER.octen [1.1.1.11] with 32 bytes of data:
Reply from 1.1.1.11: bytes=32 time=1ms TTL=64
Reply from 1.1.1.11: bytes=32 time=1ms TTL=64
Ping statistics for 1.1.1.11:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
ping soyver
Pinging soyver.octen [1.1.3.2] with 32 bytes of data:
Reply from 1.1.3.2: bytes=32 time=2ms TTL=128
Reply from 1.1.3.2: bytes=32 time=1ms TTL=128
Reply from 1.1.3.2: bytes=32 time<1ms TTL=128
Reply from 1.1.3.2: bytes=32 time=1ms TTL=128
Ping statistics for 1.1.3.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 2ms, Average = 1ms
ping main
Pinging main [1.1.1.1] with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=1ms TTL=64
Reply from 1.1.1.1: bytes=32 time=1ms TTL=64
Reply from 1.1.1.1: bytes=32 time<1ms TTL=64
Reply from 1.1.1.1: bytes=32 time<1ms TTL=64
Ping statistics for 1.1.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
ping colissio
Pinging Colissio [fe80::c184:c233:950c:e9ad%9] from fe80::c184:c233:950c:e9ad%9
with 32 bytes of data:
Reply from fe80::c184:c233:950c:e9ad%9: time<1ms
Reply from fe80::c184:c233:950c:e9ad%9: time<1ms
Reply from fe80::c184:c233:950c:e9ad%9: time<1ms
Reply from fe80::c184:c233:950c:e9ad%9: time<1ms
Ping statistics for fe80::c184:c233:950c:e9ad%9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
ping kevin-top
Pinging kevin-top [1.1.4.1] with 32 bytes of data:
Reply from 1.1.3.1: Destination host unreachable.
Reply from 1.1.3.1: Destination host unreachable.
Ping statistics for 1.1.4.1:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss)
45
Installation and Upgrades / [SOLVED] Samba access cumbersome and slow as if on satellite connection
« on: February 06, 2010, 04:17:08 pm »
Samba in all eBox except 1.4 used to be extremely fast and useful. Now, when I try to access a Samba share (on the eBox), it's extremely cumbersome and slow. Sometimes in Windows, I do \\hostname, and it won't work even though it can see the hostname in the Network area, but if I do \\IP_ADDRESS, then it works but it is still very slow when trying to go through files sometimes taking up to 5 seconds or more. I've even had it just cut off the connection.