

Try looking up “peddlers permit” aka hawking, canvassing, and soliciting. I have seen it be any or a combination of the terms when codified.


Try looking up “peddlers permit” aka hawking, canvassing, and soliciting. I have seen it be any or a combination of the terms when codified.
Depending on how your ISP is doing IPv6, the typical way would just route the entire prefix to your router, and the ISP would not know how many addresses are used, in the sense that there is no table (no neighbor discovery is needed). If your ISP is keeping data of flows from your prefix then it could start counting unique addresses, but there isn’t really good a reason to and it wouldn’t be accurate. Some devices pull and use more than one address, and quiet devices might not get picked up by flows which are typically sampled at a ratio.


Depending on the jurisdiction, soliciting often requires a permit and conditions of the permit include obeying no soliciting signs. Failure to obey typically means the permit can be revoked, or it could be a criminal offense. Could be worth looking into that for your area.


New York State’s civil service pension/retirement system is still like this. Including holidays.


Without prefix delegation turned on, you probably don’t get an IPv6 address on your lan devices. With it turned on, your router should assign a /64 to the LAN from a different subnet then what your WAN will have.
With PD on, what addresses do your clients get? For the laptop that doesn’t work, what does test-ipv6.com tell you?
With IPv6 you need to have your firewall rules setup correctly, as blocking certain ICMP messages will break IPv6.
Is the static IPv6 chosen for your server from the subnet your WAN is in? In this case, with PD off, if you cannot reach the internet you might need to enable a Neighbor Discovery Protocol proxy to allow the service provider’s router to learn where to find your server.
Personally, I would reenable PD then try to get the work laptop fixed. Maybe disable IPv6 on the work laptop. What I found at my job, is that when I am on VPN from a dual stack client, my company does not give a IPv6 address (or route) on the vpn, but replies with AAAA records causing the client to try to use the internet to reach things behind the corporate firewall.
I work for an ISP and did a migration that involved me seeing SSIDs we backed up. The FBI has hundreds of surveillance vans according to that.


I use Frigate and HomeAssistant, they are on different hosts and the only port allowed from Frigate to HomeAssistant is the non-auth api port. For normal users using Frigate, I use an Oauth2-proxy instance on the same host (same compose) as Frigate tied to a third host with keycloak. go2rtc is on the Frigate host, but it only talks to Frigate and the cameras themselves. You can also access go2rtc from outside if you want to access the streams directly but your HomeAssistant does not need too. I find that this is better than the cameras directly as the processing is not really meant for a whole bunch of streams at once.
I followed docs for the HomeAssistant to Frigate stuff with the GIF notifications and it is working fine. I also use the Frigate integration (using HACS) so maybe there is a lot done for me.


I have multiple linux computers, from servers to a surface tablet, i am able to use all different generations of all nvidia, both permanently installed, and eGPU. It is not without any issue, but it works and is usable.
For me issues stem from x11 vs wayland (work computer is ubuntu due to company policy), or egpu shenanigans which I feel is platform agnostic
VyOS for performance but if you don’t use a network device CLI regularly and it’s for home use OPNsense.
OPNsense comes with a lot of pretty sane defaults for a gateway/firewall, VyOS you really do everything from scratch, as it’s more geared towards enterprise or service provider.
VyOS does do well as a gateway/firewall and there is a lot you can install to extend features for stuff like what OPNsense has to the point that I have had 0 things I couldn’t do when I migrated a few years ago.