Strange one with dual WAN
-
Hi all!
I have a really nasty problem with dual WAN config.
Primary is DHCP and secondary is PPPoE.When I reset modem it takes 3-4 minutes to become operational.
PPPoE IPv4 and IPv6 come up just fine.But primary WAN DHCP doesn
t. In DHCP logs it
s requesting IP from address on PPPoE link instead on its own link. Gateway shows as pending, DHCP log says:Jun 29 20:35:52 dhcpleases Sending HUP signal to dns daemon(90399) Jun 29 20:35:52 dhcpleases Sending HUP signal to dns daemon(90399) Jun 29 20:35:52 dhcpd Server starting service.
Gateway log says:
Jun 29 20:35:49 dpinger WAN_DHCP 85.XX.XXX.1: sendto error: 65 Jun 29 20:35:49 dpinger WAN_DHCP 85.XX.XXX.1: sendto error: 65
System log:
Jun 29 20:47:48 kernel arpresolve: can't allocate llinfo for 85.XX.XXX.1 on em2 Jun 29 20:47:41 kernel arpresolve: can't allocate llinfo for 85.XX.XXX.1 on em2 Jun 29 20:47:38 kernel arpresolve: can't allocate llinfo for 85.XX.XXX.1 on em2 Jun 29 20:47:38 kernel arpresolve: can't allocate llinfo for 85.XX.XXX.1 on em2
Point is, it never comes back. When modem is OK if I just re-plug eth cable then it works just fine.
Problematic are those 3-4 minutes while modem is initializing and pfsense sees link as up but of course it can not establish DHCP or PPPoE just yet.In addition, on pppoe there is also IPv6 configured and when PPPoE comes up IPv6 is working just fine, but gateway status is reporting pending which is not ok.
Also in interface status, there is no IPv6 Address "2001:xxxx:xxxxxx:xxx:xxxx:xxxx". Disconnect and then connect solves this one.Any idea how to fine tune the thing so that modem reset which takes 3-4 minutes won`t be a problem?
Thanks!
-
Look at this thread i opened, i think it's the same bug. there is a open Redmine ticket (#6495).
-
Hi!
No, this is totally different.
My DHCP WAN never recovers while pppoe does and and sets correct route.