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.
Hey there. This might not be considered a Linux question as such, but I'm having a few networking problems that I really can't understand.
The problem now is that I'm living in Japan, so when making router configuration changes I couldn't really understand what I was doing. It mysteriously broke one day, and in trying to fix it I managed to lock myself out of it completely!
I did a hard reset but I still can't login. The router here is a bit odd in that it plugs in to our Yahoo BB box (which is the default gateway) rather than connect to the line directly. I guess its as much a wireless hub if anything else.
Anyway, the IP addresses DHCP is assigning are in the 192.168.3 network, and *i think* this router's IP is set at 192.168.1.1. I can ping 192.168.1.1 and get an active response, so I'm assuming that this is the router itself.
However, I can't connect to it through a web browser in order to login, that merely times out. This could be a networking thing (since its on a different network) or potentially a configuration error (perhaps I selected an option to disallow router logins from anywhere?)
It seems strange that I can ping it but not receive the webpage in order to login and alter the settings. The router is a Corega router (Not sure on the exact model, but I'll go through the paperwork if its needed).
Any ideas for finding a solution to this problem? Or at least helping to further diagnose it?
Since it is assigning internal ip addresses by DHCP the first thing I'd check is what it is telling your computer the default gateway's ip addy is. In almost all routers I have seen this is the same as the internal management address. so once you look that up you can try opening that address with a browser.
Since it is assigning internal ip addresses by DHCP the first thing I'd check is what it is telling your computer the default gateway's ip addy is. In almost all routers I have seen this is the same as the internal management address. so once you look that up you can try opening that address with a browser.
Hope this helps
Freemor
Yeah I've tried this and it has never worked. I think this wireless router's IP is on a network I apparently can't connect to, yet apparently still can ping. I really don't understand, the whole scenario seems to go against anything I've ever been taught regarding networking :O
Hmmmm... The only other thing I can think of are that some routers have their management interface on a port other then 80 (www standard) so you might want to try some of the more standard alternates like 8080 etc. Also it might be an idea to google the model of router you have and see if anyone else has had a similar problem. Googling might also get you the right alternate port if it uses one, or information on how to do a hard reset of the router to set it back to factory default (I've had to reset a couple of SMC routers for people that had forgotten their passwords.)
Hmmmm... The only other thing I can think of are that some routers have their management interface on a port other then 80 (www standard) so you might want to try some of the more standard alternates like 8080 etc. Also it might be an idea to google the model of router you have and see if anyone else has had a similar problem. Googling might also get you the right alternate port if it uses one, or information on how to do a hard reset of the router to set it back to factory default (I've had to reset a couple of SMC routers for people that had forgotten their passwords.)
Hope this helps
Freemor
Possibly, the trouble with googling is that any problems are written in japanese, which I can't yet read. I don't believe this model is available outside of Japan.
As for it being a non standard port, The only problem with that is that I *could* login with port 80 before hand, but mysteriously am now completely unable to. I can't imagine I would have changed the default port accidentally though...
EDIT : Just done a nmap scan of 192.168.1.1 and it shows port 80 as open, but filtered. hmm..
Uh OH... is it possible you restricted internal managment to having to come from a certian ip address?
I don't know, I guess it could be a possibility. The last thing I remember changing was the 'mode' of something, but I can't imagine that mode was a "can login" mode
I don't know if I can just reset the thing back to factory settings. There is the pin hole bit on the back, but it doesn't seem to change anything after pressing it! Is there another method to return a router to factor settings?!
As a suggestion, has the router been configured to restrict access to certain "mac" addresses?
I use a Belkin router that can be configured to only allow access to specific mac addresses which it picks up from individual machines, I can swap network cards around into different machines and they can connect regardless of the ip address, but if I try to connect using a network card with an unrecognised mac address (either by wire or wirelessly) there's no connection.
there usually is a more complex sequence to do a hard/factory reset. on the SMC routers I worked on you had to short a couple of pins on the rs232 port of the router and then reset. some you need to hold down the reset while during power on, etc. is there anyway you could contact either the isp that supplied the router or the manufacturer and inquire about the correct sequence to do a hard reset.
Also in you nmap port scan was port 23 available.. some routers have telnet management as well so that might be an option to try
there usually is a more complex sequence to do a hard/factory reset. on the SMC routers I worked on you had to short a couple of pins on the rs232 port of the router and then reset. some you need to hold down the reset while during power on, etc. is there anyway you could contact either the isp that supplied the router or the manufacturer and inquire about the correct sequence to do a hard reset.
Also in you nmap port scan was port 23 available.. some routers have telnet management as well so that might be an option to try
No, port 23 was not open.
Interdictor, I'm fairly sure that I didn't disallow certain mac addresses, but again I'm open to the possibility that I did! It's hard trying to configure a router properly when it's all in Japanese.
Freemor, if there is a more difficult sequence for a factory reset then thats probably my only hope! I'll try and find a japanese friend today to translate the manuals for me, that might save me!
Hope that worked for YOU. Suggestion: Get permission to replace the router. If Yes, then replace with a model that technologically is compatible. English is the primary language, and the instructions are attainable. Purchase and install. Good luck to YOU. P.S. http://www.freedict.com/onldict/jap.html For some of the curious dialogs...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.