Darryl Gregorash wrote:
On 2020-08-22 7:13 a.m., Per Jessen wrote:
Darryl Gregorash wrote:
Except 192.168.100.1 is my cable modem, and it certainly does not have a DHCP server in it. I ave never seen that IP appear in my logs before, except the last 2 reboots.
Something on your network provides a DHCP service, using a range of 192.168.100.[2-254] The actual range is a guess, but it's quite typical for an access modem to be 192.168.x.1, run a DHCP server and advertise itself as the default gateway. It does seem quite likely that your cable modem has a DHCP server.
As Carlos points out, 20sec is a very short lease - I don't know what the idea of that might be.
I just spoke with the ISP, and the modem does not have a DHCP server in it. It would make no sense for it to have a DHCP server unless it was a router, which it is not.
Okay - I wonder what kind of setup you have, but I am not really familiar with the "cable modem" expression. If your cable modem is _not_ a router, your home network is directly connected to the overall telco/cable network. Unless the next uplevel switch is using vlans, all of your neighbours can listen in on what you're doing.
As far as I am concerned, 192.168.100.11 is being assigned by the OS, because the DHCP request has failed (timed out), on account of a network interface that has not been properly initialized.
No, that would be the OS rolling a pair of dice. Why not 10.1.2.3 or 172.16.45.67 ? or 185.84.248.1 ? iow, where does that number come from?
Please recall that this problem has never occurred except during a reboot right after a kernel update. I have already rebooted once after my first post, and everything went fine. Do you wish to see the log from that boot?
It might be interesting to see, yes. -- Per Jessen, Zürich (22.6°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org