I got a tcpdump trace on the init and nego exchange
for both the kernel driver and the userspace driver,
and there's a difference.

(see http://en.wikipedia.org/wiki/Pppoe for background
info)

Both kernel and userspace start with sending a PADI.
ISP sends back a PADO with the AC-name and a
relay-session-id.
Both kernel and userspace responds with a PADR,
however the userspace sends back the relay-session-id
where the kernel driver does not.
The userspace continues the nego successfully. The
kernel driver simply re-tries the PADR again unchanged
after no response from ISP.

Is there a way to get the pppoe(4) to include the
relay-session-id in the PADR packet?

Thanks,


      
____________________________________________________________________________________
Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs

Reply via email to