Networks

Ask something
Question Locked

Configuring WAP behind router

0 helpful
2 replies

by pilotjack59

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I needed to move my wireless router more to the center of the house so I purchased a new router and am running a cat 5 cable to the old wireless router's new location.

CABLE<->Router1<->WAP

Now, the WAP is actually a router which I'm just wanting to use as a WAP. I moved the DHCP function to Router1 and connected Router1 to WAP thru a "normal" (not internet) port on the WAP.

It works and I can access the internet wirelessly...

The problem I have is that I cant figure out the IP address of the WAP so I can access the security features of the WAP (add new devices, change WEP password, ...).

How can I "talk" to the WAP? I was sure I changed it's IP to 192.168.1.2 (from 192.168.1.1) but I cant "see" it from my browser (http://192.168.1.2)

Ideas?

2 replies

by tg2

You'll probably have to start over with a reset.

you can try wireless sniffing and see if you can push out a ping (ping -b 255.255.255.255) and look for an arp with your AP's MAC or very close to it, and then go after the IP that is associated with that arp..

ping -b works with many *nixes ... there isn't an equivalent with windows ping by itself (ie other tools run on windows to do the same thing, but not the included/built-in ping)

example: (using *nix)

user:~$ ping -b 255.255.255.255
WARNING: pinging broadcast address
PING 255.255.255.255 (255.255.255.255) 56(84) bytes of data.
64 bytes from 192.168.1.6: icmp_seq=1 ttl=255 time=0.439 ms
64 bytes from 192.168.1.5: icmp_seq=1 ttl=64 time=0.464 ms (DUP!)
64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=0.507 ms (DUP!)
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.958 ms (DUP!)
64 bytes from 192.168.1.8: icmp_seq=1 ttl=255 time=1.61 ms (DUP!)
64 bytes from 192.168.1.6: icmp_seq=2 ttl=255 time=0.187 ms
64 bytes from 192.168.1.5: icmp_seq=2 ttl=64 time=0.215 ms (DUP!)
64 bytes from 192.168.1.8: icmp_seq=2 ttl=255 time=0.224 ms (DUP!)
64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=0.285 ms (DUP!)
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.694 ms (DUP!)

--- 255.255.255.255 ping statistics ---
2 packets transmitted, 2 received, +8 duplicates, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 0.187/0.559/1.619/0.421 ms

? (192.168.1.2) at 00:1a:5e:12:AC:av [ether] on eth0
? (192.168.1.5) at 00:C0:5e:A6:99:93 [ether] on eth0
? (192.168.1.6) at 00:09:a0:07:6D:F1 [ether] on eth0
? (192.168.1.21) at 00:a9:a0:12:BA:EA [ether] on eth0
? (192.168.1.1) at 00:a1:10:78:EA:C9 [ether] on eth0
? (192.168.1.8) at 00:a0:70:Ba:A1:C9 [ether] on eth0

As an afterthought ... if you can ping and get a response from your .2 ... make sure you're accessing via wired connection ... ie. maybe you didn't enable wireless admin access and so its dropping the attempt except from a wired computer...

This discussion is closed to new replies.