PPPoE problems after upgrading from 2.4.2 to 2.4.4
-
@netblues yes, tried first by updating, then by installing a fresh 2.4.4 and importing the settings and then on a fresh 2.4.4 and manually creating the pppoe connection. Didn't work with the same errors all the time.
For info, I'm running it on esxi 6.5 with a quad gigabit eth card.
-
@joxxxx I suppose you have disabled all 3 hardware offload options on advanced/networking.
(meaningless for a virtual network interface, by design...)And what are the exact errors?
-
@netblues Actually, Hardware TCP Segmentation Offloading and Hardware Large Receive Offloading were disabled, but not Hardware Checksum Offloading.
The errors are :
[opt1] IFACE: Adding IPv4 address to pppoe0 failed(IGNORING for now. This should be only for PPPoE friendly!): File exists[opt1] IFACE: Removing IPv4 address from pppoe0 failed(IGNORING for now. This should be only for PPPoE friendly!): Can't assign requested addressIt then cycles infinitely, each time getting a new wan ip and throwing the same errors.
Thanks a lot for your help !
-
@joxxxx This is something else. Have you tried with hardware checksum offloading disabled?
-
@netblues Not yet, I'll boot up the 2.4.4 vm and test it out. (On 2.3.3 hardware offloading doesn't change anything).
-
Ok, just tried it and still the same, here some more logs (appart of the recurring file exists etc. from above) :
Nov 22 14:00:50 ppp [opt1] IFACE: Up event Nov 22 14:00:50 ppp [opt1] IFACE: Rename interface ng0 to pppoe0 Nov 22 14:00:50 ppp [opt1] IPCP: rec'd Configure Ack #3 (Ack-Sent) Nov 22 14:00:50 ppp [opt1] IPADDR 188.XX.XX.XX Nov 22 14:00:50 ppp [opt1] IPCP: state change Ack-Sent --> Opened Nov 22 14:00:50 ppp [opt1] IPCP: LayerUp Nov 22 14:00:50 ppp [opt1] 188.XX.XX.XX -> 10.0.0.1 Nov 22 14:00:50 ppp [opt1] IFACE: Adding IPv4 address to pppoe0 failed(IGNORING for now. This should be only for PPPoE friendly!): File existsStrange thing is that it talks about ipv6 although I disabled it everywhere I could. It seems like on 2.4.3 it doesn't do that.
Even updated to 2.4.5-dev to see, but still the same.
-
Strange as it is it seems it manages to connect, negotiate, auth, get ip and then fail.
Any ideas why a seemingly public ip is being changed to a private one?(10.0.01) Does this happen on other tests? -
@netblues 10.0.0.1 is the pf lan address. I don't know why it does that actually. There are 3 phases to the connection process. First it's 0.0.0.0, then 10.0.0.1 and then the real ip address. Or sometimes starts with 10.0.0.1, then 0.0.0.0 and the the real ip.
10.0.0.1 seems to be taken as the pppoe gateway, maybe that's not "allowed" anymore in 2.4.4 ?
On the dashboard, the gateway for pppoe says 10.0.0.1 and the interface has the correct ip.Here is the log of the 2.3.3 that works :
Nov 22 14:05:26 ppp [opt1] IFACE: Up event Nov 22 14:05:26 ppp [opt1] IFACE: Rename interface ng0 to pppoe0 Nov 22 14:05:26 ppp [opt1] IPCP: rec'd Configure Nak #2 (Ack-Sent) Nov 22 14:05:26 ppp [opt1] IPADDR 188.XX.XX.XX Nov 22 14:05:26 ppp [opt1] 188.XX.XX.XX is OK Nov 22 14:05:26 ppp [opt1] IPCP: SendConfigReq #3 Nov 22 14:05:26 ppp [opt1] IPADDR 188.XX.XX.XX Nov 22 14:05:26 ppp [opt1] IPCP: rec'd Configure Ack #3 (Ack-Sent) Nov 22 14:05:26 ppp [opt1] IPADDR 188.XX.XX.XX Nov 22 14:05:26 ppp [opt1] IPCP: state change Ack-Sent --> Opened Nov 22 14:05:26 ppp [opt1] IPCP: LayerUp Nov 22 14:05:26 ppp [opt1] 188.XX.XX.XX-> 10.0.0.1Nov 22 14:05:26 ppp [opt1] 188.XX.XX.XX is OK : This seems to be the line that fails on 2.4.4 with "File exists".
-
@netblues said in PPPoE problems after upgrading from 2.4.2 to 2.4.4:
Any ideas why a seemingly public ip is being changed to a private one?(10.0.01) Does this happen on other tests?
It's not changing the IP, it's trying to add the IP with a default gateway of 10.0.0.1. So check your gateway settings, is the gateway for WAN set to dynamic, do you have any other gateways on your system. Make sure you have either selected the right default gateway or a properly configured gateway group if you have multiple wan gateways.
Edit: and if your PPPoE provider really uses 10.0.0.1 as their gateway address you can't use that on your LAN.
-
@joxxxx there is new functionality dealing with gateways for the box.
Please check it.
Its not right to have the lan ip as a ppp gateway.
(in system/routing gateways...) -
@grimson I have indeed 2 WAN. The main cable network that gets the info through DHCP (provider router in gateway mode) and the fiber 1Gbit ftth through pppoe (OPT1).
Gateways are dynamic and both wan are in a gateway group with the fiber set as Tier 1 and the cable as Tier 2.I don't think the provider uses 10.0.0.1 as gateway, but pfsense sees it that way. The thing is, why does it work on 2.3.3 and not on 2.4.4 and 2.4.5 ?
-
Show the whole PPP log, not just a small part of it. As for why it doesn't work on 2.4.4, mpd5 has received quite a few updates since then and it may very well check the validity of the gateway IP now.
@joxxxx said in PPPoE problems after upgrading from 2.4.2 to 2.4.4:
I don't think the provider uses 10.0.0.1 as gateway, but pfsense sees it that way.
If you get 10.0.0.1 as gateway on 2.3.3 too, and the connection works then yes your provider is using that as the gateway address.
-
If they are actually using 10.0.0.1 as the gateway, which is possible, then you should not be using that subnet internally.
It may work as it will probably be /32 and hence a more specific route but eliminating that potential conflict would be a good test.
Steve
-
Oh god, I feel stupid now... You guys nailed it, the fiber modem somehow uses 10.0.0.1 as the actual pppoe gateway !
I changed the lan network to something else and the connection worked immediately after.Thanks a thousand times for your help ! Finally it's fixed. I never thought they'd use this network for their actual gateway.
So, good to know, 2.4.4+ makes pppoe more strict ! :)
-
The above mentioned fix for @Joxxxx seems to solve a quite different issue then what I (and my others here) had as it turned out.
So, just to give everyone an update on the PPPoE "broken-until-reboot" issue(s): I am happy to report that I was not able to break my PPPoE connection with any interface config change after upgrading to 2.4.4-RELEASE-p1. I tried disabling/enabling interfaces as well as creating and removing one - PPPoE stayed up during my testing. Any of these changes would have caused PPPoE to spit out the already mentioned errors until a reboot prior to the upgrade.
-
@cetteup said in PPPoE problems after upgrading from 2.4.2 to 2.4.4:
The above mentioned fix for @Joxxxx seems to solve a quite different issue then what I (and my others here) had as it turned out.
So, just to give everyone an update on the PPPoE "broken-until-reboot" issue(s): I am happy to report that I was not able to break my PPPoE connection with any interface config change after upgrading to 2.4.4-RELEASE-p1. I tried disabling/enabling interfaces as well as creating and removing one - PPPoE stayed up during my testing. Any of these changes would have caused PPPoE to spit out the already mentioned errors until a reboot prior to the upgrade.
Thank you for posting this. I have a CenturyLink PPPoE VLAN'ed connection that I didn't want to take a chance on so I skipped 2.4.4. This makes me feel better about upgrading to the latest release.
-
I have encountered the same pppoe error in 2.5.2, without using a local subnet similar with the gateway address. What now?
IFACE: Adding IPv4 address to pppoe0 failed(IGNORING for now. This should be only for PPPoE friendly!): File exists
