WG302v2 - Wireless devices can't connect to Wired devices

[jonasestevam]

Hi, my english is really bad, so I'll go straight to the problem:

I have:

1- A PC running an Apache server;

2- A switch;

3- A WG302v2 Access Point with the lastest firmware;

4- A smartphone.

All connected like:

The PC is connected on the switch;

The switch is connected on the AP;

And the smartphone is connected on the AP wireless connection.

All configured like:

The AP is doing DHCP on the wireless network between 192.168.0.10 and 192.168.0.40;

The AP IP address is 192.168.0.1;

The PC IP address is static, configured as 192.168.0.10;

The main problem is: I can't connect to the PC server with the smartphone (Can't even ping each other).

There's this configuration on AP called "Wireless Client Security Separation" which is turned off already.

[jonasestevam · Accepted solution]

I got it working.

I noticed that when the AP is doing the DHCP on wireless network, I really can't access the wired network via the WiFi devices.

BUT, when the AP wireless network is on STATIC, I CAN access the wired. I just don't know why this happens.

Anyway, I still need to have DHCP on both networks, so I did this:

I turned off the DHCP option on the AP, and installed a DHCP server on PC.

And it worked like a charm.

Now I can access the Apache server on the wired and the wireless network.

[DaneA]

Hi @jonasestevam,

Welcome to the community! 🙂 

Based from the network setup you have provided, the PC server will not really be able to get a reply from the smartphone.  It is because the wireless network on the WG302v2 is not known by the LAN network where the PC server belongs.  

If ever your switch supports VLAN and DHCP server, I suggest you the following steps:

1. Create a VLAN.   Let say for example: VLAN 09.   

2. Set port members of VLAN 09.  For example: port 01-08 set as untagged ports with PVID of 09 and port 09 as tagged port with a PVID of 01. 

3. Create a DHCP pool for VLAN 09.  For example: 192.168.0.10 to 192.168.0.40. 

4. Set a static IP Address on the WG302v2 (example: like 192.168.0.10) for ease of management and connect it to port 09 of the switch because the WG302 is a VLAN-aware device and port 09 of the switch is set as tagged port. 

5. On the WG302v2, create a Wireless Network Profile.  For example, let us name it Private Network and set VLAN 09 on it.

6. Connect the PC server to any port member of VLAN 09 (from port 01-08).  It will obtain an IP address from the 192.168.0.11 to 192.168.0.40 IP address range because 192.168.0.10 is already set to the WG302v2.

7. Connect your smart phone to the wireless network named Private Network.  It will also obtain an IP address from the 192.168.0.11 to 192.168.0.40 IP address range. 

8. The PC server should now be able to get replies when you ping the smartphone.

Is your switch a NETGEAR device?  If yes, what is the model number of it?  

Do you have a router? 

Regards,

DaneA

NETGEAR Community Team

[jonasestevam]

Hi, DaneA, thanks for replying. Unfortunately, my switch is a simple one, so I can't manage VLAN's in it.

But anyways, I have a solution that I'll post next.

[jonasestevam · Accepted solution]

I got it working.

I noticed that when the AP is doing the DHCP on wireless network, I really can't access the wired network via the WiFi devices.

BUT, when the AP wireless network is on STATIC, I CAN access the wired. I just don't know why this happens.

Anyway, I still need to have DHCP on both networks, so I did this:

I turned off the DHCP option on the AP, and installed a DHCP server on PC.

And it worked like a charm.

Now I can access the Apache server on the wired and the wireless network.