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.
-
@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