The power outage yesterday kind of messed up my home network… mostly the Telus router.
-
The power outage yesterday kind of messed up my home network… mostly the Telus router.
It refused to give out addresses even after multiple unplugs/ reboots. That of course sent most of my devices into purgatory until it magically decided to deliver IPs again this morning.
#footiMac is up but incoming connections don’t seem to be happening reliably so @chris@mstdn.chrisalemany.ca is unavailable until I figure out the problem. The outside IP hasn’t changed and port forwards are still there so… *shrug*.
ISPs…
-
The power outage yesterday kind of messed up my home network… mostly the Telus router.
It refused to give out addresses even after multiple unplugs/ reboots. That of course sent most of my devices into purgatory until it magically decided to deliver IPs again this morning.
#footiMac is up but incoming connections don’t seem to be happening reliably so @chris@mstdn.chrisalemany.ca is unavailable until I figure out the problem. The outside IP hasn’t changed and port forwards are still there so… *shrug*.
ISPs…
able to look back again and it turns out the outside IP did actually get changed when the Telus router rebooted at some point. So at least that explains the outage. Things should return to normal now once DNS catches up.
-
able to look back again and it turns out the outside IP did actually get changed when the Telus router rebooted at some point. So at least that explains the outage. Things should return to normal now once DNS catches up.
I actually wonder if the reason the Telus router wasn't giving out DHCP addresses when it first returned from the power outage is because of some sort of mismatch on its end with the old and new IP addresses. According to my DynDNS provider, the IP updated 6 hours after the power came back on... after I had gone to bed... presumably at that point the router started handing out local addresses again.
-
I actually wonder if the reason the Telus router wasn't giving out DHCP addresses when it first returned from the power outage is because of some sort of mismatch on its end with the old and new IP addresses. According to my DynDNS provider, the IP updated 6 hours after the power came back on... after I had gone to bed... presumably at that point the router started handing out local addresses again.
@chris That doesn’t make sense.
The internal DHCP server should be giving out IP addresses to devices if it believes that there are available (typically true in a home scenario).
That’s assuming you get a private (10., 172.16-31 or 192.168) address.
-
@chris That doesn’t make sense.
The internal DHCP server should be giving out IP addresses to devices if it believes that there are available (typically true in a home scenario).
That’s assuming you get a private (10., 172.16-31 or 192.168) address.
@EdwinG ya, exactly. It doesn't make sense. I dunno. It's weird that it got a new outside IP address 6 hours after the initial power outage (and at least an hour after the last time I power-cycled it).. *and then* it started giving out private IPs after that.
black box….
-
@EdwinG ya, exactly. It doesn't make sense. I dunno. It's weird that it got a new outside IP address 6 hours after the initial power outage (and at least an hour after the last time I power-cycled it).. *and then* it started giving out private IPs after that.
black box….
@chris I have two hypothesis.
1. It didn’t receive an outside IP initially and self-configured with the last one it knew.
2. The DHCP server was waiting for the WAN side to self-configure; IPv6 is famous for that
️ -
R AodeRelay shared this topic
