Date: Wed, 26 Jun 2002 23:14:57 -0400 From: Mike Tancsa <mike@sentex.net> To: freebsd-net@freebsd.org Subject: Re: SOLVED! Native PPPoE broken (4.6-STABLE), RP-PPPoE working?! Message-ID: <4e0lhusn1nhnr8fdc591spcstfs8s8a532@4ax.com> In-Reply-To: <5.1.0.14.0.20020625112547.057eb870@marble.sentex.ca> References: <l74dhug4bgj2ls2s8r8gkse667tvrfos6u@4ax.com> <Pine.BSF.4.21.0206232037520.44896-100000@InterJet.elischer.org> <2trfhu0tbekq67seicn4amdovp7564ji62@4ax.com> <3D183606.BBD1DE54@tix.ch> <5.1.0.14.0.20020625112547.057eb870@marble.sentex.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Just to close off this issue an feed it to the archives in case anyone = else runs into this issue, the telco found the article below in the vendor's knowledge database. =20 Again to summarize, if you use FreeBSD, PPPoE and your ISP or your ISP's telco uses an ERX as the PPPoE concentrator, make sure you disable and prevent VJ header compression as it will not work. Bell Canada has been slowly deploying these boxes so if you use Sympatico, or your ISP is in Quebec or Ontario, you will start to run into this issue as the telco = slow gets rid of their Redback SMSes and replaces them with Unisphere's ERX boxes. =20 The solution I found was to make sure that its also disabled and not offered in RADIUS either, so you might have to talk to your ISP if they have it configured, as we did. ---Mike *************************** Knowledge Database - Search Results Knowledge Asset ID#: 1773.00000=20 Subject: The ERX does not support IP header compression as described in = RFC 2507 and RFC 2508.=20 -------------------------------------------------------------------------= --- ---- =20 Type: SW Release: SW Version: =20 Problem Description: The ERX does not support and does not yet have plans to support IP header compression. For a full=20 description of IP header compression refer to RFC 2507 and RFC 2508. It basically says that multiple=20 packets to and from the same destinations can get their headers = compressed to save about 8 bytes per=20 packet.=20 This feature has been requested in case 10349=20 Workaround: =20 Solution: =20 **************************** On Tue, 25 Jun 2002 11:40:48 -0400, in sentex.lists.freebsd.net you = wrote: > >In short, VJ-Header Compression! Why, I dont know. The exact same = config=20 >works agains the SMSes by Redback. But not the Unisphere ERX > >Here is what I did to get it to all work. > >a) On my radius server, I had to get rid of > Framed-Compression =3D Van-Jacobsen-TCP-IP >b) On the FreeBSD box, I had to put > disable vjcomp > > >_Before_, on the Cisco terminating L2TP server we see > >bell-border#show int vi426 >Virtual-Access426 is up, line protocol is up > Hardware is Virtual Access interface > Interface is unnumbered. Using address of Loopback0 (64.7.134.129) > MTU 1492 bytes, BW 18868 Kbit, DLY 100000 usec, > reliability 255/255, txload 1/255, rxload 1/255 > Encapsulation PPP, loopback not set > Keepalive set (10 sec) > DTR is pulsed for 5 seconds on reset > LCP Open > Open: IPCP > Last input 01:11:57, output never, output hang never > Last clearing of "show interface" counters 03:33:26 > Queueing strategy: fifo > Output queue 0/40, 0 drops; input queue 0/75, 0 drops > 5 minute input rate 0 bits/sec, 0 packets/sec > 5 minute output rate 0 bits/sec, 0 packets/sec > 9265 packets input, 4481181 bytes, 0 no buffer > Received 0 broadcasts, 0 runts, 0 giants, 0 throttles > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort > 8720 packets output, 1141908 bytes, 0 underruns > 0 output errors, 0 collisions, 0 interface resets > 0 output buffer failures, 0 output buffers swapped out > 0 carrier transitions >bell-border#show int vi426 confi >Virtual-Access426 is an L2TP link interface > >Building configuration... > >interface Virtual-Access426 configuration... >mtu 1492 >ip unnumbered Loopback0 >ip tcp header-compression > >And _after_ > >bell-border#show int vi63 >Virtual-Access63 is up, line protocol is up > Hardware is Virtual Access interface > Interface is unnumbered. Using address of Loopback0 (64.7.134.129) > MTU 1492 bytes, BW 18868 Kbit, DLY 100000 usec, > reliability 255/255, txload 1/255, rxload 1/255 > Encapsulation PPP, loopback not set > Keepalive set (10 sec) > DTR is pulsed for 5 seconds on reset > LCP Open > Open: IPCP > Last input 00:00:09, output never, output hang never > Last clearing of "show interface" counters 00:14:45 > Queueing strategy: fifo > Output queue 0/40, 0 drops; input queue 0/75, 0 drops > 5 minute input rate 0 bits/sec, 0 packets/sec > 5 minute output rate 0 bits/sec, 0 packets/sec > 10 packets input, 217 bytes, 0 no buffer > Received 0 broadcasts, 0 runts, 0 giants, 0 throttles > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort > 8 packets output, 139 bytes, 0 underruns > 0 output errors, 0 collisions, 0 interface resets > 0 output buffer failures, 0 output buffers swapped out > 0 carrier transitions >bell-border#show int vi63 config >Virtual-Access63 is an L2TP link interface > >Building configuration... > >interface Virtual-Access63 configuration... >mtu 1492 >ip unnumbered Loopback0 > > >iscar# ifconfig tun0 >tun0: flags=3D8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1492 > inet6 fe80::2d0:b7ff:fea6:4285%tun0 prefixlen 64 scopeid 0x8 > inet 64.7.134.131 --> 64.7.134.129 netmask 0xffffff00 > Opened by PID 55 >iscar# > >fetch ftp://ftp.isc.org/isc/bind9/9.2.1/bind-9.2.1.tar.gz >Receiving bind-9.2.1.tar.gz (5021044 bytes): 100% >5021044 bytes transferred in 39.9 seconds (122.76 kBps) >iscar# > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-net" in the body of the message Mike Tancsa (mdtancsa@sentex.net) =09 Sentex Communications Corp, =09 Waterloo, Ontario, Canada "Given enough time, 100 monkeys on 100 routers=20 could setup a national IP network." (KDW2) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4e0lhusn1nhnr8fdc591spcstfs8s8a532>