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.

Topics - centaur5

Pages: 1 [2]
Installation and Upgrades / Ebox 1.3.6 doesn't save default gateway
« on: December 08, 2009, 06:30:24 pm »
I have 2 internet connections with both gateways configured under Ebox 1.3.6.  Whenever I reboot the server Ebox doesn't save the default gateway and changes it to my other internet connection that I don't want as default.  I'm running 1.3.6 on Jaunty.

Installation and Upgrades / VPN has to reconnect every 2 minutes
« on: November 30, 2009, 05:03:28 am »
I setup my VPN and it works perfectly (thank you very much for making it so easy to do).  However, I found that in the OpenVPN log the client is reconnecting every 2 minutes almost exactly to the second.  I tried it from 2 different clients each one having different internet connections.  Any ideas what would be causing this?  There isn't much work that can be done in 2 minutes (actually traffic starts to time out sooner cause the client starts the process of killing and reconnecting).  Also traffic is very slow while the connection is working.  Hardware is basically idle and internet connections are 6 down 3 up.

Installation and Upgrades / Ebox 1.3.6 bug with virtual hosts
« on: October 21, 2009, 06:10:31 am »
I setup 5 different virtual hosts using 1.3.3 and this past weekend updated to 1.3.6 and tried to create a virtual host today under the web server module only to receive the following error:

          Invalid value for Virtual host's name: vhost. The virtual host name supplied is a top domain name

However, the vhost name that I used is not in the DNS at all so I don't understand the conflict.  I'm assuming this is a bug and wanted to let people know about it if it wasn't found already.

Installation and Upgrades / Ubuntu LDAP client with Ebox 1.3.3 on Jaunty
« on: September 24, 2009, 07:18:38 am »
I decided to upgrade my server to Jaunty and therefore had to go with Ebox 1.3.3 so the instructions I followed from no longer work.  Just wondering if anybody could point me in the right direction for getting a client connected to the LDAP server database since so much has changed since Intrepid with LDAP configuration.  I think these are the main differences in configuration between the howto listed above and what needs to be done now but wonder if somebody could confirm.

      Base dn:  cn=ebox,dc=nodomain
      Admin dn: cn=admin,dc=config
      Admin Pass: e2NyeXB0fUZrV3k1RzNlQURqaEU=  (This may vary...verify in /etc/ldap/slapd.d/olcDatabase={0}config.ldif)
      Domain Name:  EBOX (Whatever you set it  to when you setup Samba as PDC)
      Ebox Server IP/hostname:  (If you setup dns a hostname.domain would be better but an IP will work)

I have tried the above settings and it still fails to list the LDAP users when typing "getent passwd" and I'm not sure if ebox-desktop is update for 1.3.3 on Jaunty so I haven't pursued that route.  Thanks in advance for any insights offered.

Installation and Upgrades / Multiple PXE boot services howto
« on: March 31, 2009, 05:54:27 am »
Ebox has built in support for adding network boot files into the DHCP server which is great and does work well.  However, I wanted to do 2 services via PXE boot one for new Ubuntu installs on workstations and the other for LTSP on a couple machines I have.  So I setup the PXE boot file for the global section in Ebox through the standard GUI interface as normal nothing special had to be done there to make the network installs work.  Of course I want the network installs to be global so every machine besides the ones I specify can do a new install if desired.  In order to make a certain machine have different boot options custom fields must be added to the the fixed IP section of that host.  Since I only have 2 machines that I want to LTSP boot I made the following change to /usr/share/ebox/stubs/dhcp/subnet.mas file on line 27:

*The following code was completely thanks to sixstone.  Thanks for your help with this!

%          foreach my $fixed (@{$fixedAddresses}) {
      host <% $fixed->{'name'} %> {
         hardware ethernet <% $fixed->{'mac'} %>;
         fixed-address <% $fixed->{'ip'} %>;
%          if ( ($fixed->{'name'} eq 'host1') or ($fixed->{'name'} eq 'host2') ) {
            filename "/ltsp/i386/pxelinux.0";
            option root-path "/opt/ltsp/i386";
%          }
%             }

I added the entire foreach loop in case the line ever changes from being on line 27 so you know where it needs to go.  Of course you'll need to change host1 and host2 with the names that you provide under the static IP settings in the DHCP configuration of Ebox.  Hope this helps someone else that wants to accomplish the same task.

I left the port on the proxy to the default 3128 and enabled firewall rules to allow requests coming into Ebox from the outside on 3128 and going out from Ebox on 3128.  I tell a workstation in Firefox to go to my IP address for the proxy at port 3128 and I can browse any content when I put "always allow" in the general settings but whenever I tell it to "filter" all browsing is denied not with the content block filter but with an access denied error.  Are there other rules I need to add to the firewall to let workstations use the content filtering?

Pages: 1 [2]