On Thu, Oct 16, 2025 at 3:15 PM Roy J. Tellason, Sr. <[email protected]> wrote:
> This isn't strictly debian-related, so if there's a better place for this > feel free to point me at it and I'll try there... > > Back when my LAN was a workstation and a DSL modem, and a bit later on a > routher/firewall was added, and a server, then later on a second > workstation. Wifi was an old (now older and very flaky) AP. These days > wifi is also provided by the "modem" (Hugesnet, who is completely useless > for help on this) and it's dual band and seems overall faster. > > The problem is when I'm using that wifi I have no access to my local > server, I can only get to it by way of the old flaky AP that's internal to > the LAN. > > Particulars: The "modem" is 192.168.1.1, the WAN side of the router is > 192.168.1.2, the server on the other side of the router is 192.168.0.1, > and the workstations get DHCP addresses assigned when they connect, as do > any devices (a couple of phones and a tablet) that connect to the wifi. Is > there any simple way to get that external wifi to point to my internal > server when a 192.168.x.x address is used? > > > -- > Member of the toughest, meanest, deadliest, most unrelenting -- and > ablest -- form of life in this section of space, a critter that can > be killed but can't be tamed. --Robert A. Heinlein, "The Puppet Masters" > - > Information is more dangerous than cannon to a society ruled by lies. > --James > M Dakin > > I think your WiFi AP might be performing NAT like it was a router. Your "modem" is giving out an RFC1918 address which means almost certainly that it has its own DHCP server and routing. If you can find the configuration interface for the WiFi AP see if you can set it to bridge mode which will disable the NAT and DHCP and allow the "modem" to give out IPs and manage the network. - Luke Harding
