Hardware Not Detected - Solos Multiport PCI ADSL2+ Modem (4-port)

[andyp]

Hi,

Is it possible to get the 4-port Solos Multiport PCI ADSL2+ Modem card (http://www.traverse.com.au/productview.php?product_id=116) from Traverse Technologies working under Zentyal?

Apparently the driver is included in kernel versions 2.6.29 and later so I was surprised that it was not automatically detected and working upon installation.

Zentyal was able to detect their single port card, the Vicking PCI ADSL2+ (http://www.traverse.com.au/productview.php?product_id=115).  This card worked out-the-box - all I had to do was enter my static IP details!  Is there any way to achieve the same functionality with the Solos 4 port?

Thanks in advance,
Andy

[andyp]

Does anyone have any ideas?

I've updated the system (apt-get update and apt-get upgrade) but the card is still not dected (via Zentyal or ifconfig).

As mentioned the driver should be included in the kernel but is also supplied on sourceforge (http://sourceforge.net/projects/openadsl/).  Any help appreciated.

Cheers.

[FutureTechSys]

I'd do some googling for "Ubuntu" versus Zentyal... like "Ubuntu Solos ADSL2 Modem" or something - I have found with hardware you have to do it command line

[andyp]

Hi FutureTechSys,

Thanks for your reply.  Unfortunately this did not turn up anything useful and I am still unable to use my card.  This is extremely disappointing as I bought this card specifically because the driver is included in kernel versions 2.6.29 and higher.

The PDF that came with the card can be found online if this helps anyone:
http://www.traverse.com.au/downloads/adsl/solos_manual-0.3.pdf

To check my kernel settings I installed the following:

Code: [Select]

sudo apt-get install fakeroot kernel-wedge build-essential makedumpfile kernel-package libncurses5 libncurses5-dev
And then ran:

Code: [Select]

cd /usr/src/linux-headers-2.6.32-25-pae

Code: [Select]

make menuconfig
This enabled me to see that everything is as the manual asks for under "3 - Kernel Configuration" - including:

Device Drivers --> Network Device Support --> ATM Drivers (new) --> Solos ADSL2+ PCI Multiport Card Driver

Am I missing something?  The solos-pci modules already seems to be installed as a module already.

[andyp]

If I check /var/log/kern.log, it appears the driver has been loaded:

Code: [Select]

Oct 19 23:40:55 wellington kernel: [    6.860110] Solos PCI Driver Version 0.07
Oct 19 23:40:55 wellington kernel: [    6.860149]   alloc irq_desc for 21 on node -1
Oct 19 23:40:55 wellington kernel: [    6.860152]   alloc kstat_irqs on node -1
Oct 19 23:40:55 wellington kernel: [    6.860160] solos 0000:11:00.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
Oct 19 23:40:55 wellington kernel: [    6.860197] solos 0000:11:00.0: Solos FPGA Version 0.03 svn-38
Oct 19 23:40:55 wellington kernel: [    6.860334] solos 0000:11:00.0: Registered ATM device 0
Oct 19 23:40:55 wellington kernel: [    6.880175] solos 0000:11:00.0: Registered ATM device 1
Oct 19 23:40:55 wellington kernel: [    6.880294] solos 0000:11:00.0: Registered ATM device 2
Oct 19 23:40:55 wellington kernel: [    6.880408] solos 0000:11:00.0: Registered ATM device 3

Yet no interface has been created for the device!

[FutureTechSys]

at a terminal do "ifconfig -a" and post back.  I've had it where ubuntu created the interfaces, but they didn't appear in Zentyal.

[andyp]

Hi,

Thanks for your reply.  Unfortunately the card does not appear under 'ifconfig -a'.  Interface eth0 is just a normal NIC.

Code: [Select]

eth0   Link encap:Ethernet  HWaddr 78:e7:d1:53:6a:df 
          inet addr:192.168.1.67  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::7ae7:d1ff:fe53:6adf/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:106 errors:0 dropped:0 overruns:0 frame:0
          TX packets:89 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:19317 (19.3 KB)  TX bytes:16405 (16.4 KB)
          Interrupt:17

lo       Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:14512 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14512 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2611333 (2.6 MB)  TX bytes:2611333 (2.6 MB)

I'm really not sure what else to try or where else to look?

Cheers.

[andyp]

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

[exekias]

Hi Andyp,

Although your scripts seems ok I think you are launching it too late, when Zentyal has already configured the network. I think you need to launch it before, maybe using /etc/rc.local or other init start config:

Code: [Select]

start on started networking
That is enabling your interface after Zentyal has configured everything

You can also can try with a hook, take a look to our doc:

http://doc.zentyal.org/en/develop.html?highlight=hook#service-advanced-customization

Best regards

[andyp]

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

[andyp]

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


[andyp]

Please help if you can!

[exekias]

Hi Andyp,

I don't understand, your problem now is you are not able to see the interfaces on the admin page?

Best regards

[andyp]

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

[exekias]

Hi,

Here a hint, by default Zentyal only see interfaces with this names (see /usr/share/perl5/EBox/Network.pm):

Code: [Select]

use constant ALLIFACES => qw(sit tun tap lo irda eth wlan vlan);

And ignore this ones in the interface:

Code: [Select]

use constant IGNOREIFACES => qw(sit tun tap lo irda ppp);

You have 2 options, you can change that code and restart apache:

/etc/init.d/ebox apache restart

or you can change the name of your virtual interface to one that fits (this options is better because it is compatible with future upgrades of ebox-network)