pppd (initially) fails to negotiate PPPoE connection

I'm trying to connect to an ADSL modem under SuSE 9.0 (rp-pppoe-3.5,
smpppd-1.06, ppp-2.4.1). When I use the original SuSE kernel 2.4.21,
everything works fine:

pppd[8098]: Plugin pppoe.so loaded.
pppd[8098]: PPPoE Plugin Initialized
pppd[8098]: Plugin passwordfd.so loaded.
pppd[8098]: pppd 2.4.1 started by root, uid 0
pppd[8098]: Sending PADI
pppd[8098]: HOST_UNIQ successful match
pppd[8098]: HOST_UNIQ successful match
pppd[8098]: Got connection: b6e
pppd[8098]: Connecting PPPoE socket: 00:90:1a:40:df:1a 6e0b eth0 0x8089
pppd[8098]: Using interface ppp0
pppd[8098]: Connect: ppp0 <--> eth0
pppd[8098]: Setting MTU to 1492.
pppd[8098]: Couldn't increase MRU to 1500
pppd[8098]: Setting MTU to 1492.
...
pppd[8098]: Script /etc/ppp/ip-up finished (pid 8131), status = 0x0

But when I start my self-compiled 2.6.9, pppd fails:

pppd[1951]: PPPoE Plugin Initialized
pppd[1951]: Plugin passwordfd.so loaded.
pppd[1951]: pppd 2.4.1 started by root, uid 0
pppd[1951]: Sending PADI
pppd[1951]: HOST_UNIQ successful match
pppd[1951]: Failed to negotiate PPPoE connection: 25 Inappropriate ioctl for device
pppd[1951]: Exit.

However, if I simply wait until booting is finished, and restart the
network service later, pppd suddenly succeeds again. What might cause
this? Does the newer kernel export some functionality into a module
that I do not load soon enough, or does it try to do one thing after
another faster then the old one?

--
No animal was harmed in the making of this post.



Kilian A. Foth

"Kilian A. Foth" <(E-Mail Removed)> writes:


>I'm trying to connect to an ADSL modem under SuSE 9.0 (rp-pppoe-3.5,
>smpppd-1.06, ppp-2.4.1). When I use the original SuSE kernel 2.4.21,
>everything works fine:

> pppd[8098]: Plugin pppoe.so loaded.
> pppd[8098]: PPPoE Plugin Initialized
> pppd[8098]: Plugin passwordfd.so loaded.
> pppd[8098]: pppd 2.4.1 started by root, uid 0
> pppd[8098]: Sending PADI
> pppd[8098]: HOST_UNIQ successful match
> pppd[8098]: HOST_UNIQ successful match
> pppd[8098]: Got connection: b6e
> pppd[8098]: Connecting PPPoE socket: 00:90:1a:40:df:1a 6e0b eth0 0x8089
> pppd[8098]: Using interface ppp0
> pppd[8098]: Connect: ppp0 <--> eth0
> pppd[8098]: Setting MTU to 1492.
> pppd[8098]: Couldn't increase MRU to 1500
> pppd[8098]: Setting MTU to 1492.
> ...
> pppd[8098]: Script /etc/ppp/ip-up finished (pid 8131), status = 0x0

>But when I start my self-compiled 2.6.9, pppd fails:

> pppd[1951]: PPPoE Plugin Initialized
> pppd[1951]: Plugin passwordfd.so loaded.
> pppd[1951]: pppd 2.4.1 started by root, uid 0
> pppd[1951]: Sending PADI
> pppd[1951]: HOST_UNIQ successful match
> pppd[1951]: Failed to negotiate PPPoE connection: 25 Inappropriate ioctl for device
> pppd[1951]: Exit.

>However, if I simply wait until booting is finished, and restart the
>network service later, pppd suddenly succeeds again. What might cause
>this? Does the newer kernel export some functionality into a module
>that I do not load soon enough, or does it try to do one thing after
>another faster then the old one?

Probably timing. Some program is not up during the boot sequence when you
start pppd that pppd needs. Eg networking.



>--
>No animal was harmed in the making of this post.