I guess this is one of those things that keeps "biting" into you until you get it resolved. After some experimentation, while I never thought this would have such an effect--especially with net.inet.tcp.rfc1323=1 and net.inet.tcp.sack=1 by default--the following simple additions to /etc/sysctl.conf resolve the issue:
net.inet.tcp.recvspace=65536 net.inet.tcp.sendspace=65536 FWIW, analysis of the Windows PPPoE client in action shows this to be set to 65535. Because of my good experience with my cable connection, I never really considered Bandwidth-Delay Product having such an effect on this DSL connection, but, in this case, it clearly does. Another day, another lesson learned and another one for the archives... Danny Melameth, Daniel D. wrote: > I think I'm going to leave this as an unresolved case--shame though. > > I also performed the following: > > * Replaced my ActionTec gt701 modem with a Cisco 678 (was going to do > this anyway) and the same issue--Windows is fast, OpenBSD is not > * Replaced xl with fxp and the same issue--however, OpenBSD clearly > likes fxp better as I was able to get over 90Mb/s (under 10 percent > interrupt usage) doing a crossover ftp transfer (compared to the > 40Mb/s on xl) > * Took Kevin's suggestion and played with tcpdump -tt, but I wasn't > sure what to look for and it seems fine. Here's a snippet: > > $ sudo tcpdump -ntti fxp0 > tcpdump: listening on fxp0, link-type EN10MB > 1119059986.989027 PPPoE-Session > code Session, version 1, type 1, id 0xb394, length 78 > IP: 216.x.x.x.2853 > 200.144.121.33.123: v4 client strat 0 > poll 0 prec 0 [tos 0x10] > 1119059987.190136 PPPoE-Session > code Session, version 1, type 1, id 0xb394, length 78 > IP: 200.144.121.33.123 > 216.x.x.x.2853: v4 server strat 2 > poll 0 prec 0 > > $ sudo tcpdump -ntti pppoe0 > tcpdump: listening on pppoe0, link-type PPP_ETHER > 1119059986.989021 216.x.x.x.2853 > 200.144.121.33.123: v4 client > strat 0 poll 0 prec 0 [tos 0x10] > 1119059987.190145 200.144.121.33.123 > 216.x.x.x.2853: v4 server > strat 2 poll 0 prec > > I don't get it. I'm not sure what else to try or look at. > > Regards, > D > > Melameth, Daniel D. wrote: > > Kevin wrote: > > > On 6/7/05, Can Erkin Acar <[EMAIL PROTECTED]> wrote: > > > > Melameth, Daniel D. wrote: > > > > > Prior to migrating to DSL, this same card was used for a cable > > > > > connection and doing more than 1.5Mb/s. > > > > > > > > This really does not mean much. It could be a negotiation > > > > problem. Was your old cable modem ethernet connection 10BaseT ? > > > > 100baseTX full-duplex > > > > > > from a previous post ... > > > > > > > > > xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu > > > > > 1500 address: 00:04:75:ac:05:48 > > > > > media: Ethernet autoselect (100baseTX full-duplex) > > > > > > > > Perhaps your ADSL modem/switch has problems negotiating with > > > > your card, or your cable might have problems. > > > > The same cable was used with the Windows box. > > > > > It'd help if the OP can provide the output of 'netstat -in' after > > > the PPPoE has been up for a while. > > > > Here is the output from the time I rebooted the OpenBSD box this > > morning till the time I got home from work (which means it didn't > > get used much): > > > > $ netstat -in > > Name Mtu Network Address Ipkts Ierrs Opkts > > Oerrs Colls lo0 33224 <Link> 0 > > 0 0 0 0 lo0 33224 127/8 127.0.0.1 > > 0 0 0 0 0 lo0 33224 ::1/128 ::1 > > 0 0 0 0 0 lo0 33224 fe80::%lo0/ fe80::1%lo0 > > 0 0 0 0 0 pflog0 33224 <Link> > > 0 0 0 0 0 pfsync0 2020 <Link> > > 0 0 0 0 0 enc0* 1536 <Link> > > 0 0 0 0 0 wi0 1500 <Link> > > 00:02:6f:09:58:b2 10227 0 11042 0 519 wi0 1500 > > 192.168.255 192.168.255.254 10227 0 11042 0 519 wi0 > > 1500 fe80::%wi0/ fe80::202:6fff:fe 10227 0 11042 0 519 > > xl0 1500 <Link> 00:04:75:ac:05:48 65278 0 48429 > > 0 0 xl0 1500 192.168.255 192.168.255.221 65278 0 > > 48429 0 0 xl0 1500 fe80::%xl0/ fe80::204:75ff:fe 65278 > > 0 48429 0 0 pppoe0 1492 <Link> > > 65275 0 48425 3 0 pppoe0 1492 0.0.0.0/32 70.x.x.x > > 65275 0 48425 3 0 pppoe0 1492 fe80::%pppo > > fe80::202:6fff:fe 65275 0 48425 3 0 > > > > > > Full-duplex does not detect transmission errors, so you would > > > > not see them on netstat -i output. You could try setting media > > > > to "10BaseT half-duplex" this usually helps you notice if there > > > > is a problem, and can sometimes solve it. > > > > ifconfig takes xl0 media 10baseT, but adding half-duplex yields: > > > > $ sudo ifconfig xl0 media 10baseT half-duplex > > ifconfig: half-duplex: bad value > > > > Regardless, with ifconfig xl0 media 10baseT, both the modem and > > OpenBSD box show the connection at 10Mb/s, but the issue persists. > > > > > > And do try another ethernet card if possible. > > > > > > Seconded on both points. > > > > This is a CardBus card and I only have other 3Coms--I tried another > > identical 3Com card with the same poor results. > > > > > One thing I've found very helpful in debugging PPPoE has been to > > > use either the "-tttt" (time between packets) or "-tt" (absolute > > > epoch time) options on tpcdump, watching the packets on both the > > > real Ethernet interface and the tunnel (pppoe0) interface, in two > > > side-by-side windows. > > > > I was about to give this tcpdump timing a shot, but decided to > > spend a few more hours trying some other tests. Here is the > > results of my findings (all devices connected to the DSL modem were > > directly connected): > > > > * Reconfiguring the modem to handle the PPPoE connection, instead of > > the OpenBSD box, and reconfiguring the OpenBSD box as a workstation > > (meaning no hostname.pppoe0) yields the same 1.5Mb/s Internet > > download speed--which would suggest the issue is not with 3.7's > > kernel pppoe but, perhaps, related to xl * Removing the xl card > > from the OpenBSD box and putting it into a Windows box yields a > > 5.5Mb/s Internet download speed--which would suggest the card > > performs fine * Putting the xl card back into the OpenBSD box and > > performing an ftp transfer between the OpenBSD box and another box > > connected via crossover cable yields a 40Mb/s download speed--I'm > > not sure what this suggests, but it seems, in some way, there is > > some kind of interoperability issue between xl, OpenBSD and my DSL > > modem > > > > I'm interested in hearing some feedback on the above tests. Also, > > since it seems xl hardware is not well touted by those in the know, > > what Ethernet CardBus cards are recommended? I'll assume ne and rl > > are not one of these and I'll gladly pickup a recommended CardBus > > card to address this issue--particularly if the price is right > > (thinking eBay). > > > > Thanks again to those who've taken the time to read and respond to > > this thread, Danny
