November 13, 2009 at 10:44 pm #42039
When we first tested ZS, we were using some real old HP hardware with usb Cisco/Linsys ethernet adapters. They came up as generic…but they worked great.
Now we have moved to a smaller, newer asus unit, and here’s what happens.
We boot from a flash card…and the USB nic never shows up…yet the onboard NIC shows fine. On the USB nic itself…no link lights. If I unplug the nic from the back of the machine, and plug it back in…the link lights come on…but ZS does not see it in the GUI.
Since I’m not sure the flavor of linux…how does one get this to refresh so the USB NIC is seen and can this be done in one of the startup scripts so we don’t need to do it afterward?
TPNovember 16, 2009 at 9:10 am #49106
Check if there is something to be configured on the BIOS.
After the ZS is booted check in a shell if the network interface has been recognized.
then check if the corresponding module is loaded.
then check if the interface is working
If you cannot find something
dmesg | grep ETH
might prove helpful for locating your device name.November 16, 2009 at 3:01 pm #49107
Well…we run the lsusb and we see the device at 0b95:7720 (we know this because if we remove it…and rerun lsusb…it is missing)
I look that up and it actually turns out to be
vendor: 0b95 (“ASIX Electronics Corp.”), product: 7720 (“AX88772”)
LSMOD however shows nothing about the usb ehternet device nor asix.
I do a search on the ZS box and I find in /cdrom/modules/184.108.40.206/kernel/drivers/net/usb/asix.ko but I’m not sure how to load it..and more importantly…how to get it to auto load each time.
ifconfig comes back with the info about the onboard nic, the dummy1 conncetion, and the built in VPN connection…but no USB (because there is no mod loaded for it I would assume.)
The GREP command comes back with info only about eth00…specifically r8169 : ETH00: link up.
So…what does one need to do to get the module to load for this usb nic?
All help is greatly appreciated.
TPNovember 16, 2009 at 3:59 pm #49108
Probably the kernel is too old, or the drivers are missing, look for wich module is using in any ordinary linux distribution. i.e. voyage.hk (doing an lsmod should help too)
Once you’ve got the module name, look for it in zeroshell it should be in /lib/usb or /lib/netNovember 16, 2009 at 5:43 pm #49109
Well…we found the asix.ko in cdrom/modules/220.127.116.11/kernel/drivers/net/usb/asix.ko
if I manually do an insmod cdrom/modules/18.104.22.168/kernel/drivers/net/usb/asix.ko
and then an ifconfig -a…a new connection called eth0 shows up…and the mac address matches the device.
but if I hit freresh in the web gui…I see no network interface of eth0.
So…my question is this…
1. Why would it not show up in the web gui?
2. what do I need to do to make sure this asix.ko actually loads each time?
I’m so close…I can taste it!!
THanks for everyone’s help to this point!!
TPNovember 16, 2009 at 11:14 pm #49110
I was not able to find where to add it exactly to make sure it is loaded upon boot. Maybe you could try in
/etc/rc.d/init.d/pciprobeNovember 17, 2009 at 3:53 pm #49111
Please forgive my sheer ignorance in these matters.
I guess before I try to get it to load every time, I need to know how to get it to show up in the gui. The ifconfig shows the adapter, yet the web console will not show it. I notice the naming of the primary connection in the console is ETH00, and this new one shows up as eth0…possibly a conflict?
If anyone knows where to name this connection and how to refresh it in the gui, I would be greatly appreciative.
TPNovember 17, 2009 at 11:05 pm #49112
I guess that the interface MUST exist before the gui is started, so you should make sure the module is loaded along with the other interfaces’ modules.August 26, 2010 at 7:46 am #49113
It wasn’t clear that this was resolved, but I’ve written a howto for this here:
You must be logged in to reply to this topic.