FrostyCat
Explorer
- Joined
- Jan 4, 2022
- Messages
- 79
My Bluefin NAS has 2 IP addresses allocated, one I use for the web UI and SSH mainly (192.168.0.8) , and one I use for Kubernetes (192.168.0.9).
A couple of days ago, I lost power for several hours and I had to shutdown the machine. On the first boot after the power was restored, the were swapped on the interface, .9 was primary and .8 was secondary and all the Kubernetes services (via Traefik) were bound to 192.168.0.8. The web interface didn't start properly because of the ports conflicts, 80 and 443 were in use already).
After a few minutes of trying to understand what happened, I gave up and rebooted the machine.
What happened next surprised me because the IPs were now on the interface back in the expected order, .8 as primary and .9 as secondary and both the UI and Kubernetes were running just fine.
I next shutdown the machine and did exactly the same thing again, and I was able to reproduce the same situation, IPs wapped on the first boot, then ok after a reboot.
Could this be a bug? I'm not sure how the interface is configured, I'm assuming it's the middleware? Happy to contribute debug logs or anything else.
Interface configured correctly, it's a bit confusing cause in the UI they are both treated as aliases, not as primary and secondary aliases.
IP assignment:
Kubernetes is setup to use the second one, 192.168.0.9.
A couple of days ago, I lost power for several hours and I had to shutdown the machine. On the first boot after the power was restored, the were swapped on the interface, .9 was primary and .8 was secondary and all the Kubernetes services (via Traefik) were bound to 192.168.0.8. The web interface didn't start properly because of the ports conflicts, 80 and 443 were in use already).
After a few minutes of trying to understand what happened, I gave up and rebooted the machine.
What happened next surprised me because the IPs were now on the interface back in the expected order, .8 as primary and .9 as secondary and both the UI and Kubernetes were running just fine.
I next shutdown the machine and did exactly the same thing again, and I was able to reproduce the same situation, IPs wapped on the first boot, then ok after a reboot.
Could this be a bug? I'm not sure how the interface is configured, I'm assuming it's the middleware? Happy to contribute debug logs or anything else.
Interface configured correctly, it's a bit confusing cause in the UI they are both treated as aliases, not as primary and secondary aliases.
Code:
root@nas ~ # ip a show dev enp4s0 2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 18:c0:4d:98:e4:f5 brd ff:ff:ff:ff:ff:ff inet 192.168.0.8/24 brd 192.168.0.255 scope global enp4s0 valid_lft forever preferred_lft forever inet 192.168.0.9/24 brd 192.168.0.255 scope global secondary enp4s0 valid_lft forever preferred_lft forever
IP assignment:
Code:
[nas]> network interface ip_in_use +-------+-----------------------------------------+---------+-----------------------------------------+ | type | address | netmask | broadcast | +-------+-----------------------------------------+---------+-----------------------------------------+ | INET | 192.168.0.8 | 24 | 192.168.0.255 | | INET | 192.168.0.9 | 24 | 192.168.0.255 | +-------+-----------------------------------------+---------+-----------------------------------------+
Kubernetes is setup to use the second one, 192.168.0.9.
Code:
[nas]> app kubernetes node_ip 192.168.0.9