IdentiFi: wireless client can ping EWC, but can't ping gateway
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-06-2017 10:44 AM
Hello, everybody,
At last, I've configured my clients to get correct IPs from DHCP server using relay.
Everything looks fine, but I can't ping outside world from clients, (while could ping EWC).
From EWC I can ping outside networks and can ping wireless clients.
How could I allow wireless clients to reach their gateways?
Access mode for all Roles is "Containment VLAN", all WLAN Topologies are EWC.
Many thanks in advance,
Ilya
At last, I've configured my clients to get correct IPs from DHCP server using relay.
Everything looks fine, but I can't ping outside world from clients, (while could ping EWC).
From EWC I can ping outside networks and can ping wireless clients.
How could I allow wireless clients to reach their gateways?
Access mode for all Roles is "Containment VLAN", all WLAN Topologies are EWC.
Many thanks in advance,
Ilya
21 REPLIES 21
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-06-2017 03:14 PM
I'm using VM ESXi ver5.5
There is a problem while configuring AP and Virtual Controller, here’s model details:
Controller: Virtual Controller V2110
AP: WS-AP3935i-ROW
Scenario:
-admin port: 192.168.18.X/24
-physical port: 10.0.0.X/24, vlan 101
-test_topology: 10.10.10.X/24,
Gateway: 10.10.10.251
vlan 10 [Mode: Bridge traffic at EWC]
Problem:
-AP is detected on controller.
-Client connected to AP, but unable to access internet.
Action Taken:
-Verified on network, no issue.
-Trace route from client to internet was timeout at controller.
There is a problem while configuring AP and Virtual Controller, here’s model details:
Controller: Virtual Controller V2110
AP: WS-AP3935i-ROW
Scenario:
-admin port: 192.168.18.X/24
-physical port: 10.0.0.X/24, vlan 101
-test_topology: 10.10.10.X/24,
Gateway: 10.10.10.251
vlan 10 [Mode: Bridge traffic at EWC]
Problem:
-AP is detected on controller.
-Client connected to AP, but unable to access internet.
Action Taken:
-Verified on network, no issue.
-Trace route from client to internet was timeout at controller.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-06-2017 03:14 PM
I believe the VM environment was the issue in Ilia's case . Vince - what topology you are using - is that tunneling back to controller or bridging to AP? And second question (in case the firs answer will be : tunneling) - what controller do you use - hardware or VM . If VM - what type of VM - VmWare or HyperV.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-06-2017 03:14 PM
Hi Ilya,
I encounter the same problem as yours.
May I know what is the root cause and the solution?
I encounter the same problem as yours.
May I know what is the root cause and the solution?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-06-2017 03:14 PM
Hi Doug,
Now it's OK, I've just reinstalled controller using your *.xml file.
Now it's OK, I've just reinstalled controller using your *.xml file.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-06-2017 03:14 PM
llya,
Is this still an issue for you or are you all set?
Is this still an issue for you or are you all set?
Doug Hyde
Director, Technical Support / Extreme Networks
Director, Technical Support / Extreme Networks