i386/75165: if ng_pppoe switches to nonstandard mode it stays in it
forever but not on ver. 4.7
Adrian Baran
route at lviv.farlep.net
Thu Dec 16 11:10:21 PST 2004
>Number: 75165
>Category: i386
>Synopsis: if ng_pppoe switches to nonstandard mode it stays in it forever but not on ver. 4.7
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: freebsd-i386
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: change-request
>Submitter-Id: current-users
>Arrival-Date: Thu Dec 16 19:10:20 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator: Adrian Baran
>Release: 5.1, 5.2.1
>Organization:
ISP Farlep Lviv Telecom
>Environment:
FreeBSD server.reha.int 5.1-RELEASE FreeBSD 5.1-RELEASE #8: Mon Dec 13 11:37:51 EET 2004 adrian at server.reha.int:/usr/src/sys/i386/compile/COMM i386
>Description:
Look like the same bug as described in
http://www.freebsd.org/cgi/query-pr.cgi?pr=47920
but on FreeBSD 5.1, 5.2.1 : PPPoE client (user level ppp) switches to nonstandart PPPoE mode. FreeBSD version 4.10 in the same ethernet segment (also using PPPoЕ to connect to internet), directly after dropping connection to buggy system with 5.1 writes to /var/log/messages /kernel: Ignored nonstandard PPPoE packet from
>How-To-Repeat:
Reboot is only realy tested to resolve this trouble.
I'll try to set "sysctl net.graph.nonstandard_pppoe=0" in crontab
Hops this work. Other way is to use another PPPoE client but i do'nt now any that is not using NETGRAPH .
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-i386
mailing list