![]() Then restart each device so it can get a new IP ![]() ![]() Go change the DHCP range in the modem/router and restart it. You’ve set all the devices you want as STATIC to their static addresses In the modem / router, you’ll find a setting to control the DHCP pool range. – 192.168.1.2 → 192.168.1.64 or 192.168.1.127 – Devices you always have on and want to know their IP addresses (this is the ‘static’ IP block) – 192.168.1.1 – The modem/router (probably already is ?) Plan out how your LAN devices have their addresses mapped. Set the server’s IP address as static (192.168.1.200 sounds like a DHCP address).Disable the WiFi on the server computer.The modem/router does hand out DHCP addresses to WiFi devices.I have a dedicated WiFi AP (Access Point) to create the SSID connected to the switch.1/2 the network bandwith… and then are all the other problems) It is getting really annoying for me already… At some point I was thinking that it might be the Network Manager (in newer OS, dhcpcd was replaced with Network Manager). The issue remains the same for me, regardless if it is Debian 11 or 12. ![]() I was trying different workarounds which I found on the internet, like adding ping every 5 mins in crontab to keep alive the connection, then reinstalling different OS. I just want to keep the scenario as described above - to be able to connect wirelessy to PMS, from multiple clients. I think the best would be to have eth0 as preferred adapter but I leave it up to you. ![]() Please elaborate on how to configure preffered adapter and backup adapter with the metrics. 192.168.1.200 is the wlan0 adapter on my PMS server.ġ92.168.1.201 is the eth0 adapter on my PMS server (wired connection to the router).Ĭlients (192.168.1.x) are accessing PMS via WiFi, through the router (I believe). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |