RFC 4638 client support (PPPoE MTU > 1492) - testing
-
Not sure, IPv4 gives error about wrong total length, IPv6 look ok.
All wrong total length 92 instead of 1500 means is that the Google server handling traffic to 8.8.4.4 in your location is configured to respond with shorter packets than 1500 bytes. Try some different destinations by IP address or DNS name. Hopefully you'll find something that responds with 1500 bytes.
The server you are reading this on:
-
responds to ping -D -s 1472 -c 10 forum.pfsense.org with 1480 bytes (1500 bytes when you add in the 20 byte IPv4 header)
-
responds to ping6 -D -s 1452 -c 10 forum.pfsense.org with 1460 bytes (1500 bytes when you add in the 40 byte IPv6 header)
Everything else you posted is as expected.
-
-
Yes, that is it!
_ping -D -s 1472 -c 10 forum.pfsense.org
PING forum.pfsense.org (208.123.73.18): 1472 data bytes 1480 bytes from 208.123.73.18: icmp_seq=0 ttl=49 time=116.153 ms 1480 bytes from 208.123.73.18: icmp_seq=1 ttl=49 time=114.547 ms 1480 bytes from 208.123.73.18: icmp_seq=2 ttl=49 time=113.842 ms 1480 bytes from 208.123.73.18: icmp_seq=3 ttl=49 time=114.175 ms 1480 bytes from 208.123.73.18: icmp_seq=4 ttl=49 time=115.382 ms 1480 bytes from 208.123.73.18: icmp_seq=5 ttl=49 time=115.378 ms 1480 bytes from 208.123.73.18: icmp_seq=6 ttl=49 time=115.167 ms 1480 bytes from 208.123.73.18: icmp_seq=7 ttl=49 time=114.280 ms 1480 bytes from 208.123.73.18: icmp_seq=8 ttl=49 time=113.387 ms 1480 bytes from 208.123.73.18: icmp_seq=9 ttl=49 time=114.075 ms–- forum.pfsense.org ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 113.387/114.639/116.153/0.809 ms_ -
Tested and working on 2.3. I used the patch in post 11 and the most recent build.
ping -D -s 1472 -c 3 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 1472 data bytes 1480 bytes from 8.8.8.8: icmp_seq=0 ttl=52 time=115.295 ms 1480 bytes from 8.8.8.8: icmp_seq=1 ttl=52 time=115.393 ms 1480 bytes from 8.8.8.8: icmp_seq=2 ttl=52 time=115.577 ms --- 8.8.8.8 ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 115.295/115.422/115.577/0.117 ms(PPP log in reverse order)
Jan 4 10:46:33 ppp [wan] IFACE: Rename interface ng0 to pppoe0 Jan 4 10:46:33 ppp [wan] IFACE: Up event Jan 4 10:46:32 ppp [wan] 2.3.4.5 -> 1.1.1.1 Jan 4 10:46:32 ppp [wan] IPCP: LayerUp Jan 4 10:46:32 ppp [wan] IPCP: state change Ack-Sent --> Opened Jan 4 10:46:32 ppp [wan] SECDNS 2.2.2.2 Jan 4 10:46:32 ppp [wan] PRIDNS 3.3.3.3 Jan 4 10:46:32 ppp [wan] IPADDR 2.3.4.5 Jan 4 10:46:32 ppp [wan] IPCP: rec'd Configure Ack #3 (Ack-Sent) Jan 4 10:46:32 ppp [wan] SECDNS 2.2.2.2 Jan 4 10:46:32 ppp [wan] PRIDNS 3.3.3.3 Jan 4 10:46:32 ppp [wan] IPADDR 2.3.4.5 Jan 4 10:46:32 ppp [wan] IPCP: SendConfigReq #3 Jan 4 10:46:32 ppp [wan] SECDNS 2.2.2.2 Jan 4 10:46:32 ppp [wan] PRIDNS 3.3.3.3 Jan 4 10:46:32 ppp [wan] 2.3.4.5 is OK Jan 4 10:46:32 ppp [wan] IPADDR 2.3.4.5 Jan 4 10:46:32 ppp [wan] IPCP: rec'd Configure Nak #2 (Ack-Sent) Jan 4 10:46:32 ppp [wan] IPV6CP: LayerFinish Jan 4 10:46:32 ppp [wan] IPV6CP: state change Req-Sent --> Stopped Jan 4 10:46:32 ppp [wan] IPV6CP: protocol was rejected by peer Jan 4 10:46:32 ppp [wan_link0] LCP: protocol IPV6CP was rejected Jan 4 10:46:32 ppp [wan_link0] LCP: rec'd Protocol Reject #63 (Opened) Jan 4 10:46:32 ppp [wan] SECDNS 0.0.0.0 Jan 4 10:46:32 ppp [wan] PRIDNS 0.0.0.0 Jan 4 10:46:32 ppp [wan] IPADDR 0.0.0.0 Jan 4 10:46:32 ppp [wan] IPCP: SendConfigReq #2 Jan 4 10:46:32 ppp [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Jan 4 10:46:32 ppp [wan] IPCP: rec'd Configure Reject #1 (Ack-Sent) Jan 4 10:46:32 ppp [wan] IPCP: state change Req-Sent --> Ack-Sent Jan 4 10:46:32 ppp [wan] IPADDR 1.1.1.1 Jan 4 10:46:32 ppp [wan] IPCP: SendConfigAck #173 Jan 4 10:46:32 ppp [wan] 1.1.1.1 is OK Jan 4 10:46:32 ppp [wan] IPADDR 1.1.1.1 Jan 4 10:46:32 ppp [wan] IPCP: rec'd Configure Request #173 (Req-Sent) Jan 4 10:46:32 ppp [wan] IPV6CP: SendConfigReq #1 Jan 4 10:46:32 ppp [wan] IPV6CP: state change Starting --> Req-Sent Jan 4 10:46:32 ppp [wan] IPV6CP: Up event Jan 4 10:46:32 ppp [wan] SECDNS 0.0.0.0 Jan 4 10:46:32 ppp [wan] PRIDNS 0.0.0.0 Jan 4 10:46:32 ppp [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Jan 4 10:46:32 ppp [wan] IPADDR 0.0.0.0 Jan 4 10:46:32 ppp [wan] IPCP: SendConfigReq #1 Jan 4 10:46:32 ppp [wan] IPCP: state change Starting --> Req-Sent Jan 4 10:46:32 ppp [wan] IPCP: Up event Jan 4 10:46:32 ppp [wan] IPV6CP: LayerStart Jan 4 10:46:32 ppp [wan] IPV6CP: state change Initial --> Starting Jan 4 10:46:32 ppp [wan] IPV6CP: Open event Jan 4 10:46:32 ppp [wan] IPCP: LayerStart Jan 4 10:46:32 ppp [wan] IPCP: state change Initial --> Starting Jan 4 10:46:32 ppp [wan] IPCP: Open event Jan 4 10:46:32 ppp [wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps Jan 4 10:46:32 ppp [wan_link0] Link: Join bundle "wan" Jan 4 10:46:32 ppp [wan_link0] Link: Matched action 'bundle "wan" ""' Jan 4 10:46:32 ppp [wan_link0] LCP: authorization successful Jan 4 10:46:32 ppp [wan_link0] MESG: Login ok Jan 4 10:46:32 ppp [wan_link0] PAP: rec'd ACK #1 len: 13 Jan 4 10:46:31 ppp [wan_link0] LCP: LayerUp Jan 4 10:46:31 ppp [wan_link0] PAP: sending REQUEST #1 len: 22 Jan 4 10:46:31 ppp [wan_link0] PAP: using authname "xxxxxxx" Jan 4 10:46:31 ppp [wan_link0] LCP: auth: peer wants PAP, I want nothing Jan 4 10:46:31 ppp [wan_link0] LCP: state change Ack-Sent --> Opened Jan 4 10:46:31 ppp [wan_link0] MAGICNUM 17677400 Jan 4 10:46:31 ppp [wan_link0] MRU 1500 Jan 4 10:46:31 ppp [wan_link0] LCP: rec'd Configure Ack #2 (Ack-Sent) Jan 4 10:46:31 ppp [wan_link0] MAGICNUM 17677400 Jan 4 10:46:31 ppp [wan_link0] MRU 1500 Jan 4 10:46:31 ppp [wan_link0] LCP: SendConfigReq #2 Jan 4 10:46:31 ppp [wan_link0] PROTOCOMP Jan 4 10:46:31 ppp [wan_link0] LCP: rec'd Configure Reject #1 (Ack-Sent) Jan 4 10:46:31 ppp [wan_link0] LCP: state change Req-Sent --> Ack-Sent Jan 4 10:46:31 ppp [wan_link0] MAGICNUM 4413e422 Jan 4 10:46:31 ppp [wan_link0] AUTHPROTO PAP Jan 4 10:46:31 ppp [wan_link0] MRU 1500 Jan 4 10:46:31 ppp [wan_link0] LCP: SendConfigAck #62 Jan 4 10:46:31 ppp [wan_link0] MAGICNUM 4413e422 Jan 4 10:46:31 ppp [wan_link0] AUTHPROTO PAP Jan 4 10:46:31 ppp [wan_link0] MRU 1500 Jan 4 10:46:31 ppp [wan_link0] LCP: rec'd Configure Request #62 (Req-Sent) Jan 4 10:46:31 ppp [wan_link0] MAGICNUM 17677400 Jan 4 10:46:31 ppp [wan_link0] MRU 1500 Jan 4 10:46:31 ppp [wan_link0] PROTOCOMP Jan 4 10:46:31 ppp [wan_link0] LCP: SendConfigReq #1 Jan 4 10:46:31 ppp [wan_link0] LCP: state change Starting --> Req-Sent Jan 4 10:46:31 ppp [wan_link0] LCP: Up event Jan 4 10:46:31 ppp [wan_link0] Link: UP event Jan 4 10:46:31 ppp [wan_link0] PPPoE: connection successful Jan 4 10:46:31 ppp [wan_link0] PPPoE: rec'd PPP-Max-Payload '1500' Jan 4 10:46:31 ppp PPPoE: rec'd ACNAME "AL301" Jan 4 10:46:31 ppp [wan_link0] PPPoE: Connecting to 'any' Jan 4 10:46:31 ppp [wan_link0] PPPoE: Set PPP-Max-Payload to '1500' Jan 4 10:46:31 ppp [wan_link0] LCP: LayerStart Jan 4 10:46:31 ppp [wan_link0] LCP: state change Initial --> Starting Jan 4 10:46:31 ppp [wan_link0] LCP: Open event Jan 4 10:46:31 ppp [wan_link0] Link: OPEN event Jan 4 10:46:31 ppp [wan] Bundle: Interface ng0 created Jan 4 10:46:31 ppp web: web is not running Jan 4 10:46:31 ppp process 4843 started, version 5.7 (root@pfSense_master_amd64_amd64-pfSense_master-job-01 19:14 31-Dec-2015) Jan 4 10:46:31 ppp Multi-link PPP daemon for FreeBSD -
RFC 4638 support has now been merged into pfSense 2.3 and should show up in snapshots shortly.
-
Great, so if it is available in snapshot, I can delete your RFC 4638 patch.
But I guess we still need your PPP IPv6 fix to get an initial IPv6 connection, right?
-
You'll need to wait a few more hours before the RFC 4638 patch is in the latest snapshot and upgrades - there is a time lag between code being committed and that code being built and offered for download.
I've just reworked the PPP IPv6 patch into what I hope is a final version - I'll post more about that in the IPv6 forum thread shortly. If the latest version of that patch behaves correctly, I'll submit a pull request in the hope that that, too, will be merged into pfSense.
-
I just updated my amd64 pfSense 2.3 virtual machine to 2.3.a.20160105.0522, which includes the RFC 4638 functionality. I would expect i386 to catch up shortly if it has not already done so.
I've just posted a proper 2.3 version of the PPP IPv6 patch - I'd appreciate if you can test that and feed back in the other thread.
-
Will test this evening (in about 5 hours).
You mention version: 2.3.a.20160105.0522, but I see 2.3.a.20160105.0524, I assume this is the same version
Will report back about result of test
-
You mention version: 2.3.a.20160105.0522, but I see 2.3.a.20160105.0524, I assume this is the same version
That's strange - I copied and pasted that string from somewhere, but when I went back to check it, I also saw 2.3.a.20160105.0524.
There is already a later build - 2.3 is rebuilt around every three hours at the moment.
-
2.3 is now BETA!
Removed RFC 4638 patch.
Updated to pfSense from 2.3.a to
2.3-BETA (amd64)
built on Tue Jan 05 13:19:26 CST 2016
FreeBSD 10.2-STABLERefetched and applied PPP IPv6 fix and rebooted.
MTU=1500 en instant IPv6 access. Looking good, have to wait if stable.
edit: Please go ahead for pull request!
Your effort paid off, thank you so much David_W!