| AP Behind my Firewall I have this firewall / DHCP server that run my ethernet network in my home.. I added an AP for WiFi in the house and It seems to work great with 1 exception...
I device on the WLAN (IE laptop) cannot connect to my NAS on the LAN of the Firewall by name.. I can connect my IP address but not the device name.. If I plug directly into the LAN I can.. For example, the Buffalo NAS navigator cannot find the NAS when connected wirelessly but it can when wired to the LAN..
I have the Firewall / DHCP set to 10.25.32.x and the AP is set to 10.25.33.x..
It's as if the DHCP translation is not passing through.
Also, I have RIP enabled on both the LAN and WLAN in both directions.
Any suggestions would be much appreciated 
--
Stunod |
|
|
|
 mozerdLight Will Pierce The DarknessPremium,MVM
join:2004-04-23
Nepean, ON | said by stunod2002:I have the Firewall / DHCP set to 10.25.32.x and the AP is set to 10.25.33.x.. Since your AP is on a different subnet anything on the AP subnet will net be able to see stuff on the other subnet. If your router has the capability to span subnets then stuff on the AP and visa-versa would communicate with each other.
You have 2 subnets:
10.25.32.x
10.25.33.x..
IF you do not mind putting the AP on the same subnet then for the AP use the 10.25.32.xxx subnet and everyone will communicate as you expect.
for example:
Your Firewall --- 10.25.32.101
Your AP -------- 10.25.32.199
Many folks like to segregate their Wireless Networks from their wired networks -- in that case if one subnet needs to communicate with the other subnet one must configure rules and port forwards assuming the Router is capable of doing that kind of thing.
--
David Mozer
IT-Expert on Call
Information Technology for Home and Business |
|
| reply to stunod2002
said by stunod2002:I have the Firewall / DHCP set to 10.25.32.x and the AP is set to 10.25.33.x.. Presuming these are 255.255.255.0 (aka /24) networks. If so, agree with mozerd that
it could be a routing issue. Any particular reason why you have it configured like that?
Regards |
|
| reply to mozerd
Many folks like to segregate their Wireless Networks from their wired networks -- in that case if one subnet needs to communicate with the other subnet one must configure rules and port forwards assuming the Router is capable of doing that kind of thing.
That said, I wifi netowrk does not need to be on a diff. subnet other than the equipment seems to enforce that rule..
--
Stunod |
|
Reviews:
 ·Comcast Business..
 ·AT&T Midwest
| reply to stunod2002
Configure the LAN side of you wireless router (AP) with a static IP within same subnet as you LAN 10.25.32.101 for example.
Then set the WAN port to DHCP for it's address.
Turn off DHCP server on your AP. You want your main LAN to server all DHCP addresses.
Connect a LAN port on the AP to the Ethernet switch and you should be good to go. DO NOT connect the WAN port to anything. This basically bypasses the routing functions within the router and turns it into an access point. |
|
| uggg - Brain fart! Thank you cmslick!! I knew I was doing something stupid...
Appreciate the help...
--
Stunod |
|
cramer
join:2007-04-10
Raleigh, NC
kudos:5 Reviews:
·AT&T Southeast
| reply to stunod2002
That's not an "Access Point", that's a wireless *router*. If you want to use a router as an AP, disable it's LAN side DHCP server, and attach it to your lan via a LAN, not WAN, port. If you want to be able to access it, give it's LAN side an address within your LAN. (99% of wifi routers will not run a dhcp client on the inside -- it's a router, it's address is supposed to be fixed.)
I think all of this is in a FAQ entry somewhere around here. |
|
 DrTCPYours trulyPremium,ExMod 1999-04
join:1999-11-09
Round Rock, TX | reply to stunod2002
said by stunod2002:I actually tried that but I quickly learned it will not work. My firewall / DHCP server hands out 10.25.32.2-.100 IP addresses. My AP's uplink (A.K.A. WAN) get an IP of .3.. Therefore it will not allow you to set the LAN to the same subnet as the WAN..
That said, I wifi netowrk does not need to be on a diff. subnet other than the equipment seems to enforce that rule..
You are doing it wrong. You are trying to use a wireless router as a simple AP but you are still using its routing functionality. You need to basically eliminate the use of routing functionality and everything will be on the same network.
Instead of repeating what you need to do, here are the instructions from Wireless Networking forum FAQ:
»Wireless Networking Forum FAQ »Using a Wireless Router as an Access Point |
|
