Re: Possible DoS in mpd 5.6 pppoe server
On 05.05.2013 07:51, Marcelo Gondim wrote: I changed hardware for motherboard Supermicro X9SCM-F and Xeon processor 3.2Ghz E31230 with 8Gb ram ECC. The problem stopped and the server was very stable. The problem could be with the Intel motherboard S5500BC? Because this was installed with 2 Xeon processors and two memory banks 4Gb. Could be FreeBSD incompatibility with the hardware or faulty hardware? Thanks and best regards, I don't think so. The race problem is known. It has software nature and crash probability depends of many reasons. The change of hardware changes some of aspects, indeed :-) In your case it somehow made the server more stable but that's not any kind of hardware incompatibility. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Possible DoS in mpd 5.6 pppoe server
Em 05/05/13 04:21, Eugene Grosbein escreveu: On 05.05.2013 07:51, Marcelo Gondim wrote: I changed hardware for motherboard Supermicro X9SCM-F and Xeon processor 3.2Ghz E31230 with 8Gb ram ECC. The problem stopped and the server was very stable. The problem could be with the Intel motherboard S5500BC? Because this was installed with 2 Xeon processors and two memory banks 4Gb. Could be FreeBSD incompatibility with the hardware or faulty hardware? Thanks and best regards, I don't think so. The race problem is known. It has software nature and crash probability depends of many reasons. The change of hardware changes some of aspects, indeed :-) In your case it somehow made the server more stable but that's not any kind of hardware incompatibility. Does any developer is seeing this problem? Because I saw the prthat has been going on since 2011. http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/162558 I'm trying to replace severalMikrotik RouterOS (PPPoE server) for FreeBSD with mpd + freeradius + mysql. All my servers are FreeBSD except PPPoE Server. :( Best regards, ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Possible DoS in mpd 5.6 pppoe server
Em 21/04/13 10:59, Eugene Grosbein escreveu: On 21.04.2013 06:08, Marcelo Gondim wrote: Em 20/04/13 14:33, Eugene Grosbein escreveu: On 21.04.2013 00:26, Marcelo Gondim wrote: You seem to use dummynet and the problem is not in mpd/pppoe code, it's it the dummynet code. Look at http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/162558 for workarounds. Ok :) I will try this: - net.isr.bindthreads=1 in /boot/loader.conf; - net.isr.direct=1 and net.isr.direct_force=1 in /etc/sysctl.conf For 9.x and newer, net.isr.XXX knobs names have changed but defaults are fine - if you have not messed them, you should be OK. Eugene, Does FreeBSD 8.3-STABLEis best for this use or this problem also occurs in 8.x? I have not tried anything newer than 8.x for this task yet. With noted tuning, this problem within dummynet occurs very seldom for me. I had about two or three panics for many months. Another one described here: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/171711 Perhaps, using ng_car would be even more stable, I have not tried it. Eugene Grosbein Hi all, I changed hardware for motherboard Supermicro X9SCM-F and Xeon processor 3.2Ghz E31230 with 8Gb ram ECC. The problem stopped and the server was very stable. The problem could be with the Intel motherboard S5500BC? Because this was installed with 2 Xeon processors and two memory banks 4Gb. Could be FreeBSD incompatibility with the hardware or faulty hardware? Thanks and best regards, Gondim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Possible DoS in mpd 5.6 pppoe server
Marcelo, On Sat, Apr 20, 2013 at 02:26:10PM -0300, Marcelo Gondim wrote: M I'm doing tests with mpdas pppoeserver. Tried to simulate an attack of M 1000 connections using an incorrect login and after a certain time can M cause a kernel panic in the system. Below the panicgenerated: M M http://pastebin.com/nUXGVR3y M You seem to use dummynet and the problem is not in mpd/pppoe code, M it's it the dummynet code. Look at http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/162558 M for workarounds. M Ok :) I will try this: M M - net.isr.bindthreads=1 in /boot/loader.conf; M - net.isr.direct=1 and net.isr.direct_force=1 in /etc/sysctl.conf Be advised, that these settings do not fix the problem with dummynet, they just make the race less probable to happen. -- Totus tuus, Glebius. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Possible DoS in mpd 5.6 pppoe server
On 21.04.2013 06:08, Marcelo Gondim wrote: Em 20/04/13 14:33, Eugene Grosbein escreveu: On 21.04.2013 00:26, Marcelo Gondim wrote: You seem to use dummynet and the problem is not in mpd/pppoe code, it's it the dummynet code. Look at http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/162558 for workarounds. Ok :) I will try this: - net.isr.bindthreads=1 in /boot/loader.conf; - net.isr.direct=1 and net.isr.direct_force=1 in /etc/sysctl.conf For 9.x and newer, net.isr.XXX knobs names have changed but defaults are fine - if you have not messed them, you should be OK. Eugene, Does FreeBSD 8.3-STABLEis best for this use or this problem also occurs in 8.x? I have not tried anything newer than 8.x for this task yet. With noted tuning, this problem within dummynet occurs very seldom for me. I had about two or three panics for many months. Another one described here: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/171711 Perhaps, using ng_car would be even more stable, I have not tried it. Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Possible DoS in mpd 5.6 pppoe server
Hi all, I'm doing tests with mpdas pppoeserver. Tried to simulate an attack of 1000 connections using an incorrect login and after a certain time can cause a kernel panic in the system. Below the panicgenerated: http://pastebin.com/nUXGVR3y Other equipment I do: # for (( i=0; i 1000; i++ )); do ppp -ddial intnet ; done My System: Intel Motherboard Server S5500BC with Dual Processor Xeon(R) CPU E5606 @ 2.13GHz 8Gb ram I do not understand programming in Cor Assembly. But could someone tell me if what happened was a system problem or hardware? Best regards, Gondim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Possible DoS in mpd 5.6 pppoe server
Can you provide more information about the configuration of mpd and ppp? the panic is in the dummynet code; can you provide information about your ipfw/dummynet setup? Thanks, adrian On 20 April 2013 06:21, Marcelo Gondim gon...@bsdinfo.com.br wrote: Hi all, I'm doing tests with mpdas pppoeserver. Tried to simulate an attack of 1000 connections using an incorrect login and after a certain time can cause a kernel panic in the system. Below the panicgenerated: http://pastebin.com/nUXGVR3y Other equipment I do: # for (( i=0; i 1000; i++ )); do ppp -ddial intnet ; done My System: Intel Motherboard Server S5500BC with Dual Processor Xeon(R) CPU E5606 @ 2.13GHz 8Gb ram I do not understand programming in Cor Assembly. But could someone tell me if what happened was a system problem or hardware? Best regards, Gondim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Possible DoS in mpd 5.6 pppoe server
On 20.04.2013 20:21, Marcelo Gondim wrote: Hi all, I'm doing tests with mpdas pppoeserver. Tried to simulate an attack of 1000 connections using an incorrect login and after a certain time can cause a kernel panic in the system. Below the panicgenerated: http://pastebin.com/nUXGVR3y You seem to use dummynet and the problem is not in mpd/pppoe code, it's it the dummynet code. Look at http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/162558 for workarounds. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Possible DoS in mpd 5.6 pppoe server
Hi Adrian, Thanks for your help. :) My mpd.conf: startup: # configure mpd users #set user foo bar admin set user suporte papatango set user admin tutumineiro admin # configure the console set console self 192.168.8.34 5005 set console open # configure the web server set web self 0.0.0.0 5006 set web open default: load pppoe_server pppoe_server: create bundle template B set iface disable proxy-arp set iface enable tcpmssfix set ipcp dns 8.8.8.8 8.8.4.4 #set ipcp enable vjcomp set iface up-script /usr/local/etc/mpd5/addclient.sh set iface down-script /usr/local/etc/mpd5/removeclient.sh set ippool add pool1 10.10.0.1 10.10.255.254 set ipcp ranges 10.51.0.1/32 ippool pool1 create link template common pppoe #set link enable multilink set link action bundle B set link disable chap pap eap set link mtu 1492 set link mru 1492 set link enable pap load radius create link template igb1 common set pppoe iface igb1 set pppoe acname IntBSD1 set pppoe service * set link enable incoming set auth max-logins 1 set link max-children 5000 create link template igb2 common set pppoe iface igb2 set pppoe acname IntBSD2 set pppoe service * set link enable incoming set auth max-logins 1 set link max-children 5000 create link template igb3 common set pppoe iface igb3 set pppoe acname IntBSD3 set pppoe service * set link enable incoming set auth max-logins 1 set link max-children 5000 radius: set radius server localhost xuxupedra 1812 1813 set radius retries 3 set radius timeout 3 # send the given IP in the RAD_NAS_IP_ADDRESS attribute to the server. set radius me 127.0.0.1 # send accounting updates every 5 minutes set auth acct-update 300 # enable RADIUS, and fallback to mpd.secret, if RADIUS auth failed set auth enable radius-auth # enable RADIUS accounting set auth enable radius-acct # protect our requests with the message-authenticator set radius enable message-authentic My ppp.conf: intnet: set device PPPoE:re0 set mru 1492 set mtu 1492 set authname hercilia201254 set authkey 12345 set login set dial enable dns add default HISADDR set timeout 0 open The test server is off now, but I'll get ipfw and dummynet settings in the Companyand post it here. Em 20/04/13 11:48, Adrian Chadd escreveu: Can you provide more information about the configuration of mpd and ppp? the panic is in the dummynet code; can you provide information about your ipfw/dummynet setup? Thanks, adrian On 20 April 2013 06:21, Marcelo Gondim gon...@bsdinfo.com.br wrote: Hi all, I'm doing tests with mpdas pppoeserver. Tried to simulate an attack of 1000 connections using an incorrect login and after a certain time can cause a kernel panic in the system. Below the panicgenerated: http://pastebin.com/nUXGVR3y Other equipment I do: # for (( i=0; i 1000; i++ )); do ppp -ddial intnet ; done My System: Intel Motherboard Server S5500BC with Dual Processor Xeon(R) CPU E5606 @ 2.13GHz 8Gb ram I do not understand programming in Cor Assembly. But could someone tell me if what happened was a system problem or hardware? Best regards, Gondim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Possible DoS in mpd 5.6 pppoe server
Em 20/04/13 13:10, Eugene Grosbein escreveu: On 20.04.2013 20:21, Marcelo Gondim wrote: Hi all, I'm doing tests with mpdas pppoeserver. Tried to simulate an attack of 1000 connections using an incorrect login and after a certain time can cause a kernel panic in the system. Below the panicgenerated: http://pastebin.com/nUXGVR3y You seem to use dummynet and the problem is not in mpd/pppoe code, it's it the dummynet code. Look at http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/162558 for workarounds. Ok :) I will try this: - net.isr.bindthreads=1 in /boot/loader.conf; - net.isr.direct=1 and net.isr.direct_force=1 in /etc/sysctl.conf ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Possible DoS in mpd 5.6 pppoe server
On 21.04.2013 00:26, Marcelo Gondim wrote: You seem to use dummynet and the problem is not in mpd/pppoe code, it's it the dummynet code. Look at http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/162558 for workarounds. Ok :) I will try this: - net.isr.bindthreads=1 in /boot/loader.conf; - net.isr.direct=1 and net.isr.direct_force=1 in /etc/sysctl.conf For 9.x and newer, net.isr.XXX knobs names have changed but defaults are fine - if you have not messed them, you should be OK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Possible DoS in mpd 5.6 pppoe server
Hi,
My ipfw rules, pf rules and dummynet:
fw=/sbin/ipfw
ext_if=igb0
$fw disable one_pass
$fw -f flush
$fw zero
$fw table all flush
$fw -f pipe flush
ssh_port=4321
$fw add allow all from any to any via lo0
$fw add deny all from 127.0.0.0/8 to any
$fw add deny all from any to 127.0.0.0/8
$fw add check-state
# velocidade de 1024kbps
$fw add pipe 1 ip from table(10) to any in via ng*
$fw add pipe 2 ip from any to table(10) out via ng*
$fw pipe 1 config bw 1024Kbit/s queue 128 mask src-ip 255.255.255.255
$fw pipe 2 config bw 1024Kbit/s queue 128 mask dst-ip 255.255.255.255
# velocidade de 2048kbps
$fw add pipe 3 ip from table(11) to any in via ng*
$fw add pipe 4 ip from any to table(11) out via ng*
$fw pipe 3 config bw 2048Kbit/s queue 256 mask src-ip 255.255.255.255
$fw pipe 4 config bw 2048Kbit/s queue 256 mask dst-ip 255.255.255.255
# velocidade de 10240kbps
$fw add pipe 5 ip from table(12) to any in via ng*
$fw add pipe 6 ip from any to table(12) out via ng*
$fw pipe 5 config bw 10240Kbit/s queue 1280 mask src-ip 255.255.255.255
$fw pipe 6 config bw 10240Kbit/s queue 1280 mask dst-ip 255.255.255.255
# velocidade de 64kbps
$fw add pipe 7 ip from table(13) to any in via ng*
$fw add pipe 8 ip from any to table(13) out via ng*
$fw pipe 7 config bw 64Kbit/s queue 8 mask src-ip 255.255.255.255
$fw pipe 8 config bw 64Kbit/s queue 8 mask dst-ip 255.255.255.255
$fw add allow icmp from any to any icmptypes 0,3,8,11,12
$fw add deny icmp from any to any
PF Rules:
===
ext_if = igb0
table masq persist { 10.0.0.0/8 }
set skip on lo0
set limit states 4
nat on $ext_if from masq to any - 192.168.8.34
Em 20/04/13 11:48, Adrian Chadd escreveu:
Can you provide more information about the configuration of mpd and ppp?
the panic is in the dummynet code; can you provide information about
your ipfw/dummynet setup?
Thanks,
adrian
On 20 April 2013 06:21, Marcelo Gondim gon...@bsdinfo.com.br wrote:
Hi all,
I'm doing tests with mpdas pppoeserver. Tried to simulate an attack of 1000
connections using an incorrect login and after a certain time can cause a
kernel panic in the system. Below the panicgenerated:
http://pastebin.com/nUXGVR3y
Other equipment I do:
# for (( i=0; i 1000; i++ )); do ppp -ddial intnet ; done
My System:
Intel Motherboard Server S5500BC with Dual Processor Xeon(R) CPU E5606 @
2.13GHz
8Gb ram
I do not understand programming in Cor Assembly. But could someone tell me
if what happened was a system problem or hardware?
Best regards,
Gondim
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Possible DoS in mpd 5.6 pppoe server
Em 20/04/13 14:33, Eugene Grosbein escreveu: On 21.04.2013 00:26, Marcelo Gondim wrote: You seem to use dummynet and the problem is not in mpd/pppoe code, it's it the dummynet code. Look at http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/162558 for workarounds. Ok :) I will try this: - net.isr.bindthreads=1 in /boot/loader.conf; - net.isr.direct=1 and net.isr.direct_force=1 in /etc/sysctl.conf For 9.x and newer, net.isr.XXX knobs names have changed but defaults are fine - if you have not messed them, you should be OK. Eugene, Does FreeBSD 8.3-STABLEis best for this use or this problem also occurs in 8.x? Best regards, Gondim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.1R: ppp default route uses wrong Netif (with pppoe)
On Thu, Aug 12, 2010 at 07:31:32PM +0400, Michael BlackHeart wrote: As I understand this isn't a bug but a mistype or misunderstand of config ( see man ppp.conf ) I'm running myself 8.0, 8.1 and currently 8.STABLE with pppoe in this way and never have a problem as many peolpe do. Look in listing my-provider: set line PPPoE:nfe0 Here's some set line and should be set device like this: sorry it wasn't that. I checked the source code, set line and set device are perfect equivalent and they end up calling the same code. cheers luigi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.1R: ppp default route uses wrong Netif (with pppoe)
As I understand this isn't a bug but a mistype or misunderstand of config ( see man ppp.conf ) I'm running myself 8.0, 8.1 and currently 8.STABLE with pppoe in this way and never have a problem as many peolpe do. Look in listing my-provider: set line PPPoE:nfe0 Here's some set line and should be set device like this: pppoe_myisp: set device PPPoE:fxp0 I think that's the clue. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
8.1R: ppp default route uses wrong Netif (with pppoe)
Hi, I found the following problem with ppp after upgrading to 8.1 I am using ppp -ddial -nat ... over pppoe. The entry in ppp.conf has these lines (plus others not relevant here): my-provider: set line PPPoE:nfe0 ... add default HISADDR Up to 7.2 this sufficed to establish a route using 'tun0' as the device DestinationGatewayFlagsRefs Use Netif Expire default81.174.0.1 UGS 0 1885 tun0 With the upgrade to 8.1R the default route points to 'nfe0', i.e. the device used to talk pppoe, instead of tun0. This causes a number of failures which prevent operation. I am not sure though whether the bug is in PPP or in the kernel, and why ppp now uses the wrong device to install the route entry. A functional workaround is the following (note you need all three lines!): add default HISADDR shell route delete default shell route add default -interface INTERFACE where the first line installs the bogus entry but supplies a default address for outgoing packets, and the other two entries fix the interface. I tried to remove the 'add default HISADDR' but it does not seem to work -- tcpdump shows outgoing packets carrying 0.0.0.0 as src-ip, which prevents replies from coming back. I'll submit a PR later, but would be curious to know if someone has ideas on what could be a proper fix. cheers luigi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.1R: ppp default route uses wrong Netif (with pppoe)
Luigi Rizzo ri...@iet.unipi.it wrote: Hi, I found the following problem with ppp after upgrading to 8.1 I am using ppp -ddial -nat ... over pppoe. The entry in ppp.conf has these lines (plus others not relevant here): my-provider: set line PPPoE:nfe0 ... add default HISADDR Up to 7.2 this sufficed to establish a route using 'tun0' as the device DestinationGatewayFlagsRefs Use Netif Expire default81.174.0.1 UGS 0 1885 tun0 With the upgrade to 8.1R the default route points to 'nfe0', i.e. the device used to talk pppoe, instead of tun0. This causes a number of failures which prevent operation. That's strange ... I have a simuilar setup on my router which was upgraded from FreeBSD 6.x to 8.x recently. I don't have any routing problems. So maybe it is a problem with your configuration, not a FreeBSD bug. My rc.conf contains: ifconfig_fxp0=up ppp_enable=YES ppp_mode=ddial ppp_nat=YES ppp_profile=pppoe_myisp gateway_enable=YES And ppp.conf looks like this (few things omitted for brevity): default: set ifaddr 10.0.0.1/0 10.0.0.2/0 set server /var/run/ppp.ctl 0177 nat enable yes pppoe_myisp: set device PPPoE:fxp0 set authname myauthname set authkey myauthkey set dial set login add default HISADDR enable dns resolv readonly The default route is set correctly: $ route get default route to: default destination: default mask: default gateway: gateway.myisp.net interface: tun0 flags: UP,GATEWAY,DONE,STATIC recvpipe sendpipe ssthresh rtt,msecmtuweightexpire 0 0 0 0 1492 1 0 Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd Blogging: Never before have so many people with so little to say said so much to so few. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: pppoe on a VLAN interface issues (RELENG_7)
2009/7/9 Mike Tancsa m...@sentex.net Jul 9 14:34:17 fw02 kernel: ng_ether_attach: can't name node em1.10 Jul 9 14:34:17 fw02 kernel: ng_ether_attach: can't name node em1.172 Jul 9 14:34:17 fw02 kernel: ng_ether_attach: can't name node em1.24 Is there some reason this does not work ? reason - interfaces names with . :) -- WBR, Виталий Моисеев, v...@vm.net.ua Nick-hdl: VM347-RIPE, VM265-UANIC ICQ# 111222168 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: pppoe on a VLAN interface issues (RELENG_7)
2009/7/9 Mike Tancsa m...@sentex.net Jul 9 14:34:17 fw02 kernel: ng_ether_attach: can't name node em1.10 Jul 9 14:34:17 fw02 kernel: ng_ether_attach: can't name node em1.172 Jul 9 14:34:17 fw02 kernel: ng_ether_attach: can't name node em1.24 Is there some reason this does not work ? reason - names of interfaces with . :) -- WBR, Виталий Моисеев, v...@vm.net.ua Nick-hdl: VM347-RIPE, VM265-UANIC ICQ# 111222168 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
pppoe on a VLAN interface issues (RELENG_7)
I wanted to share a DSL modem that is in bridge mode between two FreeBSD boxes that make use of many VLANs on a pair of em interfaces. In other words, I cant dedicate a physical interface to just using the DSL. Normally, when creating vlans, I like to create them as so /sbin/ifconfig em1.172 create 192.168.1.3/24 em1.172: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=3RXCSUM,TXCSUM ether 00:30:48:d2:d6:11 inet 192.168.1.3 netmask 0xff00 broadcast 192.168.1.255 media: Ethernet autoselect (1000baseTX full-duplex) status: active vlan: 172 parent interface: em1 However, if I try and bring up pppoe using em1.10 as the PPPoE device, it does not work. Jul 9 14:34:17 fw02 ppp[1484]: tun0: Phase: deflink: closed - opening Jul 9 14:34:17 fw02 kernel: ng_ether_attach: can't name node em1.10 Jul 9 14:34:17 fw02 kernel: ng_ether_attach: can't name node em1.172 Jul 9 14:34:17 fw02 kernel: ng_ether_attach: can't name node em1.24 Jul 9 14:34:17 fw02 kernel: WARNING: attempt to net_add_domain(netgraph) after domainfinalize() Jul 9 14:34:17 fw02 kernel: Jul 9 14:34:17 fw02 kernel: ng_ether_attach: can't name node em1.10 Jul 9 14:34:17 fw02 kernel: Jul 9 14:34:17 fw02 kernel: ng_ether_attach: can't name node em1.172 Jul 9 14:34:17 fw02 kernel: Jul 9 14:34:17 fw02 kernel: ng_ether_attach: can't name node em1.24 Jul 9 14:34:17 fw02 ppp[1484]: tun0: Warning: em1.172: Cannot send a netgraph message: Invalid argument Jul 9 14:34:17 fw02 ppp[1484]: tun0: Chat: Failed to open device Jul 9 14:34:17 fw02 ppp[1484]: tun0: Phase: deflink: Enter pause (30) for redialing. Jul 9 14:34:47 fw02 ppp[1484]: tun0: Chat: deflink: Redial timer expired. Jul 9 14:34:47 fw02 ppp[1484]: tun0: Warning: em1.172: Cannot send a netgraph message: Invalid argument Jul 9 14:34:47 fw02 ppp[1484]: tun0: Warning: deflink: PPPoE: unknown host Jul 9 14:34:47 fw02 ppp[1484]: tun0: Warning: deflink: PPPoE: unknown host Jul 9 14:34:47 fw02 ppp[1484]: tun0: Warning: deflink: Device (PPPoE:em1.172) must begin with a '/', a '!' or contain at least one ':' Jul 9 14:34:47 fw02 ppp[1484]: tun0: Chat: Failed to open device Jul 9 14:34:47 fw02 ppp[1484]: tun0: Phase: deflink: Enter pause (30) for redialing. Jul 9 14:34:50 fw02 ppp[1484]: tun0: Phase: Signal 15, terminate. BUT, if I make the vlan device the old way /sbin/ifconfig vlan172 create 192.168.1.3/24 vlandev em1 vlan 172 it works It still complains about the other 2 interfaces, but it does not seem to interfere with the PPPoE connection Jul 9 14:48:15 macs-fw02 kernel: ng_ether_attach: can't name node em1.10 Jul 9 14:48:15 macs-fw02 kernel: ng_ether_attach: can't name node em1.24 Jul 9 14:48:15 macs-fw02 kernel: Jul 9 14:48:15 macs-fw02 kernel: ng_ether_attach: can't name node em1.10 Jul 9 14:48:15 macs-fw02 kernel: Jul 9 14:48:15 macs-fw02 kernel: ng_ether_attach: can't name node em1.24 Jul 9 14:48:16 macs-fw02 kernel: WARNING: attempt to net_add_domain(netgraph) after domainfinalize() Is there some reason this does not work ? ---Mike Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: problem with PPPoE STABLE and ADSL 3Com HomeConnect
On Mon, Sep 12, 2005 at 08:37:03AM +0200, ComteZero _ wrote: C Hello, C C it's been two weeks I try to find out what's wrong. Clean install from cvsup C STABLE (5). C my ADSL account works fine with REL. 4.4+rp_pppoe but not with my new STABLE C (5) (without using rp_pppoe). C could someone help me on this issue (logs provided here)... two PADI are C emitted but nothing happens after. C (i saw that someone had a similar problem, but with previous netgraph C revisions). C C thank you. C C Since my ADSL modem is 3Com HomeConnect, I've set the C net.graph.nonstandard_pppoe=1 In modern FreeBSD versions 3Com mode for ng_pppoe is switched per-node, not via sysctl. You should use ppp(8) option to enable 3Com mode: set pppoe 3Com -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problem with PPPoE STABLE and ADSL 3Com HomeConnect
With ppp.log in attach file since the email seemed unreadable. On 9/12/05, ComteZero _ [EMAIL PROTECTED] wrote: Hello, it's been two weeks I try to find out what's wrong. Clean install from cvsup STABLE (5). my ADSL account works fine with REL. 4.4+rp_pppoe but not with my new STABLE (5) (without using rp_pppoe). could someone help me on this issue (logs provided here)... two PADI are emitted but nothing happens after. (i saw that someone had a similar problem, but with previous netgraph revisions). thank you. Since my ADSL modem is 3Com HomeConnect, I've set the net.graph.nonstandard_pppoe=1 ng_pppoe.c rev. is 1.67.2.1 http://1.67.2.1/ ng_socket.c rev. is 1.53.2.3 http://1.53.2.3/ my ppp.conf is : default: set log all set ifaddr X.X.X.X/0 10.0.0.2/0 http://10.0.0.2/0 my_isp : set device PPPoE:xl0 set authname MY_USER set authkey MY_PWD set dial #set login add default HISADDR here is a tcpdump -vv -i xl0 : 18:48:40.808687 PPPoE PADI [Host-Uniq 0x00E654C1] 18:48:42.807533 PPPoE PADI [Host-Uniq 0x00E654C1] 18:51:44.010839 PPPoE PADI [Host-Uniq 0x40F195C1] 18:51:46.009639 PPPoE PADI [Host-Uniq 0x40F195C1] Thx, ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
problem with PPPoE STABLE and ADSL 3Com HomeConnect
Hello, it's been two weeks I try to find out what's wrong. Clean install from cvsup STABLE (5). my ADSL account works fine with REL. 4.4+rp_pppoe but not with my new STABLE (5) (without using rp_pppoe). could someone help me on this issue (logs provided here)... two PADI are emitted but nothing happens after. (i saw that someone had a similar problem, but with previous netgraph revisions). thank you. Since my ADSL modem is 3Com HomeConnect, I've set the net.graph.nonstandard_pppoe=1 ng_pppoe.c rev. is 1.67.2.1 http://1.67.2.1/ ng_socket.c rev. is 1.53.2.3 http://1.53.2.3/ my ppp.conf is : default: set log all set ifaddr X.X.X.X/0 10.0.0.2/0 http://10.0.0.2/0 my_isp : set device PPPoE:xl0 set authname MY_USER set authkey MY_PWD set dial #set login add default HISADDR here is a tcpdump -vv -i xl0 : 18:48:40.808687 PPPoE PADI [Host-Uniq 0x00E654C1] 18:48:42.807533 PPPoE PADI [Host-Uniq 0x00E654C1] 18:51:44.010839 PPPoE PADI [Host-Uniq 0x40F195C1] 18:51:46.009639 PPPoE PADI [Host-Uniq 0x40F195C1] here is my ppp.log: Sep 11 19:42:17 fidelio ppp[24723]: Phase: Using interface: tun0 Sep 11 19:42:17 fidelio ppp[24723]: Phase: deflink: Created in closed state Sep 11 19:42:17 fidelio ppp[24723]: tun0: Command: default: set ifaddr X.X.X.X/0 10.0.0.2/0 http://10.0.0.2/0 Sep 11 19:42:17 fidelio ppp[24723]: tun0: Phase: PPP Started (interactive mode). Sep 11 19:42:17 fidelio ppp[24723]: tun0: Timer: prompt /dev/ttyv0: fdset(r) 0 Sep 11 19:42:23 fidelio ppp[24723]: tun0: Timer: Select returns 1 Sep 11 19:42:23 fidelio ppp[24723]: tun0: Command: /dev/ttyv0: load my_isp Sep 11 19:42:23 fidelio ppp[24723]: tun0: ID0: 0x282e97c0 = fopen(/etc/ppp/ppp.conf, r) Sep 11 19:42:23 fidelio ppp[24723]: tun0: Debug: ReadSystem: Checking default (/etc/ppp/ppp.conf). Sep 11 19:42:23 fidelio ppp[24723]: tun0: ID0: 0x282e97c0 = fopen(/etc/ppp/ppp.conf, r) Sep 11 19:42:23 fidelio ppp[24723]: tun0: Debug: ReadSystem: Checking easyconnect (/etc/ppp/ppp.conf). Sep 11 19:42:23 fidelio ppp[24723]: tun0: ID0: 0x282e97c0 = fopen(/etc/ppp/ppp.conf, r) Sep 11 19:42:23 fidelio ppp[24723]: tun0: Debug: ReadSystem: Checking easyconnect (/etc/ppp/ppp.conf). Sep 11 19:42:23 fidelio ppp[24723]: tun0: Command: easyconnect: set device PPPoE:xl0 Sep 11 19:42:23 fidelio ppp[24723]: tun0: Command: easyconnect: set authname MY_USER Sep 11 19:42:23 fidelio ppp[24723]: tun0: Command: easyconnect: set authkey Sep 11 19:42:23 fidelio ppp[24723]: tun0: Command: easyconnect: set dial Sep 11 19:42:23 fidelio ppp[24723]: tun0: Command: easyconnect: add default HISADDR Sep 11 19:42:23 fidelio ppp[24723]: tun0: ID0: 3 = socket(17, 3, 0) Sep 11 19:42:23 fidelio ppp[24723]: tun0: ID0: -1 = write(3, data, 140) Sep 11 19:42:23 fidelio ppp[24723]: tun0: TCP/IP: rt_Set failure: Sep 11 19:42:23 fidelio ppp[24723]: tun0: TCP/IP: rt_Set: Cmd = Add Sep 11 19:42:23 fidelio ppp[24723]: tun0: TCP/IP: rt_Set: Dst = 0.0.0.0/0http://0.0.0.0/0 Sep 11 19:42:23 fidelio ppp[24723]: tun0: TCP/IP: rt_Set: Gateway = 10.0.0.2http://10.0.0.2/ Sep 11 19:42:23 fidelio ppp[24723]: tun0: Debug: wrote -1: cmd = Add, dst = 0.0.0.0/0 http://0.0.0.0/0, gateway = 10.0.0.2 http://10.0.0.2/ Sep 11 19:42:23 fidelio ppp[24723]: tun0: Timer: prompt /dev/ttyv0: fdset(r) 0 Sep 11 19:42:26 fidelio ppp[24723]: tun0: Timer: Select returns 1 Sep 11 19:42:26 fidelio ppp[24723]: tun0: Command: /dev/ttyv0: dial Sep 11 19:42:26 fidelio ppp[24723]: tun0: Phase: bundle: Establish Sep 11 19:42:26 fidelio ppp[24723]: tun0: Phase: deflink: closed - opening Sep 11 19:42:26 fidelio ppp[24723]: tun0: ID0: 0 = NgMkSockNode(, cs, ds) Sep 11 19:42:26 fidelio ppp[24723]: tun0: Debug: List of netgraph node ``xl0:'' (id 2) hooks: Sep 11 19:42:26 fidelio ppp[24723]: tun0: Debug: Found orphans - ethernet Sep 11 19:42:26 fidelio ppp[24723]: tun0: Debug: Connecting netgraph socket .:tun0 - [4]::tun0 Sep 11 19:42:26 fidelio ppp[24723]: tun0: ID0: 4 = socket(2, 2, 0) Sep 11 19:42:26 fidelio ppp[24723]: tun0: ID0: 0 = ioctl(4, 3223349521, 0xbfbfdd90) Sep 11 19:42:26 fidelio ppp[24723]: tun0: ID0: 0 = ioctl(4, 2149607696, 0xbfbfdd90) Sep 11 19:42:26 fidelio ppp[24723]: tun0: Debug: Sending PPPOE_CONNECT to .:tun0 Sep 11 19:42:26 fidelio ppp[24723]: tun0: Debug: Found the following interfaces: Sep 11 19:42:26 fidelio ppp[24723]: tun0: Debug: Index 1, name fxp0 Sep 11 19:42:26 fidelio ppp[24723]: tun0: Debug: Index 2, name xl0 Sep 11 19:42:26 fidelio ppp[24723]: tun0: Debug: Index 3, name plip0 Sep 11 19:42:26 fidelio ppp[24723]: tun0: Debug: Index 4, name lo0 Sep 11 19:42:26 fidelio ppp[24723]: tun0: Debug: Index 5, name tun0 Sep 11 19:42:26 fidelio ppp[24723]: tun0: Timer: timer_Start: Inserting physical throughput timer[0x80be068] Sep 11 19:42:26 fidelio ppp[24723]: tun0: Phase: deflink: Connected! Sep 11 19:42:26 fidelio ppp[24723]: tun0: Phase: deflink: opening - dial Sep 11 19:42:26 fidelio ppp[24723]: tun0: Chat: deflink: Dial attempt 1
Re: pppoe server option
On Sun, Nov 28, 2004 at 09:35:40PM +0900, Hideki Yamamoto wrote: H -l switch configures label in ppp.conf H -p swicth configures provider name which is announced in Ethernet. H H Thank you for your reply. H I think comment statement in /etc/defaults/rc.conf should be changed H because the current comment means '-l'. Otherwise we should change H /etc/rc.network. Don't you think so? H H -- /etc/defaults/rc.conf -- H pppoed_provider=service-pppoe # Provider and ppp(8) config file entry. H --- [ccing Alfred, since cvs annotate points at him] If label has not been specified, it defaults to provider. So this comment is not meaningless. If you want to specify another label, you should use pppoed_flags variable. I think it will be better to change comment to PPPoE Provider name. Alfred, what do you think? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pppoe server option
Hi,
From: Gleb Smirnoff [EMAIL PROTECTED]
Subject: Re: pppoe server option
Date: Mon, 22 Nov 2004 11:12:50 +0300
Message-ID: [EMAIL PROTECTED]
On Sun, Nov 21, 2004 at 12:34:25AM +0900, Hideki Yamamoto wrote:
H I have found a problem about PPPoE parameter in /etc/rc.network.
H When setting the following lines in /etc/rc.conf, pppoe server does not
H work well. The string service-pppoe is an entry in
H /etc/ppp/ppp.conf for PPPoE server.
H
H pppoed_enable=YES# Run the PPP over Ethernet daemon.
H pppoed_provider=service-pppoe# Provider and ppp(8) config file entry.
H pppoed_interface=fxp0# The interface that pppoed runs on.
H
H In /etc/rc.network, 'pppoed_provider' is passed into pppoe with -p
H option. After booting os, pppoe arguments are as follows:
H
Hpppoed ... -p service-pppoe fxp0
H
H But this option does not work. We should use -l instead of -p like
H this:
H
Hpppoed ... -l service-pppoe fxp0
H
H To use -l, I think the line 822 in /etc/rc.network should be modified.
H
H822pppoed_flags=${pppoed_flags} -p
${pppoed_provider}
H
H822pppoed_flags=${pppoed_flags} -l
${pppoed_provider}
H
H After modifying the above line, pppoed server works well.
H But is this modification correct?
No.
-l switch configures label in ppp.conf
-p swicth configures provider name which is announced in Ethernet.
Thank you for your reply.
I think comment statement in /etc/defaults/rc.conf should be changed
because the current comment means '-l'. Otherwise we should change
/etc/rc.network. Don't you think so?
-- /etc/defaults/rc.conf --
pppoed_provider=service-pppoe# Provider and ppp(8) config file entry.
---
--
Totus tuus, Glebius.
GLEBIUS-RIPN GLEB-RIPE
-
Hideki YAMAMOTO |
Broadband Media Solutions Department | E-mail: [EMAIL PROTECTED]
Broadband Media Company | Tel: +81-48-420-7012
Oki Electric Industry Co., Ltd. | FAX: +81-48-420-7016
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pppoe server option
On Sun, Nov 21, 2004 at 12:34:25AM +0900, Hideki Yamamoto wrote:
H I have found a problem about PPPoE parameter in /etc/rc.network.
H When setting the following lines in /etc/rc.conf, pppoe server does not
H work well. The string service-pppoe is an entry in
H /etc/ppp/ppp.conf for PPPoE server.
H
H pppoed_enable=YES # Run the PPP over Ethernet daemon.
H pppoed_provider=service-pppoe # Provider and ppp(8) config file entry.
H pppoed_interface=fxp0 # The interface that pppoed runs on.
H
H In /etc/rc.network, 'pppoed_provider' is passed into pppoe with -p
H option. After booting os, pppoe arguments are as follows:
H
Hpppoed ... -p service-pppoe fxp0
H
H But this option does not work. We should use -l instead of -p like
H this:
H
Hpppoed ... -l service-pppoe fxp0
H
H To use -l, I think the line 822 in /etc/rc.network should be modified.
H
H822 pppoed_flags=${pppoed_flags} -p
${pppoed_provider}
H
H822 pppoed_flags=${pppoed_flags} -l
${pppoed_provider}
H
H After modifying the above line, pppoed server works well.
H But is this modification correct?
No.
-l switch configures label in ppp.conf
-p swicth configures provider name which is announced in Ethernet.
--
Totus tuus, Glebius.
GLEBIUS-RIPN GLEB-RIPE
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
pppoe server option
Hi,
I have found a problem about PPPoE parameter in /etc/rc.network.
When setting the following lines in /etc/rc.conf, pppoe server does not
work well. The string service-pppoe is an entry in
/etc/ppp/ppp.conf for PPPoE server.
pppoed_enable=YES # Run the PPP over Ethernet daemon.
pppoed_provider=service-pppoe # Provider and ppp(8) config file entry.
pppoed_interface=fxp0 # The interface that pppoed runs on.
In /etc/rc.network, 'pppoed_provider' is passed into pppoe with -p
option. After booting os, pppoe arguments are as follows:
pppoed ... -p service-pppoe fxp0
But this option does not work. We should use -l instead of -p like
this:
pppoed ... -l service-pppoe fxp0
To use -l, I think the line 822 in /etc/rc.network should be modified.
822 pppoed_flags=${pppoed_flags} -p
${pppoed_provider}
822 pppoed_flags=${pppoed_flags} -l
${pppoed_provider}
After modifying the above line, pppoed server works well.
But is this modification correct?
-
Hideki YAMAMOTO |
Broadband Media Solutions Department | E-mail: [EMAIL PROTECTED]
Broadband Media Company | Tel: +81-48-420-7012
Oki Electric Industry Co., Ltd. | FAX: +81-48-420-7016
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.10-STABLE - ADSL PPPoE
On Fri, Jun 04, 2004 at 01:14:23AM -0400, Rob Clark wrote: On Thu, 3 Jun 2004 20:10:16 -0400 Rob Clark [EMAIL PROTECTED] wrote: On Thu, 03 Jun 2004 18:16:00 [EMAIL PROTECTED] wrote: Dear all, I update my system 4.10-STABLE(27 May) to FreeBSD 4.10-STABLE(June 2) without problems but now my connection ADSL does not work , previously worked correctly, and the connections with loopback 127.0.0.1 delay much, example ssh/ftp/ 127.0.0.1 delay 30 - 40 seconds. I seen this same behavior today (06.03.04) after updating sources. My last update was 05.27.04 and everything worked fine at that point in the branch. PPPoE on today's stable doesn't load the netgraph modules: netgraph.ko ng_ether.ko ng_pppoe.ko ng_socket.ko when PPPoE is started. I reverted to sources to 05.27.04 date, did buildworld and PPPoE is working again by adding the following to my supfile: *default date=2004.05.27.23.00.00 If I can help in narrowing down the date of failure please let me know. Thanks, Rob Apologies for following up on my own post, but i've narrowed down the failure window a bit. Other updates tried: *default date=2004.05.27.23.00.00 /* works */ *default date=2004.06.01.00.00.00 /* works */ *default date=2004.06.02.00.00.00 /* breaks */ cvsupping from date=2004.06.01.00.00.00 to date=2004.06.02.00.00.00 is where the breakage occurs. Here is an excerpt from the cvsup log showing the files involved: Updating collection src-all/cvs Edit src/share/man/man4/ng_ether.4 Add delta 1.4.2.13 2004.06.01.22.55.24 archie Edit src/share/man/man4/ng_hole.4 Add delta 1.10.2.2 2004.06.01.14.50.38 ru Edit src/sys/i386/i386/mp_machdep.c Add delta 1.115.2.21 2004.06.01.18.09.58 jhb Edit src/sys/netgraph/ng_ether.c Add delta 1.2.2.15 2004.06.01.22.55.24 archie This is the culprit. I was having the same problem (PPPoE stopped working), but recompiling my system with the previous (1.2.2.14) of ng_ether.c solved it. Archie, is it possible to fix this (either by reverting the patch or by applying a new one)? Best regards, --rro -- rro at das ufsc br Please remove NOSPAM from the header if you want to contact me. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.10-STABLE - ADSL PPPoE
At 10:25 PM 04/06/2004, Rafael R Obelheiro wrote: This is the culprit. I was having the same problem (PPPoE stopped working), but recompiling my system with the previous (1.2.2.14) of ng_ether.c solved it. Archie, is it possible to fix this (either by reverting the patch or by applying a new one)? Try recompiling mpd. Those patches broke binary compatibility. ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ppp(8) v. 3.1 : PPPoE lqr problem.
On Monday 24 November 2003 15:32, Mike Tancsa wrote: The problem is that LQR is agreed to with the ERX (the PPPoE terminating device on the other end), but it never works. Works for me. I guess there really are many providers with misconfigured equipment out there. Actually, I know people who cannot use lqr although they're using the same provider as I do (but they 'dial in' to a different AC). Trying to actually get such an obscure technical thing through any big telco/provider hotline to someone who can actually understand what you want is pretty futile, too. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp0.pgp Description: signature
Re: ppp(8) v. 3.1 : PPPoE lqr problem.
Are you sure you actually connect to an ERX on the other end, and its actually negotiating LQR ? e.g. if you add LQM to the logging section, do you see tun0: LQM: deflink: Will send LQR every 10.00 secs or do you see tun0: LQM: deflink: LQR/ECHO LQR not negotiated What do you have for your ppp.conf ? I have enable lqr accept lqr set lqrperiod 10 Like I said, its very possible the telco has the ERX misconfigured and yes, its impossible to get this level of detail out of them :-( ---Mike At 10:17 AM 24/11/2003, Michael Nottebrock wrote: On Monday 24 November 2003 15:32, Mike Tancsa wrote: The problem is that LQR is agreed to with the ERX (the PPPoE terminating device on the other end), but it never works. Works for me. I guess there really are many providers with misconfigured equipment out there. Actually, I know people who cannot use lqr although they're using the same provider as I do (but they 'dial in' to a different AC). Trying to actually get such an obscure technical thing through any big telco/provider hotline to someone who can actually understand what you want is pretty futile, too. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ppp(8) v. 3.1 : PPPoE lqr problem.
On Monday 24 November 2003 16:46, Mike Tancsa wrote: Are you sure you actually connect to an ERX on the other end, and its actually negotiating LQR ? e.g. if you add LQM to the logging section, do you see tun0: LQM: deflink: Will send LQR every 10.00 secs or do you see tun0: LQM: deflink: LQR/ECHO LQR not negotiated Yes. LQM: deflink: Will send LQR every 30.00 secs I even found this way back in my ppp.log: Phase: deflink: ** Too many LQR packets lost ** So it's actually doing what it should. :) What do you have for your ppp.conf ? I have enable lqr accept lqr set lqrperiod 10 Just enable lqr. The default period of 30 seconds is quite reasonable IMHO. Like I said, its very possible the telco has the ERX misconfigured and yes, its impossible to get this level of detail out of them :-( C'est la vie. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp0.pgp Description: signature
Re: ppp(8) v. 3.1 : PPPoE lqr problem.
At 10:59 AM 24/11/2003, Michael Nottebrock wrote: On Monday 24 November 2003 16:46, Mike Tancsa wrote: Are you sure you actually connect to an ERX on the other end, and its actually negotiating LQR ? e.g. if you add LQM to the logging section, do you see tun0: LQM: deflink: Will send LQR every 10.00 secs or do you see tun0: LQM: deflink: LQR/ECHO LQR not negotiated Yes. LQM: deflink: Will send LQR every 30.00 secs I even found this way back in my ppp.log: Phase: deflink: ** Too many LQR packets lost ** So it's actually doing what it should. :) But is it doing that because its never hearing the LQR reply ? And for sure its an ERX on the other end ? ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ppp(8) v. 3.1 : PPPoE lqr problem.
On Monday 24 November 2003 17:07, Mike Tancsa wrote: At 10:59 AM 24/11/2003, Michael Nottebrock wrote: On Monday 24 November 2003 16:46, Mike Tancsa wrote: Are you sure you actually connect to an ERX on the other end, and its actually negotiating LQR ? e.g. if you add LQM to the logging section, do you see tun0: LQM: deflink: Will send LQR every 10.00 secs or do you see tun0: LQM: deflink: LQR/ECHO LQR not negotiated Yes. LQM: deflink: Will send LQR every 30.00 secs I even found this way back in my ppp.log: Phase: deflink: ** Too many LQR packets lost ** So it's actually doing what it should. :) But is it doing that because its never hearing the LQR reply ? Yes. ppp nicely detects when they're up and fuzzing with the AC again. And for sure its an ERX on the other end ? Actually it's an NRP - it seems Cisco does a better job with their PPPoE implementation. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp0.pgp Description: signature
Re: ppp(8) v. 3.1 : PPPoE lqr problem.
At 11:25 AM 24/11/2003, Michael Nottebrock wrote: And for sure its an ERX on the other end ? Actually it's an NRP - it seems Cisco does a better job with their PPPoE implementation. OK, thanks. The problem I see is only against an ERX. So either misconfigured ERX or something about Juniper's implementation. As the original poster was connecting against Frace Telecom and I to Bell Canada and given that VJ Header compression also does not play well with FreeBSD's I am leaning to the ERX. Back to the original question of how best to work around this. I will be deploying close to 100 boxes, most of which will talk to an ERX. It would be nice if I could avoid having to manually patch the boxes each time I do an update. If I work with my programmers here to come up with a patch, is there even a chance that someone would commit it to HEAD and then MFC it back to RELENG_4? Who is looking after PPP these days anyways ? ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ppp(8) v. 3.1 : PPPoE lqr problem.
On Monday 24 November 2003 17:35, Mike Tancsa wrote: given that VJ Header compression also does not play well with FreeBSD's I am leaning to the ERX. Right, vjcomp, I don't need to disable that here as well... Back to the original question of how best to work around this. I will be deploying close to 100 boxes, most of which will talk to an ERX. It would be nice if I could avoid having to manually patch the boxes each time I do an update. If I work with my programmers here to come up with a patch, is there even a chance that someone would commit it to HEAD and then MFC it back to RELENG_4? Who is looking after PPP these days anyways ? I guess there is a definite chance, it's not like ppp's pppoe functionality is some rarely-used feature... I myself am only a lowly ports-committer, but if you submit a PR and send me a note, I'll make sure it gets assigned to brian (or maybe there are already PRs pending?). -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp0.pgp Description: signature
Re: FTP installation from the floppies through ADSL modem with PPPoE or PPTP protocol.
The modem can be configured to use PPPoE or PPTP protocol for making the connection with my Internet Servise Provider. Well if the modem does PPPoE itself (and preusmably NAT) then you need no speical support from the OS. From its poitn of view you are just conencted via ethernet. If you need the machine to do PPPoE, ppp supports PPPoE. For this to work, though, you need netgraph, which isn't in GENERIC. You will need to make a custom kernel and build your own set of custom floppies. Ok, so in my situation the installation of FreeBSD is impossible. What do you think about changing GENERIC or just the kernel in installation floppies in the future releases of FreeBSD? I think it will be very useful because ADSL (therefore PPPoE protocol) is very frequent method of connecting with Internet Service Provider in our days. P.S. FTP installation use much less internet traffic than 4 huge ISO files' downloading. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: ppp(8) v. 3.1 : PPPoE lqr problem.
Le 2002-10-01, Artur Pydo écrivait : Since the end of August i had problems running my ADSL connection. I discovered that ppp changed its behaviour regarding lqr after the upgrade from version 2.3.3 to 3.1. This is probably a coincidence. I saw that when France Telecom changed some ADSL equipment: the new BASs indeed do not reply to LCP Echo Request frames. I have notified them of this problem several times since then, to no avail. Thomas. -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: ppp(8) v. 3.1 : PPPoE lqr problem.
At 09:56 AM 10/1/2002 +0200, Thomas Quinot wrote: Le 2002-10-01, Artur Pydo écrivait : Since the end of August i had problems running my ADSL connection. I discovered that ppp changed its behaviour regarding lqr after the upgrade from version 2.3.3 to 3.1. This is probably a coincidence. I saw that when France Telecom changed some ADSL equipment: the new BASs indeed do not reply to LCP Echo Request frames. I have notified them of this problem several times since then, to no avail. And, their VJ Header compression is broken... We got burned by this big time when Bell Canada started switching away from Redback's SMSes... Knowledge Asset ID#: 1773.0 Subject: The ERX does not support IP header compression as described in RFC 2507 and RFC 2508. Type: SW Release: SW Version: Problem Description: The ERX does not support and does not yet have plans to support IP header compression. For a full description of IP header compression refer to RFC 2507 and RFC 2508. It basically says that multiple packets to and from the same destinations can get their headers compressed to save about 8 bytes per packet. This feature has been requested in case 10349 -- Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: ppp(8) v. 3.1 : PPPoE lqr problem.
Hi, Thomas Quinot wrote: Le 2002-10-01, Artur Pydo écrivait : Since the end of August i had problems running my ADSL connection. I discovered that ppp changed its behaviour regarding lqr after the upgrade from version 2.3.3 to 3.1. This is probably a coincidence. Not really. The old version of ppp is still working today (see below). I saw that when France Telecom changed some ADSL equipment: the new BASs indeed do not reply to LCP Echo Request frames. I have notified them of this problem several times since then, to no avail. I made my tests yesterday and the behaviour is different with these two ppp versions on the same France Telecom ADSL equipment. So why it's working with ppp v. 2.3.3 and not wotking with v. 3.1 ? Best regards, Artur. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
about PPPoE in 4.6.2
Hi ALL, Is there any specific details in using PPP over Ethernet in 4.6.2-STABLE ? There is an ADSL modem, machine used as gateway with 2 interfaces. How to run PPPoE on it ? Tried to use ppp.conf as it was on machine with 4.1 but it doesn't work. Any help will be kindly appreciated. -- Best regards, Vasily [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: about PPPoE in 4.6.2
:: Is there any specific details in using PPP over Ethernet in 4.6.2-STABLE? The handbook is your friend. Be one with the handbook. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/pppoe.html Cheers - Erick To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Problem with user-pppoe after upgrade, fixed
Hi, Let me make sure I've got things straight. You've upgraded to -stable and removed any ``set mtu'' or ``set mru'' lines that you've got in your ppp.conf. If this is the case, then I'm not sure what's happening. The only way I can reproduce what you're seeing in your log is if I add ``set mtu 1500'' to the configuration - which is incorrect (you can't force the link to have a 1500 byte mtu as it's physically invalid). Ok. I ran some tests on the server, from here, and I of course fried my connection. :) It's all back up now and I have the logs of the failure, so... http://anarcat.dyndns.org/ftp/pub/FreeBSD/local/info/ppp.log Also censored, properly, this time. Neal (the -questions guy :) sent me this privately: -- Looking at CVS for ppp, I noticed that the last change seemed to be MFC: Support stateful MPPE Insist on correct MRU negotiation during LCP I wonder if this would have anything to do with my problems? -- What do you think? a. -- Brian [EMAIL PROTECTED][EMAIL PROTECTED] http://www.freebsd-services.com/brian@[uk.]FreeBSD.org Don't _EVER_ lose your sense of humour ! brian@[uk.]OpenBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Problem with user-pppoe after upgrade, fixed
Hi, I said your ppp.conf was censored because you didn't attach it - you just attached an error message that said it couldn't read it :*P The right fix is to simply remove these lines. What do your logs say when you enable LCP logging and the negotiation fails ? Brian Somers wrote: Hi, I think your ppp.conf was a bit too censored. Well the only thing I censored was my password/username lines and a set log line I removed the same day. Apart from that, this is the ppp.conf that I use right now, and it works. If you're setting the MTU or MRU to 1500, this will now fail. As seen in the logs? The maximum these can be set to for PPPoE is 1492. That's the physical ethernet limitation, right? That's now enforced by the PPPoE ppp device as it knows the limitations on the physical Ethernet. Shouldn't ppp warn the user or panic instead of looping as it did for me? Just commenting out your setting of the MTU/MRU should solve your problems. Actually, putting the set mtu/mru lines solved the problems. Should I remove them altogether to remove future problems? :) Thank you very much. A. -- Antoine Beaupré Jambala TCM team Ericsson Canada inc. mailto:[EMAIL PROTECTED] -- Brian [EMAIL PROTECTED][EMAIL PROTECTED] http://www.freebsd-services.com/brian@[uk.]FreeBSD.org Don't _EVER_ lose your sense of humour ! brian@[uk.]OpenBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Problem with user-pppoe after upgrade, fixed
Brian Somers wrote: Hi, I said your ppp.conf was censored because you didn't attach it - you just attached an error message that said it couldn't read it :*P LOL! ok.. I see. Darn mozilla. :) Ok, here goes a url, that should be fine: http://anarcat.dyndns.org/ftp/pub/FreeBSD/local_info/ppp.conf Also check the parent dir for dmesg. The right fix is to simply remove these lines. Then a workaround is to change them to 1492. :) But ok, I'll kill the line. What do your logs say when you enable LCP logging and the negotiation fails ? I'm sorry, I forgot to check yesterday night. But we have another nice test case here that cross-posted -stable and -questions. :) I'll try to do it via remote and a nice script, but this is mad, I could really fsck up my connection here. Hmm... Let's be mad. ;) A. -- Antoine Beaupré Jambala TCM team Ericsson Canada inc. mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: panic on -stable during ppp-dial (PPP NETGRAPH PPPoE)
In article local.mail.freebsd-stable/20010711080517$[EMAIL PROTECTED] you write: -=-=-=-=-=- Hi, on a pentium 233 IPC with a dual fxp (Intel Pro 100+) card, with this ppp configuration: ... tdsl: set device PPPoE:fxp1 ... and the attached kernel configuration file (mike) I get the following panic: I would guess that PPPoE here is attempting to send a packet through the fxp device while it is administratively down, and the fxp driver panics because it is not initialized. This is a bug in netgraph, it should check the status of the interface before queuing a packet. If this is the problem, then a workaround is to bring the interface up (via 'ifconfig fxp0 up') before running ppp. -- Jonathan PS. Yes, I have a static IP address. You're using an awfully big brush to tar everyone with by rejecting all mail from @home. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
FreeBSD 4.3 stable PPPoE
Dear FreeBSD experts, Can you let me know what should I do to provide enough information for the FreeBSD developers to trace/ debug/ fix the PPPoE I experienced with FreeBSD 4.3 stable, please? I tried to upgrade from 4.2 stable to 4.3 stable several times after a cvsup and a clean buildworld during the last two months (April - June 2001). As of today, my box still couldn't connect to my ISP via pppoe with 4.3 stable. I have no choice but to switch back to 4.2 stable (tcpdump on 4.2 is attached below). In other world, I can connect to my ISP with FreeBSD 4.2 stable only. Above all, I cannot enjoy the improvements the FreeBSD developers have made on 4.3 stable. I am bound to 4.2 stable. Thank you. -echelon Here is the tcpdump I got: For 4.3, (cvsup on May 15 and before), PADI-PADO-PADR-PADS received but PADT arrived before an ip was allocated to my box. (cvsup on June 14), my box send out a stream of PADI without receiveing any PADO. (tcpdump on 4.2 stable for a normal connection) tcpdump: listening on xl0 14:37:23.765991 Broadcast 8863 32: PPPoE PADI [Host-Uniq UTF8] 14:37:25.762297 Broadcast 8863 32: PPPoE PADI [Host-Uniq UTF8] 14:37:25.765052 8863 67: PPPoE PADO [Host-Uniq UTF8] [Service-Name] [AC-Name -X-] [AC-Cookie UTF8] 14:37:25.765070 8863 67: PPPoE PADR [Host-Uniq UTF8] [AC-Cookie UTF8] [AC-Name -X-] 14:37:25.957263 8863 67: PPPoE PADS [ses 0x79eb] [Host-Uniq UTF8] [AC-Cookie UTF8] [AC-Name -X-] 14:37:25.965396 8864 60: PPPoE [ses 0x79eb] LCP ConfReq id=0x1 auth PAP magic 0x936d062e 14:37:26.506862 8864 36: PPPoE [ses 0x79eb] LCP ConfReq id=0x1 mru 1492 magic 0xb88717d6 14:37:26.506914 8864 36: PPPoE [ses 0x79eb] LCP ConfAck id=0x1 auth PAP magic 0x936d062e 14:37:26.510170 8864 60: PPPoE [ses 0x79eb] LCP ConfNak id=0x1 mru 1500 14:37:26.510294 8864 36: PPPoE [ses 0x79eb] LCP ConfReq id=0x2 mru 1500 magic 0xb88717d6 14:37:26.513226 8864 60: PPPoE [ses 0x79eb] LCP ConfAck id=0x2 mru 1500 magic 0xb88717d6 14:37:26.513806 8864 54: PPPoE [ses 0x79eb] PAP 14:37:26.707275 8864 60: PPPoE [ses 0x79eb] PAP 14:37:26.707818 8864 60: PPPoE [ses 0x79eb] IPCP 14:37:26.710496 8864 32: PPPoE [ses 0x79eb] proto-0x80fd 14:37:26.710550 8864 50: PPPoE [ses 0x79eb] IPCP 14:37:26.710598 8864 32: PPPoE [ses 0x79eb] IPCP 14:37:26.714876 8864 60: PPPoE [ses 0x79eb] LCP ProtRej id=0x1 prot=PROT-0x80fd 14:37:26.716304 8864 60: PPPoE [ses 0x79eb] IPCP 14:37:26.717307 8864 44: PPPoE [ses 0x79eb] IPCP 14:37:26.721494 8864 60: PPPoE [ses 0x79eb] IPCP 14:37:26.722677 8864 44: PPPoE [ses 0x79eb] IPCP 14:37:26.728334 8864 60: PPPoE [ses 0x79eb] IPCP ... __ Do You Yahoo!? Spot the hottest trends in music, movies, and more. http://buzz.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
pppoe crashes in 4.3-stable (14.5.2000)
Title: pppoe crashes in 4.3-stable (14.5.2000) user-mode ppp crashes when calling pppoe-providers. After starting ppp I get the following error message linker_file_sysinit netgraph.ko failed to register! 17 Fatal Trap 12: page fault while in kernel mode The kernel panics, and i got no further errors in logfiles. Netgraph is built directly into the kernel, also the tun-interface. what's going wrong ?
Re: pppoe crashes in 4.3-stable (14.5.2000)
Title: pppoe crashes in 4.3-stable (14.5.2000) Can you tell me exactly what options you put in your kernel? - Original Message - From: Bernd Fürwitt To: [EMAIL PROTECTED] Sent: Tuesday, May 15, 2001 12:37 PM Subject: pppoe crashes in 4.3-stable (14.5.2000) user-mode ppp crashes when calling pppoe-providers.After starting ppp I get the following error messagelinker_file_sysinit "netgraph.ko" failed to register! 17Fatal Trap 12: page fault while in kernel modeThe kernel panics, and i got no further errors in logfiles.Netgraph is built directly into the kernel, also the tun-interface.what's going wrong ?
Re: pppoe crashes in 4.3-stable (14.5.2000)
On Wed, May 16, 2001 at 07:59:26AM +0200, Bernd Fürwitt wrote: user-mode ppp crashes when calling pppoe-providers. After starting ppp I get the following error message linker_file_sysinit netgraph.ko failed to register! 17 Fatal Trap 12: page fault while in kernel mode The kernel panics, and i got no further errors in logfiles. Netgraph is built directly into the kernel, also the tun-interface. what's going wrong ? Old modules? You sure you have all of the netgraph modules PPPoE requires statically compiled in (not just NETGRAPH)? Kris PGP signature
RE: pppoe crashes in 4.3-stable (14.5.2000)
Title: RE: pppoe crashes in 4.3-stable (14.5.2000) On Wed, May 16, 2001 at 07:59:26AM +0200, Bernd Fürwitt wrote: user-mode ppp crashes when calling pppoe-providers. After starting ppp I get the following error message linker_file_sysinit netgraph.ko failed to register! 17 Fatal Trap 12: page fault while in kernel mode The kernel panics, and i got no further errors in logfiles. Netgraph is built directly into the kernel, also the tun-interface. what's going wrong ? Old modules? You sure you have all of the netgraph modules PPPoE requires statically compiled in (not just NETGRAPH)? I tried compiling in all of the netgraph-stuff (statically), the result remains the same. I built the world, after changing any kernel-options. And now i've upgraded again to 4.3-stable (16.05.01). Nothing changed.
Re: pppoe crashes in 4.3-stable (14.5.2000)
On Wed, May 16, 2001 at 08:34:43AM +0200, Bernd Fürwitt wrote: On Wed, May 16, 2001 at 07:59:26AM +0200, Bernd Fürwitt wrote: user-mode ppp crashes when calling pppoe-providers. After starting ppp I get the following error message linker_file_sysinit netgraph.ko failed to register! 17 Fatal Trap 12: page fault while in kernel mode The kernel panics, and i got no further errors in logfiles. Netgraph is built directly into the kernel, also the tun-interface. what's going wrong ? Old modules? You sure you have all of the netgraph modules PPPoE requires statically compiled in (not just NETGRAPH)? I tried compiling in all of the netgraph-stuff (statically), the result remains the same. I built the world, after changing any kernel-options. And now i've upgraded again to 4.3-stable (16.05.01). Nothing changed. The error message above indicates it's trying to kldload something because it's not present in your running kernel. Can you post your kernel config file? Kris PGP signature
Re: pppoe crashes in 4.3-stable (14.5.2000)
I think there is an open pr about this where the dynamic loading is broken, this was talked about maybe a week ago. Roughly if part of it is compiled statically but not all, the kldloader can't tell and tries to load it anyways(the stuff that's already compiled in). Not trying to do anything but open the possibility that this could be an existing open problem. - Original Message - From: Kris Kennaway [EMAIL PROTECTED] To: Bernd Fürwitt [EMAIL PROTECTED] Cc: 'Kris Kennaway' [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, May 16, 2001 1:39 AM Subject: Re: pppoe crashes in 4.3-stable (14.5.2000) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
pppoe crashes in 4.3-stable (14.5.2000)
Title: pppoe crashes in 4.3-stable (14.5.2000) user-mode ppp crashes when calling pppoe-providers. After starting ppp I get the following error message linker_file_sysinit netgraph.ko failed to register! 17 Fatal Trap 12: page fault while in kernel mode The kernel panics, and i got no further errors in logfiles. Netgraph is built directly into the kernel, also the tun-interface. what's going wrong ?
RE: Release 4.3 stable: PPPoE/ PPP problem
If you are using the kernel built from make buildkernel/installkernel, the kernel is not built with PPPoE options. That is built with GENERIC. You have to rebuild your kernel with the options for PPPoE. Please refer PPPoE section of handbook. (http://www.freebsd.org/doc/en_US.ISO_8859-1/books/handbook/pppoe.html) /Jaeho -Original Message- From: echelon [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 25, 2001 2:06 AM To: [EMAIL PROTECTED] Subject: Release 4.3 stable: PPPoE/ PPP problem Hi, Before I describe my problem, I'd like to thanks all FreeBSD developers for releasing 4.3 stable. I've been using FreeBSD since 4.0 release. I use it mainly as an internet gateway (PPP in PPPoE mode + PPP NAT + IPfilter) for my home network. I CVSed my 4.3 beta to 4.3 stable on Monday. As usual, buildworld and buildkernel went smoothly without errors except some warnings from gcc. After installkernel, installworld and finally mergemaster, the system is up and running well. I can ssh to it, ipfilter works as it used to be. However, my box just couldn't connect to my ISP via PPPoE after upgrading to 4.3 stable. The ppp.log just shows carrier hang up. It shouldn't be the problem of my configuration as I have used the same setting for months and gone through a number of CVS update cycle. I am quite certain that I have setup netgraph (at kernel conf file) / ppp.conf properly since FreeBSD 4.2. My network card is 3Com 3C905B. xl and miibus have no compilation errors. Are there any new configurations I need to set up in 4.3 stable before I can use PPP? Thanks a lot. -e_chelon __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Kernel Panic on 4.3-RC #0 using PPPoE
Hi,
On Tue, Mar 27, 2001 at 12:40:11PM -0800, Archie Cobbs wrote:
Mike Tancsa writes:
Not sure why this hasn't been detected before though. Below is
a possible patch.
It has been at http://www.freebsd.org/cgi/query-pr.cgi?pr=25478 and
discussed a few times in freebsd-net.
Here is the better (?) patch. I'd like to commit this if nobody
objects..
Please take a careful look at the frames 6 through 9 of the stack
trace in PR#25478, so you may notice that your patch happens to do
nothing about the broblem. You are going to add a check for IFF_UP
to ether_output_frame() while that function is just a bottom half
of ether_output(), which does do the check at its very beginning.
The real problem is that ethernet card drivers rely on ether_output()
making sure they are up before calling their if_output()s. AFAIK
the vlan driver is the only piece of code where the standard
ether_output()-if_output() order is bypassed, and an if_output()
routine of an ethernet card is called directly. Therefore, the
IFF_UP check should be in the vlan code, and I'm going to commit
a corresponding fix (PR: kern/22179). Any objections?
Luigi: would you mind reviewing this for possible BRIDGE problems?
-Archie
__
Archie Cobbs * Packet Design * http://www.packetdesign.com
Index: if_ethersubr.c
===
RCS file: /home/ncvs/src/sys/net/if_ethersubr.c,v
retrieving revision 1.70.2.15
diff -u -r1.70.2.15 if_ethersubr.c
--- if_ethersubr.c2001/03/13 22:00:32 1.70.2.15
+++ if_ethersubr.c2001/03/27 20:39:38
@@ -366,6 +366,11 @@
{
int s, error = 0;
+ if ((ifp-if_flags (IFF_UP|IFF_RUNNING)) != (IFF_UP|IFF_RUNNING)) {
+ m_freem(m);
+ return (ENETDOWN);
+ }
+
#ifdef BRIDGE
if (do_bridge BDG_USED(ifp) ) {
struct ether_header *eh; /* a ptr suffices */
SY, Yar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: Kernel Panic on 4.3-RC #0 using PPPoE
On Wed, Mar 28, 2001 at 11:30:49AM +0400, Yar Tikhiy wrote: Please take a careful look at the frames 6 through 9 of the stack trace in PR#25478, so you may notice that your patch happens to do nothing about the broblem. You are going to add a check for IFF_UP to ether_output_frame() while that function is just a bottom half of ether_output(), which does do the check at its very beginning. Just a clarifying note: Please keep in mind that ether_output() (frame 9) through vlan_start() (frame 7) are called on a vlan interface while fxp_start() (frame 6) is called on a different interface - fxp. The real problem is that ethernet card drivers rely on ether_output() making sure they are up before calling their if_output()s. AFAIK the vlan driver is the only piece of code where the standard ether_output()-if_output() order is bypassed, and an if_output() routine of an ethernet card is called directly. Therefore, the IFF_UP check should be in the vlan code, and I'm going to commit a corresponding fix (PR: kern/22179). Any objections? Please substitute "if_output" with "if_start" when reading the above paragraph. Sorry :-) SY, Yar To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Kernel Panic on 4.3-RC #0 using PPPoE
Archie Cobbs writes: I am receiving kernel panics under 4.3-RC #0 when trying to bring up PPPoE. A copy of the kernel debug, the start up and the actual PPP configuration are attached. It appears to be something in the subroutine called fxp_start of the actual ethernet card (Which is an Intel Express) trying to use a structure which has not yet been initialized. The machine is an SMP machine as well; although compiling without SMP support has so far made no difference. The problem also occurs under 4.2-RELEASE. Any help on the subject would be appreciated. I think that the interface has not yet been brought up (IFF_UP) before the first packet is sent out of it. This can normally only happen when using netgraph (or raw sockets I suppose)... the fxp driver seems to assume that it will never see an output packet without an IFF_UP first, which is no longer true. Also, ppp(8) should be setting IFF_UP on the interface before trying to send out of it. Not sure why this hasn't been detected before though. Below is a possible patch. Actually a better fix is probably to check for IFF_UP at the beginning of ether_output_frame()... -Archie __ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: PPPoE
Ted Sikora wrote: Recently my cable service reduced the bandwidth. Now upstreams average 16k and downstream 400k. There has to be something better. Several users on my node (all BSD/Linux users) have been enjoying our own little private network with speeds up to 900k both ways.(600k average) Now it's terrible. They now limited the internal network to 33k between users. Compared to before it's like putting us on dialups. When you signed on, didn't you agree to pay per month for a given service level? If I understand you correctly, @home has now changed the terms of the agreement. We need competition for cable service in a big, big way. :-( I don't have the option for DSL where I live (yet), and my cable "ISP" (I have to put that in quotes, because they couldn't find their bungholes with both hands and a roadmap) guarantees 1500K down and 500K up for what I'm paying, BUT they block all the ports below 1024. :-( I can hack around that, given a friendly site outside their firewall who's willing to divert packets for me, but it's still a PITA. Regards, Chris BeHanna [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
RE: PPPoE
Ted, I believe that William was requesting a method to do a net install of FreeBSD with PPPoE. So, having been stuck at one point in this same situation (i live in Toronto, Canada, and the xDSL provided by Bell Sympatico uses PPPoE) i re-post the question: Is there any possibility of PPPoE being an **installation** option. If PPPoE is your only connection option to install FreeBSD, a post-install How-To won't really help much. :-( If it's a matter of demand, there's several thousand DSL subscribers in Canada who are stuck with PPPoE... i'm sure several would love to avoid having to buy the FreeBSD CD. I'd be willing to ask them all to submit their email addresses for a group request if it would grease the wheels. Heck, i'm sure some of them would even volunteer to help out! I know i would lend whatever resources i could. :-) Regards, Mit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ted Sikora Sent: Sunday, July 30, 2000 6:53 PM To: [EMAIL PROTECTED] Subject: Re: PPPoE William Wong wrote: Hi there, Does anyone know if there are plans to support PPPoE outta the box? (without recompiling the kernel) I'm not sure how many people are affected by this, but not being able to do a PPPoE install from the boot disks is a bugger. Here's a HOWTO for PPPoe -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: PPPoE
Will Mitayai Keeso Rowe wrote: Ted, I believe that William was requesting a method to do a net install of FreeBSD with PPPoE. So, having been stuck at one point in this same situation (i live in Toronto, Canada, and the xDSL provided by Bell Sympatico uses PPPoE) i re-post the question: Is there any possibility of PPPoE being an **installation** option. If PPPoE is your only connection option to install FreeBSD, a post-install How-To won't really help much. :-( If it's a matter of demand, there's several thousand DSL subscribers in Canada who are stuck with PPPoE... Just FYI, Bell Atlantic (I guess they're now called Verizon) is deploying the same junk. I mean, PPPoE is *so* wasteful, with THIRTY extra bytes of overhead per frame (10 bytes of LLC/SNAP header, 14 bytes of Ethernet header, plus 6 bytes of PPPoE header), compared to direct PPP over ATM. So our northern friends are not alone in this situation... Gary To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: PPPoE
Just FYI, Bell Atlantic (I guess they're now called Verizon) is deploying the same junk. I mean, PPPoE is *so* wasteful, with THIRTY extra bytes of overhead per frame (10 bytes of LLC/SNAP header, 14 bytes of Ethernet header, plus 6 bytes of PPPoE header), compared to direct PPP over ATM. So our northern friends are not alone in this situation... My own experience with PPPoE and HellAtlantic Infospeed is absolutely horrid. It is no coincidence that BA is ranked at the absolute bottom in the national ratings on www.dslreports.com. Stay away if at all possible -- you truly don't get what you don't pay for... We are switching away from BA as fast as we can. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: PPPoE
Will Mitayai Keeso Rowe wrote: Ted, I believe that William was requesting a method to do a net install of FreeBSD with PPPoE. Yeah I know. I emailed him earlier. I posted the FAQ in case anyone was having trouble with PPPoe. It would be nice to have the option on the install floppies. All the DSL users are left in the cold. It's starting to become as popular as Cable. At least in my area. -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: PPPoE
Dan Ts'o wrote: Just FYI, Bell Atlantic (I guess they're now called Verizon) is deploying the same junk. I mean, PPPoE is *so* wasteful, with THIRTY extra bytes of overhead per frame (10 bytes of LLC/SNAP header, 14 bytes of Ethernet header, plus 6 bytes of PPPoE header), compared to direct PPP over ATM. So our northern friends are not alone in this situation... My own experience with PPPoE and HellAtlantic Infospeed is absolutely horrid. It is no coincidence that BA is ranked at the absolute bottom in the national ratings on www.dslreports.com. Stay away if at all possible -- you truly don't get what you don't pay for... We are switching away from BA as fast as we can. They have SNET/SBC in my area. According to them it uses DHCP not PPPoe.(Yet their faq says PPPoe?) I ordered it for the 14th out of curiosity. See how it stands up to cable. Anyone have experience with SNET DSL? I ordered it with NTPLEX.net as my ISP. You can chose your own ISP. -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: PPPoE
Ted Sikora wrote: Dan Ts'o wrote: Just FYI, Bell Atlantic (I guess they're now called Verizon) is deploying the same junk. I mean, PPPoE is *so* wasteful, with THIRTY extra bytes of overhead per frame (10 bytes of LLC/SNAP header, 14 bytes of Ethernet header, plus 6 bytes of PPPoE header), compared to direct PPP over ATM. So our northern friends are not alone in this situation... My own experience with PPPoE and HellAtlantic Infospeed is absolutely horrid. It is no coincidence that BA is ranked at the absolute bottom in the national ratings on www.dslreports.com. Stay away if at all possible -- you truly don't get what you don't pay for... We are switching away from BA as fast as we can. They have SNET/SBC in my area. According to them it uses DHCP not PPPoe.(Yet their faq says PPPoe?) I ordered it for the 14th out of curiosity. See how it stands up to cable. Anyone have experience with SNET DSL? I ordered it with NTPLEX.net as my ISP. You can chose your own ISP. I just checked dslreports.com not very encouraging. Not very many happy people. I guess I'll find out for myself. Recently my cable service reduced the bandwidth. Now upstreams average 16k and downstream 400k. There has to be something better. Several users on my node (all BSD/Linux users) have been enjoying our own little private network with speeds up to 900k both ways.(600k average) Now it's terrible. They now limited the internal network to 33k between users. Compared to before it's like putting us on dialups. -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
PPPoE
I know this seem like a repetative question, but is there going to be any PPPoE kervel level support for FreeBSD any time soon? Or is there already.. if not is there a package someone can recommend to use temporarily with FreeBSD 3.3 Stable. Thanx! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
