1
17.7 Legacy Series / Re: Flapping WAN interface
« on: October 06, 2017, 12:42:08 am »
Well, that was weird... I upgraded from 17.7.4 to 17.7.5 today and there's no more flapping...
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
17.7 Legacy Series / Flapping WAN interface
« on: September 29, 2017, 05:18:26 pm »
One of my WAN interfaces keep flapping every <10 seconds, I simply cannot figure out why. I've already attempted to move it to a different physical port on the firewall, no change.
This is a sample of the logs:
This repeats every just under 10 seconds. I'm not sure what to try now...
This is a sample of the logs:
Quote
Sep 29 14:45:32 opnsense: /usr/local/etc/rc.newwanip: Switching default gateway to EM1_WAN_VDSL_PPPOE (OTHER-WAN-IP)
Sep 29 14:45:31 opnsense: /usr/local/etc/rc.newwanip: On (IP address: FLAPPING-WAN-IP) (interface: EM0_WAN_VIRGIN[wan]) (real interface: em0).
Sep 29 14:45:31 opnsense: /usr/local/etc/rc.newwanip: IP renewal is starting on 'em0'
Sep 29 14:45:31 kernel: arpresolve: can't allocate llinfo for FLAPPING-WAN-GW on em0
Sep 29 14:45:31 kernel: arpresolve: can't allocate llinfo for FLAPPING-WAN-GW on em0
Sep 29 14:45:31 kernel: arpresolve: can't allocate llinfo for FLAPPING-WAN-GW on em0
Sep 29 14:45:31 kernel: arpresolve: can't allocate llinfo for FLAPPING-WAN-GW on em0
Sep 29 14:45:31 kernel: arpresolve: can't allocate llinfo for FLAPPING-WAN-GW on em0
Sep 29 14:45:30 kernel: arpresolve: can't allocate llinfo for FLAPPING-WAN-GW on em0
Sep 29 14:45:30 kernel: em0: link state changed to UP
Sep 29 14:45:30 kernel: arpresolve: can't allocate llinfo for FLAPPING-WAN-GW on em0
Sep 29 14:45:30 kernel: arpresolve: can't allocate llinfo for FLAPPING-WAN-GW on em0
Sep 29 14:45:30 kernel: arpresolve: can't allocate llinfo for FLAPPING-WAN-GW on em0
Sep 29 14:45:29 kernel: arpresolve: can't allocate llinfo for FLAPPING-WAN-GW on em0
Sep 29 14:45:29 kernel: arpresolve: can't allocate llinfo for FLAPPING-WAN-GW on em0
Sep 29 14:45:28 kernel: arpresolve: can't allocate llinfo for FLAPPING-WAN-GW on em0
Sep 29 14:45:28 kernel: arpresolve: can't allocate llinfo for FLAPPING-WAN-GW on em0
Sep 29 14:45:28 kernel: em0: link state changed to DOWN
Sep 29 14:45:28 opnsense: /usr/local/etc/rc.linkup: HOTPLUG: Configuring interface wan
Sep 29 14:45:28 opnsense: /usr/local/etc/rc.linkup: DEVD Ethernet attached event for wan
Sep 29 14:45:28 configd.py: [79bc7ce3-a14c-4667-a1dc-df305fbe7fd4] Linkup starting em0
Sep 29 14:45:28 opnsense: /usr/local/etc/rc.linkup: Clearing states to old gateway FLAPPING-WAN-GW.
Sep 29 14:45:28 opnsense: /usr/local/etc/rc.linkup: DEVD Ethernet detached event for wan
Sep 29 14:45:28 configd.py: [6de0e49b-8cd3-4134-ae61-3ea0b8cdd10c] Linkup stopping em0
This repeats every just under 10 seconds. I'm not sure what to try now...
3
17.7 Legacy Series / Re: WAN over PPPoE loses default IPv4 route in multi-WAN setup
« on: September 29, 2017, 05:08:50 pm »Hi there,
Two times DHCP is tricky, we've had a larger discussion lately about what is supposed to happen and what can be done to end up with a working setup.
The current rationale is:
Go to Firewall: Settings: Advanced and enable "Allow default gateway switching".
Cheers,
Franco
I disconnected the PPPoE interface under Interfaces > Overview, and re-enabled it; result - no IPv4 default route.
System > Log File
Sep 29 14:40:48 opnsense: /usr/local/etc/rc.newwanip: Cannot switch gateway EM1_WAN_VDSL_DHCP6 with undefined address
Sep 29 14:40:48 opnsense: /usr/local/etc/rc.newwanip: Cannot switch gateway EM1_WAN_VDSL_PPPOE with undefined address
Although I do have valid IPs under Interfaces > Overview.
Also, System > Gateways > Status shows Gateway "dynamic" for both though, and gray "Pending" status.
I Disabled / Re-enabled the Interface, this seems to have fixed the issue; not ideal though.
4
16.7 Legacy Series / Re: Flapping WAN interface on 16.7.1
« on: September 29, 2017, 03:48:36 pm »
Did you ever get to the bottom of this? I'm seeing the same issue now, and I've no idea what's going on... Thanks!
5
17.7 Legacy Series / Re: WAN over PPPoE loses default IPv4 route in multi-WAN setup
« on: September 14, 2017, 08:44:18 am »
Thank you Franco! I'll try that when I'm home again, run a few tests and get back to you.
6
17.7 Legacy Series / Re: running native IPv4/IPv6 dual stack
« on: September 13, 2017, 06:04:48 pm »
Hi! The IPv6 /48 that you have, is it allocated to you with no other facilities, or does it come from your ISP via IPv6 Prefix Delegation?
If you're getting it from the ISP via Prefix Delegation, then you don't need to actually configure DHCPv6 on OPNsense; you set the LAN IPv6 interface to track the PPPoE WAN, and that should automagically work.
So in short - need some more details
If you're getting it from the ISP via Prefix Delegation, then you don't need to actually configure DHCPv6 on OPNsense; you set the LAN IPv6 interface to track the PPPoE WAN, and that should automagically work.
So in short - need some more details
7
17.7 Legacy Series / WAN over PPPoE loses default IPv4 route in multi-WAN setup
« on: September 13, 2017, 04:55:24 pm »
I think this may be related to this bug, though I may well be wrong!
I can provide more logs, config etc as required later.
Setup: latest OPNSense installed on an AOpen i45GMt-HR with an HP NC364T NIC (so all NICs are Intel based); LAN is on the onboard NIC (em4), the two WANs (em0, em1) and a DMZ interface (em3) are on the NC364T.
First WAN (em0) is configured with IPv4 DHCP only; it's a cable ISP, there is no IPv6 connectivity provided.
Second WAN (em1) is configured with PPPoE, IPv4 DHCP and IPv6 DHCPv6 (PPPoE dual-stack). I also get an IPv6 DHCP-PD from this, works fine on the LAN etc. This is a VDSL2 ISP, and these gateways are set as the defaults.
I have a couple of gateway groups configured, but no rules in place that use them. I may try removing them to see if it makes a difference.
If I disable/re-enable the PPPoE connection or interface or IPv4 gateway, I completely lose the default IPv4 route unless I completely disable the PPPoE interface or IPv4 gateway.
It doesn't seem to matter what else I do, I just cannot seem to get the PPPoE default IPv4 route back, short of a reboot. The only thing that works is to disable the PPPoE WAN or PPPoE IPv4 gateway completely, which re-instates the Cable WAN as the default IPv4 route. If I don't do that, there is NO IPv4 default route.
I'm happy to provide logs, config details etc, just kindly let me know what would be required, and what tests would be useful. Thank you!
I can provide more logs, config etc as required later.
Setup: latest OPNSense installed on an AOpen i45GMt-HR with an HP NC364T NIC (so all NICs are Intel based); LAN is on the onboard NIC (em4), the two WANs (em0, em1) and a DMZ interface (em3) are on the NC364T.
First WAN (em0) is configured with IPv4 DHCP only; it's a cable ISP, there is no IPv6 connectivity provided.
Second WAN (em1) is configured with PPPoE, IPv4 DHCP and IPv6 DHCPv6 (PPPoE dual-stack). I also get an IPv6 DHCP-PD from this, works fine on the LAN etc. This is a VDSL2 ISP, and these gateways are set as the defaults.
I have a couple of gateway groups configured, but no rules in place that use them. I may try removing them to see if it makes a difference.
If I disable/re-enable the PPPoE connection or interface or IPv4 gateway, I completely lose the default IPv4 route unless I completely disable the PPPoE interface or IPv4 gateway.
It doesn't seem to matter what else I do, I just cannot seem to get the PPPoE default IPv4 route back, short of a reboot. The only thing that works is to disable the PPPoE WAN or PPPoE IPv4 gateway completely, which re-instates the Cable WAN as the default IPv4 route. If I don't do that, there is NO IPv4 default route.
I'm happy to provide logs, config details etc, just kindly let me know what would be required, and what tests would be useful. Thank you!
Pages: [1]