Hi,
On Sun, Feb 25, 2024 at 06:34:47PM -0500, Rich Brown via Bloat wrote:
> [...]
> Then they plug the new router's WAN port into their ISP modem's port,
> connect their laptop's Ethernet to the LAN port, point their browser to
> "openwrt.lan"
How about "openwrt.local" to conform to mDNS (RFC 676
Mmmh,
> On 26. Feb 2024, at 10:24, Erik Auerswald via Bloat
> wrote:
>
> Hi,
>
> On Sun, Feb 25, 2024 at 06:34:47PM -0500, Rich Brown via Bloat wrote:
>> [...]
>> Then they plug the new router's WAN port into their ISP modem's port,
>> connect their laptop's Ethernet to the LAN port, point the
Hi,
On Mon, Feb 26, 2024 at 10:47:16AM +0100, Sebastian Moeller wrote:
> > On 26. Feb 2024, at 10:24, Erik Auerswald via Bloat
> > wrote:
> > On Sun, Feb 25, 2024 at 06:34:47PM -0500, Rich Brown via Bloat wrote:
> >> [...]
> >> Then they plug the new router's WAN port into their ISP modem's port
Thanks for the observations re: "zero configuration OpenWrt install"
> On Feb 26, 2024, at 4:47 AM, Sebastian Moeller wrote:
>
>>
>> How about "openwrt.local" to conform to mDNS (RFC 6762) and IANA's
>> [special-use domain names][1]? Or perhaps "openwrt.internal" in the
>> future?
>
> Or per
On 2/26/2024 6:28 AM, Rich Brown via Bloat wrote:
- Avoid the WAN port's DHCP assigned subnet (what if the ISP uses
192.168.1.0/24?)
I recently got ATT fiber and its modem won't let me assign from
10.0.0.0/8! So I put a Raspberry Pi 4 in front of it.
