How to access a switch

B

balanga

I've recently configure a old LINKSYS WRT150N router into a switch to provide a few extra network ports. Is there any way I can access it without resetting it? I configured it as 192.168.3.1 and my Internet gateway is 192.168.1.1.
 
My experience is "not unless you wrote down the password you changed it to". If you have a laptop, I would simply plug the laptop into the WRT150N, make sure the WRT150N is unplugged from the network and do a factory reset. The laptop should be set to DHCP, then the WRT150N will have factory settings, configure it the way you want then plug it back into the network
 
My switch offers a serial console on USB, and I once needed it cause I forgot to "save" the config and some power outage "factory-reset" the device, which is a catastrophic thing in a network using both VLANs and lagg(4) (with LACP). I downloaded the manual on my mobile phone to be able to do something meaningful on the somewhat weird commandline presented on the serial console. ?

Yep, SirDice nailed it, although "RTFM" would have been more efficient ?
 
Try to configure an static IP address on your PC, like 192.168.3.100
Make a direct connection between PC and router, disconnect all another equipment from router,
and try to access your route/switch via its IP 192.168.3.1
 
SirDice said:
Here's a novel idea, download the manual for that device and read it.
Click to expand...
Actually, it has DD-WRT installed on it, but I'm useless when it comes to routing between different subnets on the same physical network. I'm presuming the router/switch has to be on a separate subnet...
 
After messing about with various of many options, not fully undestanding many, I am able to telnet into my router/switch if I set a static IP address of 192.168.2.2. My router is 192.168.2.1. I can also ping 192.168.1.1 (my Internet gateway) as well as 8.8.8.8 from my router and from my FreeBSD laptop.

Unfortunately I'm unable to get web access to the router. I get 'This site can't be reached' - refused to connect.
The same happens when trying to access any other web server.

What could be the problem?
 
After spending quite a bit of time and doing numerous reboots I can't tell if I've bricked my router.
How do I tell if it has an IP address assigned. dhclient em0 shows no result.
 
dhclient will not show the IP-address of your router. It will return an IP-address for your "client".
For you client you can assign a fixed IP-address in the same subnet of your router ...

You should "know" the configuration of your router.
If you forgot the configuration of your router you can do a factory reset according to the manual. Sometimes its plugging in a needle and push a switch.
 
Alain De Vos said:
dhclient will not show the IP-address of your router. It will return an IP-address for your "client".
For you client you can assign a fixed IP-address in the same subnet of your router ...

You should "know" the configuration of your router.
If you forgot the configuration of your router you can do a factory reset according to the manual. Sometimes its plugging in a needle and push a switch.
Click to expand...
I think I tried resetting it a few dozen times but don't get any response.

I thought I would try and found out if it managed to assign an IP address to itself which I could try and ping, but the only way I could think of fingding out was by using nmap but that didn't show anything.

Maybe wireshark could find something...
 
It's not a switch. It's a wireless access point that happens to have an unmanaged 4 port ethernet switch built-in.
 
You must log in or register to reply here.
Back
Top