WAN DHCP issue and one package

[none]

GUI, on the status->interfaces page.

[franco]

Ok, thanks. Are there any dmesg lines that seem to indicate why the lease has gone stale? Do you know the lease time the link has?

[none]

Log when the link was not ok. I then click renew, and the log is bellow.

vr0 is my lan, vr1 is the default ISP, vr2 is the second isp.

Code: [Select]

Sep 14 23:44:40 OPNsense dhclient[34470]: bound to 187.61.x.x -- renewal in 5400 seconds.
Sep 14 23:44:28 OPNsense dhclient: Creating resolv.conf
Sep 14 23:44:28 OPNsense dhclient: Adding new routes to interface: vr2
Sep 14 23:44:28 OPNsense dhclient: New Routers (vr2): 187.61.x.y
Sep 14 23:44:28 OPNsense dhclient: New Broadcast Address (vr2): 187.61.x.255
Sep 14 23:44:28 OPNsense dhclient: New Subnet Mask (vr2): 255.255.248.0
Sep 14 23:44:28 OPNsense dhclient: New IP Address (vr2): 187.61.x.x
Sep 14 23:44:26 OPNsense dhclient: ifconfig vr2 inet 187.61.x.x netmask 255.255.248.0 broadcast 187.61.x.255
Sep 14 23:44:26 OPNsense dhclient: Starting add_new_address()
Sep 14 23:44:26 OPNsense dhclient: BOUND
Sep 14 23:44:26 OPNsense dhclient[34470]: DHCPACK from 10.18.0.1
Sep 14 23:44:26 OPNsense dhclient[34470]: DHCPREQUEST on vr2 to 255.255.255.255 port 67
Sep 14 23:44:26 OPNsense dhclient: ARPCHECK
Sep 14 23:44:24 OPNsense dhclient: ARPSEND
Sep 14 23:44:24 OPNsense dhclient[34470]: DHCPOFFER from 10.18.0.1
Sep 14 23:44:24 OPNsense dhclient[34470]: DHCPDISCOVER on vr2 to 255.255.255.255 port 67 interval 2
Sep 14 23:44:24 OPNsense dhclient: Removing states through old gateway '187.61.x.x' (new gateway '')
Sep 14 23:44:24 OPNsense dhclient: Comparing Routers: Old: 187.61.x.x New:
Sep 14 23:44:24 OPNsense dhclient: Starting delete_old_states()
Sep 14 23:44:24 OPNsense dhclient: PREINIT
Sep 14 23:44:24 OPNsense dhclient: Deleting old routes
Sep 14 23:44:24 OPNsense dhclient: Removing states from old IP '187.61.x.z' (new IP '')
Sep 14 23:44:24 OPNsense dhclient: Comparing IPs: Old: 187.61.x.x New:
Sep 14 23:44:24 OPNsense dhclient: Starting delete_old_states()
Sep 14 23:44:24 OPNsense dhclient: EXPIRE
Sep 14 23:37:20 OPNsense dhclient[13991]: bound to 187.123.x.x -- renewal in 2195 seconds.
Sep 14 23:37:20 OPNsense dhclient: Creating resolv.conf
Sep 14 23:37:20 OPNsense dhclient: RENEW
Sep 14 23:37:20 OPNsense dhclient[13991]: DHCPACK from 187.123.x.x
Sep 14 23:37:20 OPNsense dhclient[13991]: DHCPREQUEST on vr1 to 187.123.x.x port 67
Sep 14 23:14:04 OPNsense dhclient[34470]: DHCPREQUEST on vr2 to 192.168.228.175 port 67
Sep 14 22:58:13 OPNsense dhclient[34470]: DHCPREQUEST on vr2 to 192.168.228.175 port 67
Sep 14 22:49:47 OPNsense dhclient[34470]: DHCPREQUEST on vr2 to 192.168.228.175 port 67
Sep 14 22:44:57 OPNsense dhclient[34470]: DHCPREQUEST on vr2 to 192.168.228.175 port 67
Sep 14 22:42:37 OPNsense dhclient[34470]: DHCPREQUEST on vr2 to 192.168.228.175 port 67
Sep 14 22:40:57 OPNsense dhclient[34470]: DHCPREQUEST on vr2 to 192.168.228.175 port 67
Sep 14 22:40:13 OPNsense dhclient[34470]: DHCPREQUEST on vr2 to 192.168.228.175 port 67
Sep 14 22:39:52 OPNsense dhclient[34470]: DHCPREQUEST on vr2 to 192.168.228.175 port 67
Sep 14 22:38:09 OPNsense dhclient[34470]: DHCPREQUEST on vr2 to 192.168.228.175 port 67

