Messages

1

Installation and Upgrades / Re: DDNS issues where client has two interfaces (wired & wireless)

« on: March 22, 2012, 01:56:13 pm »

I guess the customisation of dhcpd.conf is not possible then?  It's certainly not easy unless maybe if you happen to be a Perl developer.  Cheers community for all your help!

Back to SBS 2011 with either ClearOS, Endian or IPCop for me!

2

Installation and Upgrades / Re: network objects, static dhcp and reverse dns

« on: March 20, 2012, 02:37:33 pm »

Hi biyover,

since I gather that dhcp updates the dns record automatically

I don't believe this is the case unless you enabled Dynamic DNS under DHCP. 

Also, it's not necessary to setup DNS on your local network network at all - it just makes life a lot easier than having to remember loads IP addresses!

Cheers,
Andy

3

Installation and Upgrades / Re: DDNS issues where client has two interfaces (wired & wireless)

« on: March 20, 2012, 12:16:15 pm »

Seriously, no one here can help?  Just in case its was not clear I shall try once more...

I simply want to make the below change (shown in bold below) to the dhcpd.conf file.  Is it possible with Zentyal?

==============================================
/etc/dhcpd.conf:

shared-network eth0 {

        subnet 192.168.0.0 netmask 255.255.255.0 {

            option routers 192.168.0.254;
                option domain-name "brocas.oit";
            option domain-name-servers 192.168.0.254, 192.168.111.105;
                option ntp-servers 192.168.0.254;
                default-lease-time 1800;
                max-lease-time 7200;

                option host-name = config-option server.ddns-hostname;
                ddns-hostname = pick-first-value( option fqdn.hostname,
                                                  option host-name,
                                                  concat("dhcp-", binary-to-ascii(10, 8, "-", leased-address), "-wifi"));
                ddns-domainname      "brocas.oit.";
                zone brocas.oit. {
                    primary 127.0.0.1;
                    key brocas.oit.;
                }
                zone 0.168.192.in-addr.arpa. {
                    primary 127.0.0.1;
                    key brocas.oit.;
                }

            pool {
                range 192.168.0.1 192.168.0.30;
            }
        }
==============================================

Thanks in advance.

4

Installation and Upgrades / Re: DDNS issues where client has two interfaces (wired & wireless)

« on: March 19, 2012, 11:08:49 am »

Any ideas?

5

Installation and Upgrades / Re: I changed Zentyal administration port to 80 and cannot login to it

« on: March 14, 2012, 03:27:44 pm »

Hi,

Have you tried logging in via SSH and rebooting?  Or restarting apache?

Code: [Select]

/etc/init.d/zentyal apache restart

I'm not sure whether Zentyal writes over this config file or not but have a look at /etc/apache2/ports.conf.  Maybe edit it back to 443 and try restarting apache or rebooting Zentyal.  Mine looks like this:

Code: [Select]

# If you just change the port or add more ports here, you will likely also
# have to change the VirtualHost statement in
# /etc/apache2/sites-enabled/000-default
# This is also true if you have upgraded from before 2.2.9-3 (i.e. from
# Debian etch). See /usr/share/doc/apache2.2-common/NEWS.Debian.gz and
# README.Debian.gz

NameVirtualHost *:80
Listen 80

<IfModule mod_ssl.c>
    # If you add NameVirtualHost *:443 here, you will also have to change
    # the VirtualHost statement in /etc/apache2/sites-available/default-ssl
    # to <VirtualHost *:443>
    # Server Name Indication for SSL named virtual hosts is currently not
    # supported by MSIE on Windows XP.
    Listen 443
</IfModule>

<IfModule mod_gnutls.c>
    Listen 443
</IfModule>

Hope this helps.

Cheers,
Andy

6

Installation and Upgrades / DDNS issues where client has two interfaces (wired & wireless)

« on: March 14, 2012, 02:26:30 pm »

Hi all,

I have just enabled DDNS on Zentyal 2.2 for my two LANs:

192.168.0.0/24
192.168.111.0/24

Everything works well except when someone disconnects from the wifi on 192.168.0.0/24 and reconnects to the wired network on 192.168.111.0/24.  This results in a lot of error messages like:

Code: [Select]

Mar 14 12:57:58 kgeorge dhcpd: DHCPACK to 192.168.111.14 (00:24:8c:7b:5f:0b) via eth2
Mar 14 13:01:23 kgeorge dhcpd: DHCPREQUEST for 192.168.111.11 from 00:25:64:7d:70:d1 (Andy-Laptop) via eth2
Mar 14 13:01:23 kgeorge dhcpd: DHCPACK on 192.168.111.11 to 00:25:64:7d:70:d1 (Andy-Laptop) via eth2
Mar 14 13:04:01 kgeorge dhcpd: DHCPREQUEST for 192.168.111.14 from 00:24:8c:7b:5f:0b (Andy-Desktop) via eth2
Mar 14 13:04:01 kgeorge dhcpd: DHCPACK on 192.168.111.14 to 00:24:8c:7b:5f:0b (Andy-Desktop) via eth2
Mar 14 13:05:45 kgeorge dhcpd: DHCPDISCOVER from 90:4c:e5:45:22:01 via eth0
Mar 14 13:05:46 kgeorge dhcpd: DHCPOFFER on 192.168.0.2 to 90:4c:e5:45:22:01 (Andy-Laptop) via eth0
Mar 14 13:05:46 kgeorge named[10571]: client 127.0.0.1#42065: updating zone 'brocas.oit/IN': update unsuccessful: Andy-Laptop.brocas.oit: 'name not in use' prerequisite not satisfied (YXDOMAIN)
Mar 14 13:05:46 kgeorge named[10571]: client 127.0.0.1#51922: updating zone 'brocas.oit/IN': update unsuccessful: Andy-Laptop.brocas.oit/TXT: 'RRset exists (value dependent)' prerequisite not satisfied (NXRRSET)
Mar 14 13:05:46 kgeorge dhcpd: Forward map from Andy-Laptop.brocas.oit. to 192.168.0.2 FAILED: Has an A record but no DHCID, not mine.
Mar 14 13:05:46 kgeorge dhcpd: DHCPREQUEST for 192.168.0.2 (192.168.0.254) from 90:4c:e5:45:22:01 (Andy-Laptop) via eth0
Mar 14 13:05:46 kgeorge dhcpd: DHCPACK on 192.168.0.2 to 90:4c:e5:45:22:01 (Andy-Laptop) via eth0
Mar 14 13:05:50 kgeorge dhcpd: DHCPINFORM from 192.168.0.2 via eth0
Mar 14 13:05:50 kgeorge dhcpd: DHCPACK to 192.168.0.2 (90:4c:e5:45:22:01) via eth0

Does anyone have any suggestions?  Surely this is not a very unusual situation?

I wanted to try the suggestion made in the below article where they change the ddns-hostname to append "-wifi" to the name of all the hosts on a particular network (192.168.0.0/24).

http://www.techswamp.com/2011/06/20/working-around-binds-ddns-limits-for-multi-homed-hosts/

According to your documentation customising configuration scripts is supposed to be easy - so I thought I'd give it a go.  However, I have no idea how to make that simple change to a section of the template that looks like this:

Code: [Select]

<%perl>
        foreach my $iface (keys(%real_ifaces)) {
           # Write configuration if there are any range or fixed addresses
           my @ifacesToCheck = @{$real_ifaces{$iface}};
           push(@ifacesToCheck, $iface);
           my $nIfaceToWrite = grep { @{$ifaces{$_}->{ranges}} > 0 or values(%{$ifaces{$_}->{fixed}}) > 0 } @ifacesToCheck;
           if ( $nIfaceToWrite > 0) {
</%perl>
<& dhcp/shared-network.mas, iface => $iface, ifaces => \%ifaces, vifaces => $real_ifaces{$iface} &>
%          }
%       }

I would really appreciate anyone's help here.  Either to make this minor change or to suggest a better way to overcome the problem.

Cheers,
Andy

7

Installation and Upgrades / Re: Hardware Not Detected - Solos Multiport PCI ADSL2+ Modem (4-port)

« on: December 04, 2010, 10:09:12 pm »

Hi Cperez,

Thanks for your reply.  No, I can see the interfaces via the admin pages.  Now I use ‘start on startup’ the virtual interfaces are still there after a reboot too.  The real problem is that my virtual interfaces do not seem visible from the outside world.  That is to say, I can’t successfully open ports on my virtual IP addresses and forward them to internal machines.

Please see the below post for more information.

http://forum.zentyal.org/index.php?topic=5510.0
 
Many thanks,
Andy

8

Installation and Upgrades / Re: Hardware Not Detected - Solos Multiport PCI ADSL2+ Modem (4-port)

« on: December 03, 2010, 01:00:38 pm »

Please help if you can!

9

Installation and Upgrades / Re: Cannot return to Dashboard

« on: December 01, 2010, 04:23:19 pm »

Hi,

Is there anything in /var/log and /var/log/ebox that might give us a clue as to the problem?  Also have you changed anything recently?

Cheers,
Andy

10

Installation and Upgrades / Re: Hardware Not Detected - Solos Multiport PCI ADSL2+ Modem (4-port)

« on: December 01, 2010, 02:01:25 am »

Also...

/var/log/daemon.log:

Code: [Select]

Nov 30 19:27:37 wellington named[1449]: starting BIND 9.7.0-P1 -u bind
Nov 30 19:27:37 wellington named[1449]: built with '--prefix=/usr' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstatedir=/var' '--enable-threads' '--enable-largefile' '--with-libtool' '--enable-shared' '--enable-static' '--with-openssl=/usr' '--with-gssapi=/usr' '--with-gnu-ld' '--with-dlz-postgres=no' '--with-dlz-mysql=no' '--with-dlz-bdb=yes' '--with-dlz-filesystem=yes' '--with-dlz-ldap=yes' '--with-dlz-stub=yes' '--with-geoip=/usr' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2' 'LDFLAGS=-Wl,-Bsymbolic-functions' 'CPPFLAGS='
Nov 30 19:27:37 wellington named[1449]: adjusted limit on open files from 1024 to 1048576
Nov 30 19:27:37 wellington named[1449]: found 2 CPUs, using 2 worker threads
Nov 30 19:27:37 wellington named[1449]: using up to 4096 sockets
Nov 30 19:27:37 wellington named[1449]: loading configuration from '/etc/bind/named.conf'
Nov 30 19:27:37 wellington named[1449]: reading built-in trusted keys from file '/etc/bind/bind.keys'
Nov 30 19:27:37 wellington named[1449]: using default UDP/IPv4 port range: [1024, 65535]
Nov 30 19:27:37 wellington named[1449]: using default UDP/IPv6 port range: [1024, 65535]
Nov 30 19:27:37 wellington named[1449]: listening on IPv4 interface lo, 127.0.0.1#53
Nov 30 19:27:37 wellington named[1449]: listening on IPv4 interface eth0, 192.168.1.254#53
Nov 30 19:27:37 wellington named[1449]: listening on IPv4 interface nas0, 216.239.32.10#53
Nov 30 19:27:37 wellington named[1449]: listening on IPv4 interface nas0:ns1, 216.239.36.10#53
Nov 30 19:27:37 wellington named[1449]: listening on IPv4 interface nas0:ns2, 216.239.36.11#53
Nov 30 19:27:37 wellington named[1449]: listening on IPv4 interface nas0:www, 216.239.34.10#53
Nov 30 19:27:37 wellington named[1449]: generating session key for dynamic DNS
Nov 30 19:27:37 wellington named[1449]: automatic empty zone: 254.169.IN-ADDR.ARPA
Nov 30 19:27:37 wellington named[1449]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Nov 30 19:27:37 wellington named[1449]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
Nov 30 19:27:37 wellington named[1449]: automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Nov 30 19:27:37 wellington named[1449]: automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Nov 30 19:27:37 wellington named[1449]: automatic empty zone: D.F.IP6.ARPA
Nov 30 19:27:37 wellington named[1449]: automatic empty zone: 8.E.F.IP6.ARPA
Nov 30 19:27:37 wellington named[1449]: automatic empty zone: 9.E.F.IP6.ARPA
Nov 30 19:27:37 wellington named[1449]: automatic empty zone: A.E.F.IP6.ARPA
Nov 30 19:27:37 wellington named[1449]: automatic empty zone: B.E.F.IP6.ARPA
Nov 30 19:27:37 wellington named[1449]: command channel listening on 127.0.0.1#953
Nov 30 19:27:37 wellington named[1449]: command channel listening on ::1#953
Nov 30 19:27:37 wellington named[1449]: zone 0.in-addr.arpa/IN: loaded serial 1
Nov 30 19:27:37 wellington named[1449]: zone 127.in-addr.arpa/IN: loaded serial 1
Nov 30 19:27:37 wellington named[1449]: zone 255.in-addr.arpa/IN: loaded serial 1
Nov 30 19:27:37 wellington named[1449]: zone localhost/IN: loaded serial 2
Nov 30 19:27:37 wellington named[1449]: running
Nov 30 19:27:38 wellington named[1449]: lame server resolving 'mta.mydomain.com' (in 'mydomain.com'?): 216.239.36.10#53
Nov 30 19:27:38 wellington named[1449]: lame server resolving 'mta.mydomain.com' (in 'mydomain.com'?): 216.239.36.11#53
Nov 30 19:27:38 wellington named[1449]: lame server resolving 'ns1.mydomain.com' (in 'mydomain.com'?): 216.239.36.10#53
Nov 30 19:27:38 wellington named[1449]: lame server resolving 'ns1.mydomain.com' (in 'mydomain.com'?): 216.239.36.11#53
Nov 30 19:27:38 wellington named[1449]: lame server resolving 'ns2.mydomain.com' (in 'mydomain.com'?): 216.239.36.10#53
Nov 30 19:27:38 wellington named[1449]: lame server resolving 'ns2.mydomain.com' (in 'mydomain.com'?): 216.239.36.11#53
Nov 30 19:27:41 wellington ddclient[1508]: WARNING:  file /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
Nov 30 19:27:41 wellington ddclient[1511]: WARNING:  file /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
Nov 30 19:27:42 wellington named[1449]: lame server resolving 'mta.mydomain.com.mydomain.com' (in 'mydomain.com'?): 216.239.36.11#53
Nov 30 19:27:42 wellington named[1449]: lame server resolving 'mta.mydomain.com.mydomain.com' (in 'mydomain.com'?): 216.239.36.10#53
Nov 30 19:27:47 wellington named[1449]: received control channel command 'reconfig'
Nov 30 19:27:47 wellington named[1449]: loading configuration from '/etc/bind/named.conf'
Nov 30 19:27:47 wellington named[1449]: reading built-in trusted keys from file '/etc/bind/bind.keys'
Nov 30 19:27:47 wellington named[1449]: using default UDP/IPv4 port range: [1024, 65535]
Nov 30 19:27:47 wellington named[1449]: using default UDP/IPv6 port range: [1024, 65535]
Nov 30 19:27:47 wellington named[1449]: reloading configuration succeeded
Nov 30 19:27:47 wellington named[1449]: any newly configured zones are now loaded
Nov 30 19:27:47 wellington ntpdate[1809]: no servers can be used, exiting
Nov 30 19:27:47 wellington init: ssh main process (1299) terminated with status 255
Nov 30 19:27:47 wellington ntpd[1844]: ntpd 4.2.4p8@1.1612-o Fri Apr  9 00:28:40 UTC 2010 (1)
Nov 30 19:27:47 wellington ntpd[1850]: precision = 1.000 usec
Nov 30 19:27:47 wellington ntpd[1850]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Nov 30 19:27:47 wellington ntpd[1850]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
Nov 30 19:27:47 wellington ntpd[1850]: Listening on interface #1 wildcard, ::#123 Disabled
Nov 30 19:27:47 wellington ntpd[1850]: Listening on interface #2 eth0, fe80::7ae7:d1ff:fe53:6adf#123 Enabled
Nov 30 19:27:47 wellington ntpd[1850]: Listening on interface #3 lo, ::1#123 Enabled
Nov 30 19:27:47 wellington ntpd[1850]: Listening on interface #4 nas0, fe80::200:1ff:fe00:0#123 Enabled
Nov 30 19:27:47 wellington ntpd[1850]: Listening on interface #5 lo, 127.0.0.1#123 Enabled
Nov 30 19:27:47 wellington ntpd[1850]: Listening on interface #6 eth0, 192.168.1.254#123 Enabled
Nov 30 19:27:47 wellington ntpd[1850]: Listening on interface #7 nas0, 216.239.32.10#123 Enabled
Nov 30 19:27:47 wellington ntpd[1850]: Listening on interface #8 nas0:ns1, 216.239.36.10#123 Enabled
Nov 30 19:27:47 wellington ntpd[1850]: Listening on interface #9 nas0:ns2, 216.239.36.11#123 Enabled
Nov 30 19:27:47 wellington ntpd[1850]: Listening on interface #10 nas0:www, 216.239.34.10#123 Enabled
Nov 30 19:27:47 wellington ntpd[1850]: kernel time sync status 2040
Nov 30 19:27:47 wellington ntpd[1850]: frequency initialized 0.000 PPM from /var/lib/ntp/ntp.drift
Nov 30 19:27:47 wellington named[1449]: lame server resolving 'mta.mydomain.com.mydomain.com' (in 'mydomain.com'?): 216.239.36.10#53
Nov 30 19:27:47 wellington named[1449]: lame server resolving 'mta.mydomain.com.mydomain.com' (in 'mydomain.com'?): 216.239.36.11#53
Nov 30 19:27:47 wellington named[1449]: error (network unreachable) resolving 'ns1.mydomain.com/AAAA/IN': 2001:503:c27::2:30#53
Nov 30 19:27:47 wellington named[1449]: error (network unreachable) resolving 'ns1.mydomain.com/AAAA/IN': 2001:503:ba3e::2:30#53
Nov 30 19:27:47 wellington named[1449]: error (network unreachable) resolving 'ns1.mydomain.com/AAAA/IN': 2001:503:a83e::2:30#53
Nov 30 19:27:47 wellington named[1449]: received control channel command 'reconfig'
Nov 30 19:27:47 wellington named[1449]: loading configuration from '/etc/bind/named.conf'
Nov 30 19:27:47 wellington named[1449]: reading built-in trusted keys from file '/etc/bind/bind.keys'
Nov 30 19:27:47 wellington named[1449]: using default UDP/IPv4 port range: [1024, 65535]
Nov 30 19:27:47 wellington named[1449]: using default UDP/IPv6 port range: [1024, 65535]
Nov 30 19:27:47 wellington named[1449]: reloading configuration succeeded
Nov 30 19:27:47 wellington named[1449]: any newly configured zones are now loaded
Nov 30 19:27:47 wellington named[1449]: lame server resolving 'ns1.mydomain.com' (in 'mydomain.com'?): 216.239.36.10#53
Nov 30 19:27:47 wellington named[1449]: lame server resolving 'ns1.mydomain.com' (in 'mydomain.com'?): 216.239.36.11#53
Nov 30 19:27:47 wellington init: ssh main process (1834) terminated with status 255
Nov 30 19:27:47 wellington ntpd[1850]: ntpd exiting on signal 15
Nov 30 19:27:47 wellington ntpdate[1936]: no servers can be used, exiting
Nov 30 19:27:47 wellington ntpd[1972]: ntpd 4.2.4p8@1.1612-o Fri Apr  9 00:28:40 UTC 2010 (1)
Nov 30 19:27:47 wellington ntpd[1973]: precision = 1.000 usec
Nov 30 19:27:47 wellington ntpd[1973]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Nov 30 19:27:47 wellington ntpd[1973]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
Nov 30 19:27:47 wellington ntpd[1973]: Listening on interface #1 wildcard, ::#123 Disabled
Nov 30 19:27:47 wellington ntpd[1973]: Listening on interface #2 eth0, fe80::7ae7:d1ff:fe53:6adf#123 Enabled
Nov 30 19:27:47 wellington ntpd[1973]: Listening on interface #3 lo, ::1#123 Enabled
Nov 30 19:27:47 wellington ntpd[1973]: Listening on interface #4 nas0, fe80::200:1ff:fe00:0#123 Enabled
Nov 30 19:27:47 wellington ntpd[1973]: Listening on interface #5 lo, 127.0.0.1#123 Enabled
Nov 30 19:27:47 wellington ntpd[1973]: Listening on interface #6 eth0, 192.168.1.254#123 Enabled
Nov 30 19:27:47 wellington ntpd[1973]: Listening on interface #7 nas0, 216.239.32.10#123 Enabled
Nov 30 19:27:47 wellington ntpd[1973]: Listening on interface #8 nas0:ns1, 216.239.36.10#123 Enabled
Nov 30 19:27:47 wellington ntpd[1973]: Listening on interface #9 nas0:ns2, 216.239.36.11#123 Enabled
Nov 30 19:27:47 wellington ntpd[1973]: Listening on interface #10 nas0:www, 216.239.34.10#123 Enabled
Nov 30 19:27:47 wellington ntpd[1973]: kernel time sync status 2040
Nov 30 19:27:47 wellington ntpd[1973]: frequency initialized 0.000 PPM from /var/lib/ntp/ntp.drift
Nov 30 19:27:48 wellington named[1449]: received control channel command 'reconfig'
Nov 30 19:27:48 wellington named[1449]: loading configuration from '/etc/bind/named.conf'
Nov 30 19:27:48 wellington named[1449]: reading built-in trusted keys from file '/etc/bind/bind.keys'
Nov 30 19:27:48 wellington named[1449]: using default UDP/IPv4 port range: [1024, 65535]
Nov 30 19:27:48 wellington named[1449]: using default UDP/IPv6 port range: [1024, 65535]
Nov 30 19:27:48 wellington named[1449]: reloading configuration succeeded
Nov 30 19:27:48 wellington named[1449]: any newly configured zones are now loaded
Nov 30 19:27:48 wellington init: ssh main process (1945) terminated with status 255
Nov 30 19:27:48 wellington ntpd[1973]: ntpd exiting on signal 15
Nov 30 19:27:48 wellington ntpdate[2044]: no servers can be used, exiting
Nov 30 19:27:48 wellington named[1449]: lame server resolving 'ns2.mydomain.com' (in 'mydomain.com'?): 216.239.36.11#53
Nov 30 19:27:48 wellington named[1449]: lame server resolving 'ns2.mydomain.com' (in 'mydomain.com'?): 216.239.36.10#53
Nov 30 19:27:48 wellington ntpd[2079]: ntpd 4.2.4p8@1.1612-o Fri Apr  9 00:28:40 UTC 2010 (1)
Nov 30 19:27:48 wellington ntpd[2080]: precision = 1.000 usec
Nov 30 19:27:48 wellington ntpd[2080]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Nov 30 19:27:48 wellington ntpd[2080]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
Nov 30 19:27:48 wellington ntpd[2080]: Listening on interface #1 wildcard, ::#123 Disabled
Nov 30 19:27:48 wellington ntpd[2080]: Listening on interface #2 eth0, fe80::7ae7:d1ff:fe53:6adf#123 Enabled
Nov 30 19:27:48 wellington ntpd[2080]: Listening on interface #3 lo, ::1#123 Enabled
Nov 30 19:27:48 wellington ntpd[2080]: Listening on interface #4 nas0, fe80::200:1ff:fe00:0#123 Enabled
Nov 30 19:27:48 wellington ntpd[2080]: Listening on interface #5 lo, 127.0.0.1#123 Enabled
Nov 30 19:27:48 wellington ntpd[2080]: Listening on interface #6 eth0, 192.168.1.254#123 Enabled
Nov 30 19:27:48 wellington ntpd[2080]: Listening on interface #7 nas0, 216.239.32.10#123 Enabled
Nov 30 19:27:48 wellington ntpd[2080]: Listening on interface #8 nas0:ns1, 216.239.36.10#123 Enabled
Nov 30 19:27:48 wellington ntpd[2080]: Listening on interface #9 nas0:ns2, 216.239.36.11#123 Enabled
Nov 30 19:27:48 wellington ntpd[2080]: Listening on interface #10 nas0:www, 216.239.34.10#123 Enabled
Nov 30 19:27:48 wellington ntpd[2080]: kernel time sync status 2040
Nov 30 19:27:48 wellington ntpd[2080]: frequency initialized 0.000 PPM from /var/lib/ntp/ntp.drift
Nov 30 19:27:48 wellington named[1449]: received control channel command 'reconfig'
Nov 30 19:27:48 wellington named[1449]: loading configuration from '/etc/bind/named.conf'
Nov 30 19:27:48 wellington named[1449]: reading built-in trusted keys from file '/etc/bind/bind.keys'
Nov 30 19:27:48 wellington named[1449]: using default UDP/IPv4 port range: [1024, 65535]
Nov 30 19:27:48 wellington named[1449]: using default UDP/IPv6 port range: [1024, 65535]
Nov 30 19:27:48 wellington named[1449]: reloading configuration succeeded
Nov 30 19:27:48 wellington named[1449]: any newly configured zones are now loaded
Nov 30 19:27:48 wellington init: ssh main process (2048) terminated with status 255
Nov 30 19:27:48 wellington ntpd[2080]: ntpd exiting on signal 15
Nov 30 19:27:48 wellington ntpdate[2151]: no servers can be used, exiting
Nov 30 19:27:48 wellington ntpd[2186]: ntpd 4.2.4p8@1.1612-o Fri Apr  9 00:28:40 UTC 2010 (1)
Nov 30 19:27:48 wellington ntpd[2187]: precision = 1.000 usec
Nov 30 19:27:48 wellington ntpd[2187]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Nov 30 19:27:48 wellington ntpd[2187]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
Nov 30 19:27:48 wellington ntpd[2187]: Listening on interface #1 wildcard, ::#123 Disabled
Nov 30 19:27:48 wellington ntpd[2187]: Listening on interface #2 eth0, fe80::7ae7:d1ff:fe53:6adf#123 Enabled
Nov 30 19:27:48 wellington ntpd[2187]: Listening on interface #3 lo, ::1#123 Enabled
Nov 30 19:27:48 wellington ntpd[2187]: Listening on interface #4 nas0, fe80::200:1ff:fe00:0#123 Enabled
Nov 30 19:27:48 wellington ntpd[2187]: Listening on interface #5 lo, 127.0.0.1#123 Enabled
Nov 30 19:27:48 wellington ntpd[2187]: Listening on interface #6 eth0, 192.168.1.254#123 Enabled
Nov 30 19:27:48 wellington ntpd[2187]: Listening on interface #7 nas0, 216.239.32.10#123 Enabled
Nov 30 19:27:48 wellington ntpd[2187]: Listening on interface #8 nas0:ns1, 216.239.36.10#123 Enabled
Nov 30 19:27:48 wellington ntpd[2187]: Listening on interface #9 nas0:ns2, 216.239.36.11#123 Enabled
Nov 30 19:27:48 wellington ntpd[2187]: Listening on interface #10 nas0:www, 216.239.34.10#123 Enabled
Nov 30 19:27:48 wellington ntpd[2187]: kernel time sync status 2040
Nov 30 19:27:48 wellington ntpd[2187]: frequency initialized 0.000 PPM from /var/lib/ntp/ntp.drift
Nov 30 19:27:52 wellington dhcpd: Wrote 0 leases to leases file.
Nov 30 19:27:52 wellington dhcpd:
Nov 30 19:27:52 wellington dhcpd: No subnet declaration for nas0 (216.239.32.10).
Nov 30 19:27:52 wellington dhcpd: ** Ignoring requests on nas0.  If this is not what
Nov 30 19:27:52 wellington dhcpd:    you want, please write a subnet declaration
Nov 30 19:27:52 wellington dhcpd:    in your dhcpd.conf file for the network segment
Nov 30 19:27:52 wellington dhcpd:    to which interface nas0 is attached. **
Nov 30 19:27:52 wellington dhcpd:
Nov 30 19:27:52 wellington dhcpd: Can't create PID file /var/run/dhcp3-server/dhcpd.pid: No such file or directory.
Nov 30 19:27:52 wellington named[1449]: received control channel command 'stop -p'
Nov 30 19:27:52 wellington named[1449]: shutting down: flushing changes
Nov 30 19:27:52 wellington named[1449]: stopping command channel on 127.0.0.1#953
Nov 30 19:27:52 wellington named[1449]: stopping command channel on ::1#953
Nov 30 19:27:52 wellington named[1449]: no longer listening on 127.0.0.1#53
Nov 30 19:27:52 wellington named[1449]: no longer listening on 192.168.1.254#53
Nov 30 19:27:52 wellington named[1449]: no longer listening on 216.239.32.10#53
Nov 30 19:27:52 wellington named[1449]: no longer listening on 216.239.36.10#53
Nov 30 19:27:52 wellington named[1449]: no longer listening on 216.239.36.11#53
Nov 30 19:27:52 wellington named[1449]: no longer listening on 216.239.34.10#53
Nov 30 19:27:52 wellington named[1449]: exiting
Nov 30 19:27:55 wellington init: ebox.redis main process (1527) killed by TERM signal
Nov 30 19:27:56 wellington dhcpd: Wrote 0 leases to leases file.
Nov 30 19:27:56 wellington dhcpd:
Nov 30 19:27:56 wellington dhcpd: No subnet declaration for nas0 (216.239.32.10).
Nov 30 19:27:56 wellington dhcpd: ** Ignoring requests on nas0.  If this is not what
Nov 30 19:27:56 wellington dhcpd:    you want, please write a subnet declaration
Nov 30 19:27:56 wellington dhcpd:    in your dhcpd.conf file for the network segment
Nov 30 19:27:56 wellington dhcpd:    to which interface nas0 is attached. **
Nov 30 19:27:56 wellington dhcpd:
Nov 30 19:31:00 wellington ntpd[2187]: synchronized to LOCAL(0), stratum 13
Nov 30 19:31:00 wellington ntpd[2187]: kernel time sync status change 2001


11

Installation and Upgrades / Re: Hardware Not Detected - Solos Multiport PCI ADSL2+ Modem (4-port)

« on: December 01, 2010, 01:59:29 am »

Hi Cperez,

Thanks for your reply – it’s certainly kept me busy recently.  I entered the following in /etc/rc.local:

exec /usr/sbin/solbridge

…however, this did not work.  If I placed it after the existing ‘/etc/init.d/slim restart’ then I found myself unable to boot back into Zentyal (I’m using via a KVM).  If I place it before, it loads but too late still with the network and firewall modules also failing to load.

Interestingly, I’ve been playing with the upstart script and it seems the following line works (almost):

Code: [Select]

start on startup

… although this appears to work, i.e, when I reboot the virtual interfaces are still present, I have internet, all Zentyal modules start successfully, etc.  However it still does not seem to register the interfaces at some level.  The only ugly messages I can find in my log files after a reboot are:

/var/log/boot.log:

Code: [Select]

<< my script output ommited here... >>

 * Starting AppArmor profiles        [80G Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox

 [74G[ OK ]
 * Starting domain name service... bind9        [80G
 [74G[ OK ]
 * Starting PostgreSQL 8.4 database server        [80G
 [74G[ OK ]
WARNING:  file /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
 * Starting Zentyal module: network        [80G
 [74G[ OK ]
 * Starting Zentyal module: firewall        [80G
 [74G[ OK ]
 * Starting Zentyal module: dhcp        [80G
 [74G[ OK ]
 * Starting Zentyal module: dns        [80G
 [74G[ OK ]
 * Starting Zentyal module: events        [80G
 [74G[ OK ]
 * Starting Zentyal module: logs        [80G
 [74G[ OK ]
 * Starting Zentyal module: apache        [80G
 [74G[ OK ]
Starting redis-server: redis-server.
 * Starting DHCP server dhcpd3        [80G
 [74G[ OK ]
 * Starting web server apache2        [80G
 [74G[ OK ]
Stopping X display manager: slim not running (/var/run/slim.lock not found).
Starting X display manager: slim.
Starting X display manager: slim already running.

/var/log/ebox/ebox.log:

Code: [Select]

2010/11/30 19:27:43 INFO> Redis.pm:584 EBox::Config::Redis::_initRedis - Starting redis server
2010/11/30 19:27:46 INFO> Service.pm:705 EBox::Module::Service::restartService - Restarting service for module: network
2010/11/30 19:27:49 INFO> Service.pm:705 EBox::Module::Service::restartService - Restarting service for module: firewall
2010/11/30 19:27:50 INFO> Base.pm:798 EBox::Module::Base::_hook - Running hook: /etc/ebox/hooks/firewall.postservice 1
2010/11/30 19:27:50 INFO> Service.pm:705 EBox::Module::Service::restartService - Restarting service for module: dhcp
2010/11/30 19:27:50 ERROR> Sudo.pm:212 EBox::Sudo::_rootError - root command /usr/bin/test -f '/var/lib/ebox/conf/dhcp/eth0/firmware' failed.
Error output:
Command output: .
Exit value: 1
2010/11/30 19:27:50 ERROR> Sudo.pm:212 EBox::Sudo::_rootError - root command /usr/bin/test -f '/var/lib/ebox/conf/dhcp/nas0/firmware' failed.
Error output:
Command output: .
Exit value: 1
2010/11/30 19:27:51 ERROR> Sudo.pm:212 EBox::Sudo::_rootError - root command /usr/bin/test -f '/var/lib/ebox/conf/dhcp/nas0:ns1/firmware' failed.
Error output:
Command output: .
Exit value: 1
2010/11/30 19:27:51 ERROR> Sudo.pm:212 EBox::Sudo::_rootError - root command /usr/bin/test -f '/var/lib/ebox/conf/dhcp/nas0:ns2/firmware' failed.
Error output:
Command output: .
Exit value: 1
2010/11/30 19:27:52 ERROR> Sudo.pm:212 EBox::Sudo::_rootError - root command /usr/bin/test -f '/var/lib/ebox/conf/dhcp/nas0:www/firmware' failed.
Error output:
Command output: .
Exit value: 1
2010/11/30 19:27:52 INFO> Service.pm:705 EBox::Module::Service::restartService - Restarting service for module: dns
2010/11/30 19:27:53 INFO> Service.pm:705 EBox::Module::Service::restartService - Restarting service for module: events
2010/11/30 19:27:53 INFO> Service.pm:705 EBox::Module::Service::restartService - Restarting service for module: logs
2010/11/30 19:27:53 INFO> Service.pm:705 EBox::Module::Service::restartService - Restarting service for module: apache
2010/11/30 19:27:54 INFO> EventDaemon.pm:301 EBox::EventDaemon::_loadModules - EBox::Event::Dispatcher::Log loaded from registeredDispatchers
2010/11/30 19:28:16 INFO> Redis.pm:584 EBox::Config::Redis::_initRedis - Starting redis server

Does anyone have any suggestions?  Could someone please explain how I can add my netmask 255.255.0.0 to dhcpd.conf for the nas0 interface (if that is what I need to do)?  I’m not sure why I would want DHCP for my nas0 interfaces?!

Many thanks,
Andy

12

Installation and Upgrades / Re: Help configuring port forwarding

« on: November 25, 2010, 02:46:35 am »

Hi Cperez (wow, a “Zen Monk”!), thanks for your reply.  Firstly to answer your question, yes, I am trying to redirect external nas0:www, nas0:ns1, nas0:ns2 (with public IP addresses) to internal (private IP addresses).

Secondly, as I mentioned above, the main purpose of the post above was to confirm the configuration as good (which you seem to have done).  That being the case, I should refer you to another post which I think might be the root of the problem (only the last post by me on the 24-Nov is relevant):

http://forum.zentyal.org/index.php?topic=5242.msg22757

Either way, please find the output you asked for below:

iptables -t filter -v -L:

Code: [Select]

Chain INPUT (policy DROP 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         
 419K   76M ACCEPT     all  --  lo     any     anywhere             anywhere           
  133  6103 DROP       all  --  any    any     anywhere             anywhere            state INVALID
26637 4192K ACCEPT     all  --  any    any     anywhere             anywhere            state RELATED,ESTABLISHED
18327 1189K inospoof   all  --  any    any     anywhere             anywhere           
18327 1189K iexternalmodules  all  --  any    any     anywhere             anywhere           
18327 1189K iexternal  all  --  any    any     anywhere             anywhere           
16592 1093K inoexternal  all  --  any    any     anywhere             anywhere           
15124 1013K imodules   all  --  any    any     anywhere             anywhere           
15124 1013K iintservs  all  --  any    any     anywhere             anywhere           
15124 1013K iglobal    all  --  any    any     anywhere             anywhere           
    0     0 ACCEPT     icmp !f  any    any     anywhere             anywhere            icmp echo-request state NEW
    0     0 ACCEPT     icmp !f  any    any     anywhere             anywhere            icmp echo-reply state NEW
    0     0 ACCEPT     icmp !f  any    any     anywhere             anywhere            icmp destination-unreachable state NEW
    0     0 ACCEPT     icmp !f  any    any     anywhere             anywhere            icmp source-quench state NEW
    0     0 ACCEPT     icmp !f  any    any     anywhere             anywhere            icmp time-exceeded state NEW
    0     0 ACCEPT     icmp !f  any    any     anywhere             anywhere            icmp parameter-problem state NEW
    2   152 idrop      all  --  any    any     anywhere             anywhere           

Chain FORWARD (policy DROP 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 DROP       all  --  any    any     anywhere             anywhere            state INVALID
 125K   82M ACCEPT     all  --  any    any     anywhere             anywhere            state RELATED,ESTABLISHED
 6851  471K fnospoof   all  --  any    any     anywhere             anywhere           
 6851  471K fredirects  all  --  any    any     anywhere             anywhere           
 6851  471K fmodules   all  --  any    any     anywhere             anywhere           
 6851  471K ffwdrules  all  --  any    any     anywhere             anywhere           
 6851  471K fnoexternal  all  --  any    any     anywhere             anywhere           
 6851  471K fdns       all  --  any    any     anywhere             anywhere           
 6851  471K fobjects   all  --  any    any     anywhere             anywhere           
 6851  471K fglobal    all  --  any    any     anywhere             anywhere           
    0     0 ACCEPT     icmp !f  any    any     anywhere             anywhere            icmp echo-request state NEW
    0     0 ACCEPT     icmp !f  any    any     anywhere             anywhere            icmp echo-reply state NEW
    0     0 ACCEPT     icmp !f  any    any     anywhere             anywhere            icmp destination-unreachable state NEW
    0     0 ACCEPT     icmp !f  any    any     anywhere             anywhere            icmp source-quench state NEW
    0     0 ACCEPT     icmp !f  any    any     anywhere             anywhere            icmp time-exceeded state NEW
    0     0 ACCEPT     icmp !f  any    any     anywhere             anywhere            icmp parameter-problem state NEW
    0     0 fdrop      all  --  any    any     anywhere             anywhere           

Chain OUTPUT (policy DROP 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         
 420K   76M ACCEPT     all  --  any    lo      anywhere             anywhere           
    0     0 DROP       all  --  any    any     anywhere             anywhere            state INVALID
27501 3705K ACCEPT     all  --  any    any     anywhere             anywhere            state RELATED,ESTABLISHED
27468 2112K ointernal  all  --  any    any     anywhere             anywhere           
  173 10380 omodules   all  --  any    any     anywhere             anywhere           
  173 10380 oglobal    all  --  any    any     anywhere             anywhere           
    0     0 ACCEPT     icmp !f  any    any     anywhere             anywhere            icmp echo-request state NEW
    0     0 ACCEPT     icmp !f  any    any     anywhere             anywhere            icmp echo-reply state NEW
    0     0 ACCEPT     icmp !f  any    any     anywhere             anywhere            icmp destination-unreachable state NEW
    0     0 ACCEPT     icmp !f  any    any     anywhere             anywhere            icmp source-quench state NEW
    0     0 ACCEPT     icmp !f  any    any     anywhere             anywhere            icmp time-exceeded state NEW
    0     0 ACCEPT     icmp !f  any    any     anywhere             anywhere            icmp parameter-problem state NEW
    0     0 odrop      all  --  any    any     anywhere             anywhere           

Chain drop (3 references)
 pkts bytes target     prot opt in     out     source               destination         
 1448 78900 LOG        all  --  any    any     anywhere             anywhere            limit: avg 50/min burst 10 LOG level debug prefix `ebox-firewall drop '
 1470 79780 DROP       all  --  any    any     anywhere             anywhere           

Chain fdns (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 ACCEPT     udp  --  any    any     anywhere             ns2.betherenow.co.uk state NEW udp dpt:domain
    0     0 ACCEPT     tcp  --  any    any     anywhere             ns2.betherenow.co.uk state NEW tcp dpt:domain
    0     0 ACCEPT     udp  --  any    any     anywhere             ns1.betherenow.co.uk state NEW udp dpt:domain
    0     0 ACCEPT     tcp  --  any    any     anywhere             ns1.betherenow.co.uk state NEW tcp dpt:domain

Chain fdrop (8 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 drop       all  --  any    any     anywhere             anywhere           

Chain ffwdrules (1 references)
 pkts bytes target     prot opt in     out     source               destination         
 6851  471K RETURN     all  --  eth0   any     anywhere             anywhere
 
    0     0 ACCEPT     udp  --  any    any     anywhere             216-239-36-11.zone3.bethere.co.uk udp dpt:domain
    0     0 ACCEPT     tcp  --  any    any     anywhere             216-239-36-11.zone3.bethere.co.uk tcp dpt:domain
    0     0 ACCEPT     udp  --  any    any     anywhere             216-239-36-10.zone3.bethere.co.uk udp dpt:domain
    0     0 ACCEPT     tcp  --  any    any     anywhere             216-239-36-10.zone3.bethere.co.uk tcp dpt:domain
    0     0 ACCEPT     udp  --  any    any     anywhere             216-239-34-10.zone3.bethere.co.uk udp dpt:www
    0     0 ACCEPT     tcp  --  any    any     anywhere             216-239-34-10.zone3.bethere.co.uk tcp dpt:www

Chain fglobal (1 references)
 pkts bytes target     prot opt in     out     source               destination         
 6851  471K ACCEPT     all  --  any    any     anywhere             anywhere           

Chain fmodules (1 references)
 pkts bytes target     prot opt in     out     source               destination         

Chain fnoexternal (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 fdrop      all  --  nas0   any     anywhere             anywhere            state NEW

Chain fnospoof (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 fdrop      all  --  !eth0  any     localnet/24          anywhere           
    0     0 fdrop      all  --  !nas0  any     216.239.19.0/20       anywhere           
    0     0 fdrop      all  --  !nas0  any     216.239.19.0/20       anywhere           
    0     0 fdrop      all  --  !nas0  any     216.239.19.0/20       anywhere           
    0     0 fdrop      all  --  !nas0  any     216.239.19.0/20       anywhere           

Chain fobjects (1 references)
 pkts bytes target     prot opt in     out     source               destination         

Chain fredirects (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 LOG        udp  --  nas0   any     anywhere             192.168.1.200     state NEW udp dpt:domain limit: avg 50/min burst 10 LOG level debug prefix `ebox-firewall redirect '
    0     0 ACCEPT     udp  --  nas0   any     anywhere             192.168.1.200     state NEW udp dpt:domain
    0     0 LOG        tcp  --  nas0   any     anywhere             192.168.1.200     state NEW tcp dpt:domain limit: avg 50/min burst 10 LOG level debug prefix `ebox-firewall redirect '
    0     0 ACCEPT     tcp  --  nas0   any     anywhere             192.168.1.200     state NEW tcp dpt:domain
    0     0 LOG        udp  --  nas0   any     anywhere             192.168.1.197     state NEW udp dpt:www limit: avg 50/min burst 10 LOG level debug prefix `ebox-firewall redirect '
    0     0 ACCEPT     udp  --  nas0   any     anywhere             192.168.1.197     state NEW udp dpt:www
    0     0 LOG        tcp  --  nas0   any     anywhere             192.168.1.197     state NEW tcp dpt:www limit: avg 50/min burst 10 LOG level debug prefix `ebox-firewall redirect '
    0     0 ACCEPT     tcp  --  nas0   any     anywhere             192.168.1.197     state NEW tcp dpt:www
    0     0 LOG        udp  --  nas0   any     anywhere             192.168.1.197     state NEW udp dpt:domain limit: avg 50/min burst 10 LOG level debug prefix `ebox-firewall redirect '
    0     0 ACCEPT     udp  --  nas0   any     anywhere             192.168.1.197     state NEW udp dpt:domain
    0     0 LOG        tcp  --  nas0   any     anywhere             192.168.1.197     state NEW tcp dpt:domain limit: avg 50/min burst 10 LOG level debug prefix `ebox-firewall redirect '
    0     0 ACCEPT     tcp  --  nas0   any     anywhere             192.168.1.197     state NEW tcp dpt:domain

Chain ftoexternalonly (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 ACCEPT     all  --  any    nas0    anywhere             anywhere           
    0     0 fdrop      all  --  any    any     anywhere             anywhere           

Chain idrop (7 references)
 pkts bytes target     prot opt in     out     source               destination         
 1470 79780 drop       all  --  any    any     anywhere             anywhere           

Chain iexternal (1 references)
 pkts bytes target     prot opt in     out     source               destination         
15124 1013K RETURN     all  --  eth0   any     anywhere             anywhere           
  592 27744 ACCEPT     udp  --  any    any     anywhere             anywhere            udp dpt:domain state NEW
    0     0 ACCEPT     tcp  --  any    any     anywhere             anywhere            tcp dpt:domain state NEW
    0     0 ACCEPT     udp  --  any    any     anywhere             anywhere            udp dpt:www state NEW
   15   664 ACCEPT     tcp  --  any    any     anywhere             anywhere            tcp dpt:www state NEW
 1128 67656 ACCEPT     tcp  --  any    any     anywhere             anywhere            tcp dpt:ssh state NEW

Chain iexternalmodules (1 references)
 pkts bytes target     prot opt in     out     source               destination         
15124 1013K RETURN     all  --  eth0   any     anywhere             anywhere           

Chain iglobal (1 references)
 pkts bytes target     prot opt in     out     source               destination         
15122 1013K ACCEPT     udp  --  any    any     anywhere             anywhere            udp dpt:domain state NEW
    0     0 ACCEPT     tcp  --  any    any     anywhere             anywhere            tcp dpt:domain state NEW
    0     0 ACCEPT     udp  --  any    any     anywhere             anywhere            udp dpt:bootps state NEW
    0     0 ACCEPT     udp  --  any    any     anywhere             anywhere            udp dpt:tftp state NEW
    0     0 ACCEPT     tcp  --  any    any     anywhere             anywhere            tcp dpt:ssh state NEW
    0     0 ACCEPT     tcp  --  any    any     anywhere             anywhere            tcp dpt:https state NEW

Chain iintservs (1 references)
 pkts bytes target     prot opt in     out     source               destination         

Chain imodules (1 references)
 pkts bytes target     prot opt in     out     source               destination         

Chain inoexternal (1 references)
 pkts bytes target     prot opt in     out     source               destination         
 1468 79628 idrop      all  --  nas0   any     anywhere             anywhere            state NEW

Chain inointernal (0 references)
 pkts bytes target     prot opt in     out     source               destination         

Chain inospoof (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 idrop      all  --  !eth0  any     localnet/24          anywhere           
    0     0 idrop      all  --  !nas0  any     216.239.19.0/20       anywhere           
    0     0 idrop      all  --  !nas0  any     216.239.19.0/20       anywhere           
    0     0 idrop      all  --  !nas0  any     216.239.19.0/20       anywhere           
    0     0 idrop      all  --  !nas0  any     216.239.19.0/20       anywhere           

Chain log (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 LOG        all  --  any    any     anywhere             anywhere            limit: avg 50/min burst 10 LOG level debug prefix `ebox-firewall log '
    0     0 RETURN     all  --  any    any     anywhere             anywhere           

Chain odrop (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 drop       all  --  any    any     anywhere             anywhere           

Chain oglobal (1 references)
 pkts bytes target     prot opt in     out     source               destination         
  173 10380 ACCEPT     all  --  any    any     anywhere             anywhere            state NEW

Chain ointernal (1 references)
 pkts bytes target     prot opt in     out     source               destination         
 1618  119K ACCEPT     udp  --  any    any     anywhere             ns2.betherenow.co.uk state NEW udp dpt:domain
    0     0 ACCEPT     tcp  --  any    any     anywhere             ns2.betherenow.co.uk state NEW tcp dpt:domain
   29  2331 ACCEPT     udp  --  any    any     anywhere             ns1.betherenow.co.uk state NEW udp dpt:domain
    0     0 ACCEPT     tcp  --  any    any     anywhere             ns1.betherenow.co.uk state NEW tcp dpt:domain
    0     0 ACCEPT     tcp  --  any    any     anywhere             anywhere            state NEW tcp dpt:domain
25648 1981K ACCEPT     udp  --  any    any     anywhere             anywhere            state NEW udp dpt:domain

Chain omodules (1 references)
 pkts bytes target     prot opt in     out     source               destination         

iptables -t nat -v -L:

Code: [Select]

Chain PREROUTING (policy ACCEPT 17484 packets, 1140K bytes)
 pkts bytes target     prot opt in     out     source               destination         
17484 1140K premodules  all  --  any    any     anywhere             anywhere           
    0     0 DNAT       udp  --  nas0   any     anywhere             216-239-36-10.zone3.bethere.co.uk udp dpt:domain to:192.168.1.200
    0     0 DNAT       tcp  --  nas0   any     anywhere             216-239-36-10.zone3.bethere.co.uk tcp dpt:domain to:192.168.1.200
    0     0 DNAT       udp  --  nas0   any     anywhere             216-239-34-10.zone3.bethere.co.uk udp dpt:www to:192.168.1.197
    0     0 DNAT       tcp  --  nas0   any     anywhere             216-239-34-10.zone3.bethere.co.uk tcp dpt:www to:192.168.1.197
    0     0 DNAT       udp  --  nas0   any     anywhere             216-239-36-11.zone3.bethere.co.uk udp dpt:domain to:192.168.1.197
    0     0 DNAT       tcp  --  nas0   any     anywhere             216-239-36-11.zone3.bethere.co.uk tcp dpt:domain to:192.168.1.197

Chain POSTROUTING (policy ACCEPT 38216 packets, 2757K bytes)
 pkts bytes target     prot opt in     out     source               destination         
44924 3214K postmodules  all  --  any    any     anywhere             anywhere       
 6708  457K SNAT       all  --  any    nas0   !216-239-32-10.zone3.bethere.co.uk  anywhere            to:216.239.32.10

Chain OUTPUT (policy ACCEPT 38216 packets, 2757K bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain postmodules (1 references)
 pkts bytes target     prot opt in     out     source               destination         

Chain premodules (1 references)
 pkts bytes target     prot opt in     out     source               destination         


Thanks again for your help,
Andy

13

Installation and Upgrades / Re: Add-On - PPPOE

« on: November 24, 2010, 07:29:55 pm »

Hi guys,

Did you have any luck with the PPPoE module?  This seems very similar to my problem:

http://forum.zentyal.org/index.php?topic=5242.msg22757

Any help appreciated!

Cheers,
Andy

14

Installation and Upgrades / Re: Hardware Not Detected - Solos Multiport PCI ADSL2+ Modem (4-port)

« on: November 24, 2010, 07:07:07 pm »

Hi all,

Although I have made a lot of progress on this issue I still desperately need help!!

To give you an update, the card was recognised but being an ATM device I first needed to run the following commands:

Code: [Select]

$ modprobe atm
$ insmod solos-pci.ko
$ br2684ctl -b -s 2040 -c 0 -a 0.0.101
$ ifconfig nas0 1.2.3.4 up

Note:  Here, IP address 1.2.3.4 is my public static IP address.  Also 0.0.101 is the first WAN port (0) and then VCI/VCP (0.101).

If I set up a gateway on this interface to my ISP provided gateway then all works as it should!  However, if I reboot all settings are lost.  This prompted me to write a script to automate the process.  And here in lies the problem…

I think the script works fine for a regular Ubuntu installation but I don’t think it is playing nicely with the Zentyal software.  IE, I think it might not be starting at the right time?!  I’m really not familiar with ‘upstart’ and the documentation is not great.  There seem to be a number of problems relating to the firewall (and virtual interfaces) and DHCP?!

/etc/init/solbridge.conf:

Code: [Select]

# Setup Solos ADSL modem interfaces

description "setup Solos DSL modem interfaces"

start on started networking
console output
task
exec /usr/sbin/solbridge


/usr/sbin/solbridge:

Code: [Select]

#!/bin/sh
PAIRS=$@
CONF=/etc/default/solbridge
OUT=/root/solbridge.out

if [ -z $PAIRS ]; then
echo "no args, using default"
if [ -r ${CONF} ]; then
echo "loading default conf" >> ${OUT}
. ${CONF}
PAIRS=${DAEMON_ARGS}
else
echo "no default configuration! exitting!"
return 2
fi
fi

WAIT=10
sleep ${WAIT}


IFCFG=/sbin/ifconfig
BRCTL=/usr/sbin/br2684ctl
LSM=/sbin/lsmod
MODPRB=/sbin/modprobe
MODS="atm solos-pci"

RET=2

if [ ! -z $PAIRS ]; then


RET=0
## if mods are not loaded:
for m in ${MODS}
do
${LSM} | grep ${m} > /dev/null
if [ "$?" != 0 ]; then
RET=$(( $RET + 1))
fi
done
if [ "$RET" != 0 ]; then
## load them:
echo "loading drivers" >> ${OUT}
for m in $MODS
do
${MODPRB} $m
done
fi

RET=0
for pair in ${PAIRS}
do
IDX=`echo ${pair} | cut -d: -f1`
IP=`echo ${pair} | cut -d: -f2`
echo "IDX=${IDX}, IP=${IP}" >> ${OUT}
${BRCTL} -b -s 2040 -c ${IDX} -a ${IDX}.0.101 2>&1 >> ${OUT}
RET=$?
if [ "$RET" = 0 ]; then
# ${IFCFG} nas${IDX} ${IP} netmask 255.255.0.0 up 2>&1 >> ${OUT}
${IFCFG} nas${IDX} ${IP} up 2>&1 >> ${OUT}
RET=$?
if [ "$RET" != 0 ]; then
exit 2
fi

# Add your ISP provided gateway here:
# route add -net default gw 123.123.123.1
/sbin/ip route add default via 123.123.123.1

echo "Things seem good" >> ${OUT}
echo "ifconfig -a output:" >> ${OUT}
${IFCFG} -a  >> ${OUT}
echo "routing tables:" >> ${OUT}
netstat -r >> ${OUT}


else
echo "failed to setup bridge ${IDX}"
fi
done
fi

exit $RET

/etc/default/solbridge:

Code: [Select]

# Replace 1.2.3.4 with public static IP address.
# The 0 from 0:1.2.3.4 refers to port 0 (0-3).
# If it was plugged into the 3rd port it would be 2:1.2.3.4.

DAEMON_ARGS="0:1.2.3.4"

Please could someone help make this script play nicely with Zentyal?

Many thanks,
Andy

15

Installation and Upgrades / Re: Question about ppp0

« on: November 24, 2010, 05:40:43 pm »

To answer my own question…. yes, I believe it would!  However, this turned out to be irrelevant as I am with BE broadband (bethere.co.uk) and they use a bridged (nas0) connection with VCI/VPI=0/101.