Some devices randomly losing their IPv4 address
Kenneth Porter
shiva at sewingwitch.com
Wed Apr 6 03:35:37 UTC 2022
--On Tuesday, April 05, 2022 8:03 PM -0700 Julien Pierre
<goldberg.variations at gmail.com> wrote:
> Thanks. I hadn't heard of the Kea DHCP server. I just checked the
> description, and it looks like something I want to try.
I used the Kea migration assistant utility, keama, to convert my ISC config
file to a JSON Kea config file. It seemed to do a good job. I thought at
first I'd want to convert my lease file, and started to invest some coding
towards that, but realized I didn't really care if the dynamic devices got
different addresses.
I did run into the problem that I didn't want DDNS for my reserved devices,
as I gave them DNS names statically in my BIND9 zone files. More details
and how I worked around it here:
<https://gitlab.isc.org/isc-projects/kea/-/issues/2354>
> I was on the Gigabit tier not because I needed the highest download
> speed, but because that's the only way to get their maximum upload speed,
> which is a paltry 45 Mbps.
That makes perfect sense. Some of us care about the upload bandwidth.
> I have been waiting 12 years
> for AT&T to lay it. I don't think it's ever happening on my side of the
> hill.
I know what you mean. My office was stuck in ADSL hell for a very long time
before another building tenant had fiber run in, and we were able to
piggyback on the main feed for that.
It sounds like you don't really need a router capable of the full 1.2 Gbps,
as long as it can keep up with the 45 Mbps upstream. I'm hearing on the
bufferbloat mailing list that a lot of consumer routers can still keep up
with a half Gbps in each direction.
> Thanks, I hadn't thought of that. I don't have access to the logs for many
> of the devices on which this happened, which are off-the-shelf Wifi
> devices. For the single-board computers, I do have access, I'm going to
> look into it. I didn't write down the time for previous events, though.
>From experience, the first thing I put in trouble tickets is the timestamp,
so the other guy can correlate it with his logs. The first thing I do when
I see a problem is to list /var/log in date order to see which files got
touched recently.
More information about the dhcp-users
mailing list