WAN (PPPoE) and OPT1's gateway mix-up
-
Hi,
I've been experiencing a strange bug with my failover setup. I'm running the 1.2.3 release with a multi WAN failover setup. As my primary connection, on the WAN side I have an ISP with a PPPoE connection. On the OPT1 I have a cable connection with a transparent modem. OPT1 is setup to get it's settings via DHCP.
Overall the failover setup works flawlessly, however a few times after a PPPoE failure, when the cable kicks in, I've noticed that after the PPPoE is back up it gets the cable's gateway as its own in the PPPoE's settings. Even if I try to disconnect/connect the PPPoE in the WebUI it doesn't go away. My only option at this point is to restart the box and when it is back up the PPPoE's setting are all OK.
The problem is that when the PPPoE is down at least I have Internet through my backup connection however slow it is, but when the PPPoE comes back up with the wrong gateway, the Failover turns back to it as it reports it UP (there is ping to the PPPoE's monitoring IP which is its actual gateway), as it is my primary connection and I get completely cut off internet.
Is there any solution to solve this problem?
-
So, no ideas?!
Is there a way to set PPPoE settings, particularly the gateway IP address, to static ones?
Cheers.
-
Sorry for bringing this up again, but as I've encountered the bug once again I've taken a screenshot. As I said before, as the PPPoE somehow gets the gateway setting of the OPT1, the Internet connection is lost and the problem will not go away until I reboot.
-
One solution would be to use a NAT Router on WAN, with fixed IP for the pfSense WAN interface.
Edit: activate "Dial-on-Demand" mode, Idle timeout of "0" - this should do the trick.
-
I am facing 100% same issue. Were you able to sort this issue ?
Sorry for bringing this up again, but as I've encountered the bug once again I've taken a screenshot. As I said before, as the PPPoE somehow gets the gateway setting of the OPT1, the Internet connection is lost and the problem will not go away until I reboot.
-
i encounter same problem. any notes on this?
-
I believe the issue displayed here is only cosmetic on the Status>Interfaces page. Though there could be some other issue there on 1.2.3, would be fixed on 2.0 though.