Shouldn't wired and wireless clients communicate with each other when on the same router?

Toggle sidebar Toggle sidebar
N

njk42

Reputable
Jul 17, 2014
1
0
4,510
I am trying to setup a simple network using a Belkin N750 router (supports 4 ethernet LAN ports and a WLAN). There is no WAN / internet connection involved in my setup. Router firmware is updated to the most recent version from Belkin's website.

My goal is for a client connected to the WLAN (Client A) to be able to communicate with a client connected to the wired LAN (Client B). Success with "communicate" in this instance would be a simple response from the wired client "B" when PINGed by the wireless one "A".

I have configured the router with an IP address of 192.168.10.1 and rebooted it.

I have connected Client B to a router LAN port with a Cat5 cable. It is configured with static IP address 192.168.10.2.

I have joined the WLAN successfully with Client A’s WiFi interface, using a static IP address configured as 192.168.10.3.

I get a successful response when I ping the router (192.168.10.1) from Client A (192.168.10.3), but I get NO response when I ping Client B (192.168.10.2) from Client A.

So then I connect Client A’s ethernet interface directly to another LAN port on the router and configure wired NIC to have static IP address 192.168.10.4. With this setup (everything wired), I can get successful ping responses from Client B – so I know Client B is up and running and connected to the router.

My expectation was that clients on the wireless side of the network should communicate with clients on the wired side without any special configuration. Is this expectation correct and I have a bad router? or is my expectation wrong and I need to do something special to get this working? or is it simply not possible?

By the way, all router and OS firewall settings are disabled. All IP configurations are static (DHCP is turned off on the router). And I don’t see any settings on this router’s configuration page which imply that the wireless AP is shielded from the wired side.

Any help recommending other configurations to try or any helpful networking troubleshooting tools would be much appreciated.

Thanks!
 
Solution
B
In general you should be able to do what you want. There is a option on many routers called wireless isolation. This is generally used to prevent wireless devices from talking to each other because of some forms of attack. It is not really suppose to restrict the traffic between the wireless and the wired because many time you have wired servers you do want the wireless to have access to just not to each other.

It is somewhat inconsistent as to how this is implemented and there are a number of consumer routers that prevent traffic between wireless and anything other than the internet...sorta like a guest network.

I would look for a feature called wireless isolation and turn it off.
Sort by date Sort by votes
B

bill001g

Titan
Aug 9, 2012
28,319
2,754
125,640
In general you should be able to do what you want. There is a option on many routers called wireless isolation. This is generally used to prevent wireless devices from talking to each other because of some forms of attack. It is not really suppose to restrict the traffic between the wireless and the wired because many time you have wired servers you do want the wireless to have access to just not to each other.

It is somewhat inconsistent as to how this is implemented and there are a number of consumer routers that prevent traffic between wireless and anything other than the internet...sorta like a guest network.

I would look for a feature called wireless isolation and turn it off.
 
Upvote 1 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom