One suggestion though: rather than doing this all on a single LAN network and having to deal with adding exceptions for devices that still need access to the Internet during 'bedtime' periods, I suggest creating a separate VLAN for devices that need 'bedtime' enforcement and put those devices there, while leaving your 'always online' devices in your main VLAN where access to the Internet is always available. This way all you have to do is simply change your firewall rules for that VLAN to enforce bedtime, which removes the extra rules needed for exceptions.
> However, I ran into trouble with the RealTek ethernet hardware support in OpenBSD, which had been running fine with Linux for years.
I've run into problems with realtek gigE nics on Linux, FreeBSD, and Windows. I'm convinced their hardware/firmware has a timing issue where if the wrong things happen, the descriptor indexes get unsyncronized. This can lead to network stalls, but also wild writes. IIRC, reset behavior is weird too; vague because it's been a while since I looked, but I think if you get a network stall and do a reset, the card may receive and DMA a packet into RAM in the process ... something like that anyway.
I have systems where the FreeBSD base driver consistently stalls, but the realtek provided driver works mostly ok; but the realtek driver is full of undocumented flag setting, so who knows what it's doing... it also sets the NIC to emit pause frames when it runs out of RX buffers which I never want; things will be much better if packets are dropped when RX buffers are full.
I would love to have the equipment and time to figure out what's going on, but a) realtek probably should be the ones to do it, b) switching drivers usually works at no cost, and swapping to intel almost always works but you need slots and cards (ebay gets you multiport 1g for $10, 10g for $20-$30 though). I've heard realtek is good at 2.5g and intel isn't; but I haven't run enough realtek 2.5g to know.
Thank you for sharing! What are your thoughts on intentionally degrading service over the course of an hour instead of a hard cutoff? Like implementing an increasingly restrictive cap on download speeds/intentionally dropping a % of packets over the hour. Might be a little less jarring than a hard stop.
That little PC should be able to run a lot of additional stuff in addition to the packet filter. My setup is similar, but I use an old gaming PC instead, and run dozens of services including email, nginx and various game servers on it. It does not break a sweat.
I tried something like this. my kids just turned off wifi and I can't control the cell signals. Phone parent controls are not powerful enough for what I need
> The computer is a Qotom Q305p 3205u.
> Total price with power adaptor: $60
I'd love to have a handful of tiny computers that I could do fun stuff on, but there is absolutely nothing available in the UK for less than double that price.
> It runs a 1.5Ghz Celeron processor with completely passive cooling (the whole computer is a heatsink),
The whole case is the heatsink. The exterior case, and not the SSD or the mainboard or the RAM or any of the other parts; only the case.
“Computer” is the case + everything inside of it.
This irritates me just as much as when people say “my body is sweating”. Like, NO. It’s not your body that’s doing that, it’s your skin. Your internal organs aren’t sweating to cool you off, only your skin is. Your body as a whole might be overheating, it might be sending the signals to your brain to start the cooling process, but it is your skin that is actually doing the cooling. That’s your skin’s job. It’s the only organ who can do that job.
16 comments
[ 3.0 ms ] story [ 30.2 ms ] threadOne suggestion though: rather than doing this all on a single LAN network and having to deal with adding exceptions for devices that still need access to the Internet during 'bedtime' periods, I suggest creating a separate VLAN for devices that need 'bedtime' enforcement and put those devices there, while leaving your 'always online' devices in your main VLAN where access to the Internet is always available. This way all you have to do is simply change your firewall rules for that VLAN to enforce bedtime, which removes the extra rules needed for exceptions.
I've run into problems with realtek gigE nics on Linux, FreeBSD, and Windows. I'm convinced their hardware/firmware has a timing issue where if the wrong things happen, the descriptor indexes get unsyncronized. This can lead to network stalls, but also wild writes. IIRC, reset behavior is weird too; vague because it's been a while since I looked, but I think if you get a network stall and do a reset, the card may receive and DMA a packet into RAM in the process ... something like that anyway.
I have systems where the FreeBSD base driver consistently stalls, but the realtek provided driver works mostly ok; but the realtek driver is full of undocumented flag setting, so who knows what it's doing... it also sets the NIC to emit pause frames when it runs out of RX buffers which I never want; things will be much better if packets are dropped when RX buffers are full.
I would love to have the equipment and time to figure out what's going on, but a) realtek probably should be the ones to do it, b) switching drivers usually works at no cost, and swapping to intel almost always works but you need slots and cards (ebay gets you multiport 1g for $10, 10g for $20-$30 though). I've heard realtek is good at 2.5g and intel isn't; but I haven't run enough realtek 2.5g to know.
https://superuser.com/questions/545329/how-do-i-make-a-machi...
I'd love to have a handful of tiny computers that I could do fun stuff on, but there is absolutely nothing available in the UK for less than double that price.
The whole case is the heatsink. The exterior case, and not the SSD or the mainboard or the RAM or any of the other parts; only the case.
“Computer” is the case + everything inside of it.
This irritates me just as much as when people say “my body is sweating”. Like, NO. It’s not your body that’s doing that, it’s your skin. Your internal organs aren’t sweating to cool you off, only your skin is. Your body as a whole might be overheating, it might be sending the signals to your brain to start the cooling process, but it is your skin that is actually doing the cooling. That’s your skin’s job. It’s the only organ who can do that job.