I’ve noticed since moving to VyOS Stream, my WAN IP changes frequently, and I notice it happens when I add/remove interfaces from firewall zones, or from my primary bond interface more often than not.
Prior, I’d keep the same IP for weeks/months now it changes almost every time I work on my firewall. I’m a home user, so I do not have a static IP.
When this happens, it occurs when the DHClient process is killed
Nov 16 17:02:00 systemd[1]: Stopping DHCP client on bond10...
Nov 16 17:02:00 dhclient[87911]: Killed old client process
Nov 16 17:02:00 dhclient[87911]: Killed old client process
I’ve included a log of my DHCP Client & snippet from `/var/log/messages` at the timeframe which shows it changing frequently, but I did not see anything in my dmesg or firewall logs (other than firewall logs!)- if there’s more information I can provide I’ll submit whatever I can.
Doesn’t seem like your MAC address is changing, which is what could cause a different IP from DHCP. If you’re changing interfaces in a bond, then the bond could change MAC if you remove the one it got it’s MAC from (bond’s use the first interface placed in the bond’s MAC)
Your /var/log/messages is from after the last DHCPRELEASE, so not very helpful to see what changes you were making right before that would cause it. From Nov 16 17:39:07 on would be useful
Thanks for the reply, so I did more testing and it seems maybe not the firewall but specifically when I update my bond interface.
My ISP connection + my other VLANs terminate to my bond10 interface. The native VLAN on bond10 is my ISP connection.
When I updated one of the sub-interfaces it disconnects everything and grabs a new IP From my ISP. i.e. Tonight I updated bond10.80 from 1500MTU to 9000MTU and it fetched a new IP on the untagged/native bond10 DHCP address.
It may not be related to firewall updates at all, I think my suspicion of that came from me working on both interfaces / firewalling at the same time. The last couple times, I was purely working on interface configs.
I hope this helps, I included a couple hours window of logs but specifically “Nov 20 01:10:13” is when I commit the MTU change to an sub-interface.
Edit: I will also include the /var/log/messages output from this timeframe, I see a couple errors about interfaces not existing (bond10.81, which is true- it does not exist. this was a test interface I deleted long ago. When I show all my config commands and grep for 81, it does not show there either)
Seems DHClient sends a DHCPRELEASE to my ISP and shuts down the DHClient each time I modify any settings on my bond10 interface (VIFs, MTUs, anything)
My solution is to buy another NIC and break out my ISP connection to it, with hopes this can be resolved eventually. I see it has this ghost bond10.81 interface, does this cause DHClient to freak out or is it expected behavior on VyOS 1.5?
Nov 20 01:10:15 SP-C2 netplugd[11562]: bond10.81: can't get flags: No such device
Nov 20 01:10:15 SP-C2 dhclient[282476]: DHCPACK of 47.205.121.2 from 47.205.121.1
Nov 20 01:10:15 SP-C2 dhclient[282476]: DHCPACK of 47.205.121.2 from 47.205.121.1
Nov 20 01:10:15 SP-C2 netplugd[11562]: bond10.81: can't get flags: No such device
Nov 20 01:10:15 SP-C2 dhclient[282476]: DHCPACK of 47.205.121.2 from 47.205.121.1
Nov 20 01:10:15 SP-C2 dhclient[282476]: DHCPACK of 47.205.121.2 from 47.205.121.1
In the dmesg-nov19 it shows this, and I noticed it happens to throw this error each time I have this issue. There’s no bond10.81 anywhere in my configs, it’s like a ghost config. I wonder if this is causing DHClient to outright restart and release my IP?