Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Before I throw this router in the trash, maybe someone can help. My need is simple: set the router to a static IP. On the setup screen, on the drop-down menu for Internet Connection Type, the current setting is "Automatic Configuration - DHCP". When I select "Static IP" I get logged out and the login screen appears with the message, "Session Failure / Please login again". I've tried this numerous times.
Is this a public-facing router? If so, you might want to check the ISP's terms of service; they might preclude a static IP.
Yes, we have 5 static IPs and 3 have been in use for years.
I'm still struggling with this "simple" router. I believe I've set the static IP, and before doing that I set the router's LAN facing IP to 192.168.0.1, rebooted, then successfully connected to the router on that IP. I then set the static IP and netmask, but when I try to save settings I get the message "192.168.0.1 Invalid value". See image. Why? As stated, prior to attempting to set the static IP I did set the LAN IP to 192.168.0.1, rebooted the router and connected to the router on that IP. What's invalid about it?
I don't know. Basically all the instructions indicate is to select static IP and complete the fields required by your ISP and any optional fields if necessary. I assume that you probably need to do this disconnected from the MODEM. Without seeing what is behind the error message we can not tell if there is an error.
There is nothing behind the error message. I positioned the error box before taking the pic. Behind the error message is "Host Name"(blank), "Domain Name" (blank), and "MTU" (auto). I don't know, I've worked on SonicWalls that weren't this irritating to set up. I'll see if there is a firmware update.
Yes, we have 5 static IPs and 3 have been in use for years.
I'm still struggling with this "simple" router. I believe I've set the static IP, and before doing that I set the router's LAN facing IP to 192.168.0.1, rebooted, then successfully connected to the router on that IP. I then set the static IP and netmask, but when I try to save settings I get the message "192.168.0.1 Invalid value". See image. Why? As stated, prior to attempting to set the static IP I did set the LAN IP to 192.168.0.1, rebooted the router and connected to the router on that IP. What's invalid about it?
I would suggest that the "192.168.0.1" in the error box is a red-herring, it's showing the IP address of the router as the web source of the error message rather than the cause of the error message.
I would also suggest that the "Invalid Value" is the fact you've not specified a default outbound gateway or default DNS servers for your WAN side.
I would suggest that the "192.168.0.1" in the error box is a red-herring, it's showing the IP address of the router as the web source of the error message rather than the cause of the error message.
I would also suggest that the "Invalid Value" is the fact you've not specified a default outbound gateway or default DNS servers for your WAN side.
I think you're right about the "red herring" idea. Still I had trouble. I went to a different setup page changed something innocuous and was able to save from that page. I went back in and set gateway and DNSes in the Static IP section and those took, finally.
After restarting the modem, changing /etc/resolv.conf to have the same nameservers and restarting eth0 on the host, it kept changing my /etc/resolv.conf to have "nameserver 192.168.1.1", which is neither the router IP nor the nameservers I set it to. This kept happening after changing resolv.conf and restarting eth0, even after I set eth0 to USE_DHCP="no" and DHCP_KEEPRESOLV[0]="yes". Finally, I rebooted the host and the nameservers were now preserved correctly in resolv.conf. I'm guessing that before the reboot dhcpd or the like was running and kept clobbering things when I restarted eth0. On reboot that didn't run dhcpd, so perhaps that was the culprit. Not sure because I didn't verify that dhcpd was running before I rebooted. In any case, it's appears to be working now. I'm embarrassed that it was such a struggle with this normally simple device!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.