>> I'm not sure how that could happen at boot time, it would need to
>> happen whenever a DHCPv4 lease changes. This implies that the router
>> might need to renumber if the ISP changes its allocation, and there are
>> no renumbering procedures for IPv4 (I'm not sure if anyone implements
>> RFC
This was delicious:
"If latency doesn’t matter, can I create a service that cross-ships
1TB HDDs overnight and call it broadband?" -
https://news.ycombinator.com/item?id=39533800#39534166
Could someone weigh in over there with the current starlink measuremetns.
On Tue, Feb 27, 2024 at 11:08 PM
I'm not advocating that we change the default OpenWrt address from 192.168.1.1
That's welded too deeply into our synapses (and documentation). But this
proposal will benefit newcomers for the reasons described below.
> On Feb 28, 2024, at 7:17 AM, David Lang wrote:
>
> remember, you don't
On Wed, 28 Feb 2024, Juliusz Chroboczek via Bloat wrote:
But my point is that the OpenWrt router has no way to predict what
address/subnet will be assigned to its WAN port.
In principle, the ISP should assign either a global address, or an address in
the range 100.64.0.0/10 (RFC 6598). This
> But my point is that the OpenWrt router has no way to predict what
> address/subnet will be assigned to its WAN port.
In principle, the ISP should assign either a global address, or an address in
the range 100.64.0.0/10 (RFC 6598). This range was deliberately chosen to
not collide with RFC