Code: [Select]

Sep 14 23:56:40 OPNsense dhclient[29327]: bound to 187.123.x.x -- renewal in 8525 seconds.
Sep 14 23:56:30 OPNsense dhclient: Creating resolv.conf
Sep 14 23:56:30 OPNsense dhclient: /sbin/route add default 187.123.x.x
Sep 14 23:56:30 OPNsense dhclient: Adding new routes to interface: vr1
Sep 14 23:56:30 OPNsense dhclient: New Routers (vr1): 187.123.x.x
Sep 14 23:56:30 OPNsense dhclient: New Broadcast Address (vr1): 187.123.x.x
Sep 14 23:56:30 OPNsense dhclient: New Subnet Mask (vr1): 255.255.248.0
Sep 14 23:56:30 OPNsense dhclient: New IP Address (vr1): 187.123.x.x
Sep 14 23:56:26 OPNsense dhclient: ifconfig vr1 inet 187.123.x.x netmask 255.255.248.0 broadcast 187.123.x.255
Sep 14 23:56:26 OPNsense dhclient: Starting add_new_address()
Sep 14 23:56:26 OPNsense dhclient: BOUND
Sep 14 23:56:26 OPNsense dhclient[29327]: DHCPACK from 187.123.x.x
Sep 14 23:56:26 OPNsense dhclient[29327]: DHCPREQUEST on vr1 to 255.255.255.255 port 67
Sep 14 23:56:26 OPNsense dhclient: ARPCHECK
Sep 14 23:56:24 OPNsense dhclient: ARPSEND
Sep 14 23:56:24 OPNsense dhclient[29327]: DHCPOFFER from 187.123.x.x
Sep 14 23:56:24 OPNsense dhclient[29327]: DHCPDISCOVER on vr1 to 255.255.255.255 port 67 interval 1
Sep 14 23:56:24 OPNsense dhclient: Starting delete_old_states()
Sep 14 23:56:24 OPNsense dhclient: PREINIT
Sep 14 23:56:24 OPNsense dhclient: Deleting old routes
Sep 14 23:56:24 OPNsense dhclient: Removing states from old IP '187.123.x.x' (new IP '')
Sep 14 23:56:24 OPNsense dhclient: Comparing IPs: Old: 187.123.x.x New:
Sep 14 23:56:24 OPNsense dhclient: Starting delete_old_states()
Sep 14 23:56:24 OPNsense dhclient: EXPIRE
Sep 14 23:56:24 OPNsense dhclient: Removing states from old IP '187.123.x.x' (new IP '')
Sep 14 23:56:24 OPNsense dhclient: Comparing IPs: Old: 187.123.x.x New:
Sep 14 23:56:24 OPNsense dhclient: Starting delete_old_states()
Sep 14 23:56:24 OPNsense dhclient: PREINIT
Sep 14 23:56:16 OPNsense dhclient[55496]: exiting.
Sep 14 23:56:16 OPNsense dhclient[55496]: connection closed


[none]

franco,

I kinda got some info about my dns issue on double wan.

It seems the packages goes out without any NAT:

Code: [Select]

14:00:53.157631 IP 187.61.x.x.12297 > 10.1.1.81.53: 2399+ A? teredo.ipv6.microsoft.com. (43)
14:00:54.170517 IP 187.61.x.x.12297 > 10.1.1.81.53: 2399+ A? teredo.ipv6.microsoft.com. (43)
14:00:55.184505 IP 187.61.x.x.12297 > 10.1.1.81.53: 2399+ A? teredo.ipv6.microsoft.com. (43)
14:00:57.197080 IP 187.61.x.x.12297 > 10.1.1.81.53: 2399+ A? teredo.ipv6.microsoft.com. (43)
14:01:01.206079 IP 187.61.x.x.12297 > 10.1.1.81.53: 2399+ A? teredo.ipv6.microsoft.com. (43)
I have auto NAT on nat page, and my gui shows there are NAT rules for WAN2. I must use DNS outside, (like 8.8.8. to browse.

Is this seens anywhere ?

thanks,

[franco]

Apologies for the delay. I'm not sure what's going on, but I think it's not a larger issue, which makes it harder to pin down the offending line of code. Can we do remote SSH access to the boxes in order to see if anything suspicious can be found?