Giancarlo, Thanks for you suggestions. Actually, I've tried without changing the MTU on devices (both), with no success. Then, reading 5.4 man-pages I saw that, and just tried it (with no success either).
The reason for upgrading is due to hardware. As the Sun machine is too old, and it works as the firewall/router of the office (critical), the plan was to upgrade also the software. If this problem persists, the idea was to try installing 4.9 (which does the job I need) on the new machine to check if it connects through PPPoE. Installing 5.5 is an alternative too, to check if it works.... I'm not a expert on this part. So which would be the parameters to run tcpdump and try to find something? And also... With -current, how does PPPoE connection works? How reliable it would be running it in "production"? Thanks again, Felipe On Tue, Jul 22, 2014 at 11:02 PM, Giancarlo Razzolini <grazzol...@gmail.com> wrote: > Em 22-07-2014 18:28, Felipe Mesquita de Oliveira escreveu: > > # cat /etc/hostname.pppoe0 > > inet 0.0.0.0 255.255.255.255 NONE mtu 1500 pppoedev bge0 authproto pap > > # cat /etc/hostname.bge0 > > up mtu 1508 > You really need to use jumbo frames? Some physical devices have > performance issues and some even fail altogether with them. Also, from > 4.9 to 5.4 there where thousands of changes. From 5.4 to 5.5 there were > many changes. And from 5.5 to current the same holds true. Please try to > debug the issues using either 5.5 stable or, preferably, current. I'd > change your mtu to 1500 on the physical if and 1492 on the pppoe if. > Please note that you need to "clamp" your mss using pf. The following > rule generally does the job: > > match out on pppoe scrub (max-mss 1440) > > Also, besides the ifconfig debug, if you can tcpdump on the physical > interface the entire pppoe negotiation (or not) also would be helpful. > Even with pppoe(8) being removed from current, you could try it on 5.5, > just to see if the problem remains. > > Cheers, > > -- > Giancarlo Razzolini > GPG: 4096R/77B981BC
