> > The strange thing is I had the internet connection
> up
> > and running until my provider changed to the
> > RFC1483 protocol. So modem_run must have worked
> > fine, because it only brings the modem "up" right?
> > I found a patch for the speedtouch-start script
> > I used, but I needed the bridging utility br2684
> and
> > the module speedtch for that. I compiled the
> kernel
> > according to:
> >
> Yes and no
> you could too manage with modem_run and pppoa3
> called in bridged modem with
> some code like
>       if [ "$PROTOCOL" = "RFC1483" ]; then
>               iface="tap0"
>               /sbin/modprobe tun
>               /usr/sbin/pppoa3 -b -c -m 1 -vpi $VPI -vci $VCI
>               sleep 2
>               /sbin/ifconfig $iface up
>       fi
> but you need to have tun module available
> then you could start pppoe with tap0 interface
> 
> There is far more than one way to connect with
> speedtouch, and this is the most
> subject to problems when mixing incorrectly one
> how-to with another.

yes, I agree that mixing one HOW-TO with another
is not very wise, but that is what you usually
do when things don't work. But isn't true that
modem_run is independent of the connection protocol?
I should be able to run modem_run even if I can't
make a connection after that. I really don't under-
stand why modem_run returns zero if I use the 
correct firmware... 
> ...
> > "modem_run" right? I don't think this should
> > depend on the extra modules I compiled in the
> kernel.
> >
> it is easier to follow what happen when features are
> compiled as modules.
> You could load/unload modules and not have some
> warning when modules compiled in
> kernel.
> 
> 
> Gilles
> 
> Liste de diffusion modem ALCATEL SpeedTouch USB
> Pour se désinscrire :
>
mailto:[EMAIL PROTECTED]
> 
>       
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Liste de diffusion modem ALCATEL SpeedTouch USB
Pour se désinscrire : mailto:[EMAIL PROTECTED]

        

Reply via email to