It auto-inserts 192.168.0.12 because that's the IP address of your NAS, and you've logged into it to adjust something at some point in the last six months. You register it has done this as you're releasing the Enter key.

click Back.

Type the IP address again, this time carefully deleting the 2 it oh so helpfully inserted.

Wait 3 to 5 business weeks while the 16-bit ARM microcontroller they put in these things serves a web page like old people fuck. It loads to a completely useless stats page that has no information that anyone has ever needed to know.

Click LAN Setup.

Wait 3 to 5 business weeks while the 16-bit ARM microcontroller they put in these things serves a web page like old people fuck.

Parse the wall of acronyms before you, click the link that says DHCP.

Wait 3 to 5 business weeks while the 16-bit ARM microcontroller they put in these things serves a web page like old people fuck.

It continues in that fashion until you get what you need done or your network stops working and you have to get a pen and press the Reset button on the back of the device.

[–] Taleya@aussie.zone 1 points 1 day ago

It auto-inserts 192.168.0.12 because that's the IP address of your NAS, and you've logged into it to adjust something at some point in the last six months. You register it has done this as you're releasing the Enter key.

I avoid this by having my router interface on 1) a double digit IP. And 2) a non-standard port

[–] Ricaz@lemmy.dbzer0.com 4 points 1 day ago

IT professional doesn't have local DNS? LOL

[–] LordKitsuna@lemmy.world 4 points 1 day ago

Imagine not having an opnsense firewall deployed as an IT professional

[–] dejected_warp_core@lemmy.world 2 points 1 day ago

Wait 3 to 5 business weeks while the 16-bit ARM microcontroller they put in these things serves a web page like old people fuck.

This also goes for some NAS appliances and the in-dash console of newer cars. Underpowered ARM implementations are the scourge of this decade.