Ok, so I run a homelab with a mini pc running Proxmox behind an old chinese router (iball-baton) which is connected to my upstream router (Jio AirFiber IDU) in bridging mode.
My upstream router or the IDU has this config:
Gateway: 192.168.31.1
DHCP Range: 192.168.31.10 - 192.168.31.254
Subnet: 255.255.0.0 (or /16 in CIDR)
My secondary router is in bridging mode so I can access my services no matter which ap I am connected to and NAT is a pain to work with, I absolutely despise NATing.
I have static IPs assigned to each category of my LXCs, like media gets 192.168.4., administration gets 192.168.2., homepage/dashboard gets 192.168.1.*, and so on.
Everything is perfect until... well power cuts, they are not very frequent but no guarantees either, sometimes multiple small power cuts in a day or sometimes in weeks. So, after a power cut, when the IDU completes the power up, I can't connect to it from some of my devices. But some were connected automatically like my laptop, so my first attempt is to try to open the panel, well no luck. Well, what could go wrong? Did a quick nmap scan to check for open ports, nothing. Check my gateway ip with
My theory is that it's the slow IDU boot time that can't catch up with my secondary router in bride mode, and so it can't pull the ip in time, fails and as a fallback jumps over to the next subnet? (I don't use DHCP in my Proxmox, I have static IPs assigned to each LXC, that I can remember in my head).
Only possible fix (don't know if it is consistent) I have found is to disconnect my secondary router and restart my upstream IDU, it fixes itself, and then I can turn on my secondary router.
Before, figuring this out, I used to just reset the router and reapply all the changes I need after it boots up.
Any ideas? I know I need a backup power source, but it seems these airfiber idus don't support the standard router power backup options (they pull a lot of power too).
My upstream router or the IDU has this config:
Gateway: 192.168.31.1
DHCP Range: 192.168.31.10 - 192.168.31.254
Subnet: 255.255.0.0 (or /16 in CIDR)
My secondary router is in bridging mode so I can access my services no matter which ap I am connected to and NAT is a pain to work with, I absolutely despise NATing.
I have static IPs assigned to each category of my LXCs, like media gets 192.168.4., administration gets 192.168.2., homepage/dashboard gets 192.168.1.*, and so on.
Everything is perfect until... well power cuts, they are not very frequent but no guarantees either, sometimes multiple small power cuts in a day or sometimes in weeks. So, after a power cut, when the IDU completes the power up, I can't connect to it from some of my devices. But some were connected automatically like my laptop, so my first attempt is to try to open the panel, well no luck. Well, what could go wrong? Did a quick nmap scan to check for open ports, nothing. Check my gateway ip with
ip a, to my surprise it jumped a whole freaking subnet, 192.169.0.201/28 was my new ip range, what is going on? Still can't access the panel, so I did a nmap scan for open ports again, still nothing of value.My theory is that it's the slow IDU boot time that can't catch up with my secondary router in bride mode, and so it can't pull the ip in time, fails and as a fallback jumps over to the next subnet? (I don't use DHCP in my Proxmox, I have static IPs assigned to each LXC, that I can remember in my head).
Only possible fix (don't know if it is consistent) I have found is to disconnect my secondary router and restart my upstream IDU, it fixes itself, and then I can turn on my secondary router.
Before, figuring this out, I used to just reset the router and reapply all the changes I need after it boots up.
Any ideas? I know I need a backup power source, but it seems these airfiber idus don't support the standard router power backup options (they pull a lot of power too).