Matthew Emmerton writes:
> Any ideas on why doing an 'ifconfig rl0 up' before starting PPP (using set
> device PPPoE:rl0) would cause this problem? (These machines are running
> 4.3-REL-p20)
There is a kernel bug in 4.3 where certain interfaces can't deal
with an outgoing packet appearing while
On Thu, 22 Nov 2001 14:36:37 + (UTC), in sentex.lists.freebsd.net you
wrote:
>Thanks for all who replied to this thread, indicating that a bad cable was
>likely the culprit.
>
>In this case, changing the cable didn't help, but commenting out the
>"ifconfig_rl0='up'" line in /etc/rc.conf fixed
Thanks for all who replied to this thread, indicating that a bad cable was
likely the culprit.
In this case, changing the cable didn't help, but commenting out the
"ifconfig_rl0='up'" line in /etc/rc.conf fixed the problem.
Any ideas on why doing an 'ifconfig rl0 up' before starting PPP (using s
the way to debug this is to run tcpdump on the ethernet card in question
tcpdump knows how to interpret pppoe packets
and it's good to see what is coming over from the other end..
On Tue, 20 Nov 2001 [EMAIL PROTECTED] wrote:
>
> > What is happening is that when ppp starts on bootup (ppp -quie
>
> > What is happening is that when ppp starts on bootup (ppp -quiet -ddial
> > pppoe), the last entry is "dial -> carrier" and nothing else. Normally
>
> Looks like that the ethernet connection between your host and the modem is
> broken. I get the same message when I unplug my ethernet wire.
> What is happening is that when ppp starts on bootup (ppp -quiet -ddial
> pppoe), the last entry is "dial -> carrier" and nothing else. Normally
Looks like that the ethernet connection between your host and the modem is
broken. I get the same message when I unplug my ethernet wire.
Cheers
Mar
