Upgrade to 2.7.0 stop PPPoE working
-
@IanJanus said in Upgrade to 2.7.0 stop PPPoE working:
The interface appear to attempt to connect, it gets an ip and then goes down again, this keeps on repeating.
Take a look at the ppp log - this should be more helpful ...
-
I have had a look at the log...but I don't understand most of it.
I attach a copy of it. ppp_log.txt
-
@IanJanus said in Upgrade to 2.7.0 stop PPPoE working:
I have had a look at the log...but I don't understand most of it.
I am not a specialist but overlooking I do not see something that pops out ...
-
@fireodo the only thing I thought was curious was "Jul 1 12:36:02 ppp 74415 caught fatal signal TERM"
though I have no idea quite what it means or what I need to do?
-
@IanJanus said in Upgrade to 2.7.0 stop PPPoE working:
the only thing I thought was curious was "Jul 1 12:36:02 ppp 74415 caught fatal signal TERM"
Thats normal when pppoe is restarting
-
J jimp moved this topic from Problems Installing or Upgrading pfSense Software on
-
Did you ever figure this out? Having exact same problem. Can ping from pppoe interface out to google but nothing internal after reboot. If i restore config it comes back to life until a reboot. Thanks
-
Check it still has a default route. Check it has the auto NAT rules in place if you can ping from pfSense but not client behind it.
-
Thanks Stephen. That was the issue. Not enough coffee today obviously. Default route was missing so definitely not a version issue. Thanks again i owe you one of the missing coffees :)
-
That could still be a bug. The default route should be automatically set when the PPPoE WAN comes up. Unless it was set to something else statically perhaps?
-
Thanks Stephen. It was actually the default gateway setting (I've never had to set a static route). I've always left it as automatic (worked flawlessly since i installed it on my watchguard xtm5 years ago). All of a sudden after the update, traffic would only route past pppoe gateway if I manually set the default gateway to my pppoe interface. I could ping the ISP gateway but not past it, unless i manually set it. Maybe i should have chosen manual from day 1? Either way works great now like it did before. Another change i did was set the outbound Nat to automatic instead of hybrid. Hope this helps anyone else with similar issues.
-
If you have more than one gateway defined, like a VPN gateway or an internal LAN gateway, you should definitely set WAN_PPPoE as default rather than automatic. Otherwise it may default to one of the others and that's almost always invalid.
