• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1197
  • Last Modified:

Ping between Two VLAN's

Hello All,

In our network we have 2 VLAN's (vlan-41 and Vlan-42). i connected a laptop LAN to Vlan-41 and Wifi to Vlan-42. when i try to ping/access wifi (vlan-42 IP) i am unable to access but, i can able to access LAN (vlan-41 IP).

both VLAN's are working normal.

can any body help me to resolve the issue. i need to make this work in our office.


Thanks in Advance
0
hellosoft
Asked:
hellosoft
  • 7
  • 6
1 Solution
 
lesliem-saCommented:
Hi,

a few questions:
is other lan traffic between vlan-41 and vlan-42 working correctly?  Can you ping the AP ip address on vlan-42 from a host on vlan-41?
what device is routing traffic between the vlans?  Are both vlans allowed over the trunk?
how is the port configured where the ap plugs into the switch?
are you using more than 1 switch in your network?
Is your AP configured to tag packets?

Regards,
Leslie
0
 
hellosoftAuthor Commented:
Hello Leslie,

First Thanks for your quick response.

1) Traffic between Vlan-41 and Vlan-42 is fine.
2) Can able to ping from vlan-41 to AP on vlan-42.
3) using Hp pro-curve switch for routing between vlan-41 and vlan-42.
4)yes, both vlan's are allowed over trunk
5)Yes, we are using more number of switches.
6) there is not specific configuration of ports for AP.
7)AP is configured with basic settings.

Thanks,
Rafi
0
 
lesliem-saCommented:
OK, just to be clear - you are trying to ensure that all wireless clients connected to teh AP are on Vlan-42?
If there is no vlan configuration in the AP itself, then you need to add the port that the AP connect to to the vlan-42 vlan - set it as "untagged"  This will put the AP itself in the vlan-42 vlan - check that it is on the correct network, and also check that the AP clients are getting the correct ip addresses for the vlan-42 vlan.
0
Improved Protection from Phishing Attacks

WatchGuard DNSWatch reduces malware infections by detecting and blocking malicious DNS requests, improving your ability to protect employees from phishing attacks. Learn more about our newest service included in Total Security Suite today!

 
hellosoftAuthor Commented:
ok i got it.

AP connected to vlan-42 (port is untagged to vlan-42).

the idea is :
i got laptop 1 interface to vlan-41 and one interface to vlan-42. i can able to ping vlan-41 interface from machine in vlan-41 network and vlan-42 interface from machine in vlan-42 network. but not able to ping vlan-41 interface from machine in vlan-42 network.. vice ..versa.

(but routing is working between vlan-41 and vlan-42 traditionally)


Cheers,
Rafi
0
 
lesliem-saCommented:
Hi Rafi,

If other hosts are able to ping each other across the two clans, then it could be a firewall on the laptop that is blocking the pings?
0
 
hellosoftAuthor Commented:
yes,

other hosts can ping each other (vlan41 to vlan42 and vice versa).
vlan-42 hosts can ping vlan-42 ip of laptop, vlan-41 hosts can ping vlan-41 ip of laptop.

firewall is already disabled in laptop...

Any ideas Please
0
 
lesliem-saCommented:
Would you try ping the laptop vlan-41 interface from a host on vlan-42 and then run "arp -a" to see what mac address is being resolved for the laptop vlan-41 interface please?
0
 
lesliem-saCommented:
Also, please do a trace route to the laptop vlan-41 interface from a host on vlan-42.
0
 
hellosoftAuthor Commented:
Hi,

Actually with another laptop with windows i can able to ping to both vlan's. but, with linux OS it's not working.

Thanks
0
 
lesliem-saCommented:
are you doing any vlan tagging within the linux network stack?
0
 
hellosoftAuthor Commented:
Nope!!

same for both windows and Linux.
0
 
lesliem-saCommented:
I should have asked this long ago, but:
Why are you trying to ping from vlan-41 to the interface in vlan-42 when the host already has an interface in vlan-41.  What are you trying to achieve.

It is possible, that this is by design in linux - according to its routing table, to reach the vlan-41 subnet (originating IP) is sends the return packet via its vlan-41 interface instead of using the interface that it received the icmp packet on originally (vlan-42) ?
0
 
hellosoftAuthor Commented:
Hi,

Actually ping is required for testing VoIP related stuff by our testing teams.

i didn't understand second half could you please elaborate..
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Become an IT Security Management Expert

In today’s fast-paced, digitally transformed world of business, the need to protect network data and ensure cloud privacy has never been greater. With a B.S. in Network Operations and Security, you can get the credentials it takes to become an IT security management expert.

  • 7
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now