Menu
▾
▴
#362 Driver for BiPAC7000 Modem
Hi!
Are there any chance that IPCOP will support the BiPAC
7000 ADSL Modem? The vendor (Billion.Com) has already
provided the driver for Linux. It can be reached here
>>
http://60.248.77.180/_Internet/fd/bipac-7000/bipac-7000Linuxstandard.zip
Logged In: YES
user_id=691649
It should work already with include 'Connexant usb' driver.
Have you tested this?
Logged In: YES
user_id=1415768
Yes, I have tested that driver (Conexant USB). It can detect
the carrier and line speed (I saw that from the message when
I try loading the firmware with cxload manually) but failed
when sending the LCP ConfReq. Finally, it end up with the
"Timeout waiting for PADO packets".
What I saw it the log file is something like:
Oct 20 15:30:29 troll pppd[6574]: pppd 2.4.2 started by
root, uid 0
Oct 20 15:30:29 troll pppd[6574]: using channel 12
Oct 20 15:30:29 troll pppd[6574]: Using interface ppp0
Oct 20 15:30:29 troll pppd[6574]: Connect: ppp0 <--> /dev/pts/1
Oct 20 15:30:30 troll pppd[6574]: sent [LCP ConfReq id=0x1
<mru 1492> <magic 0xf8ef24b1>]
Oct 20 15:31:03 troll last message repeated 11 times
Oct 20 15:31:04 troll pppoe[6575]: Timeout waiting for PADO
packets
I've successfully tested the same line with Zyxel 630-11
Modem. So, it should not the problem on the communication
line. Any suggestion?
Logged In: YES
user_id=1041094
Originator: NO
>I've successfully tested the same line with Zyxel 630-11
>Modem. So, it should not the problem on the communication
>line. Any suggestion?
under IPCop?
waiting pado packet:
the ppp server don't receive/reply requests. The link
is UP so probably, it is a configuration problem.
pppOA? VPI/VCI?
Franck
Logged In: YES
user_id=1415768
Originator: YES
Yes. The test was running on the IPCop. I just simply replaced the BiPAC7000 Modem with Zyxel 630-11 and reconfigure IPCop using the same line configuration value (PPPoE, LLC and the same VPI/VCI), and it works. Also, I've tested this BiPAC7000 Modem on my RedHat Linux using it's original driver and it works fine. So, I assume that the problem should be at the IPCop's driver.
FYI - the original driver provide a web interface for the user to configure the line configuration. The PPP initiation and login (both CHAP and PAP are supported) are done by the driver on the modem itself. I don't need any PPP daemon on my Linux box to connect to the internet.
Also, there is other driver on Linux side (a module called e2.o) to be loaded. Once loaded, it creates an interface (called hsb0 - on my system) with an IP address. All the traffic to the modem configuration interface and internet must be routed to this interface.
Logged In: YES
user_id=691649
Originator: NO
I know the cnxadsl driver may be sometime unreliable as I have tested with Olitec modem and it has work at some attempts but not all.
As this Olitec modem had RX and TX leds, I know by the leds that some data goes in and out from the modem but pppd look to not receive anything.
In that case, the only workaround I find was to reset usb and reload the driver.
The driver with e2.o use a different firmware with ethernet interface to the modem and only work with modems shipped with more memories. Older modems only support firmware with atm interface and smaller memory footprint.
Some vulnerabilities has been discovered on the web interface to configure this big firmware/ ethernet modem. I don't know if it has been fixed. As it is a closed source package, it is difficult to know what has been changed.
For simplicity and as not able to maintain ethernet big firmware web interface, developpers of the open source driver have choosen to offer an universal solution based only on small firmware/atm interface.
A derivative of this work has been made and this new driver based on usbatm has been include in 2.6 kernel (2.6.15 if I remember well). There is probably fixes in this driver that could be backported on the first driver(firmware patch, maybe other parts).
This could be the solution to the problem with some of the supported modems that are not reliabily supported actually by cnxadl.
Another solution could have be to use a 2.6 kernel but development of IPCop v1.5 is too slow and I have no free time actually for that.
I am not inclined to include a driver wich is not maintained and not maintainable, particulary when an open source driver is available. Fixes have to be made against the open source driver.
Logged In: YES
user_id=1415768
Originator: YES
OK, that fine to me. I can wait for the version 1.5. Thanks for your help!