Question Locked

VLANs and routing trouble

0 helpful
20 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I set up some new vlans to improve security on my gigantic flat network. We have rental offices on site on the same network as our servers! Not good. I've decided to use 192.168 networks (10 total) in .25 increments (192.168.25.X, 192.168.50.X, etc). I was in the testing phase working with ACLs when I discovered some computers not being able to access computers on different subnets even though they can access others on that subnet. Example, I can successfully ping from 192.168.175.130 to 192.168.25.21. I cannot ping from 192.168.175.130 to 192.168.25.38. I can ping the 192.168.25.38 from anything on the 192.168.25.X network. I have a Cisco 2800 router and turned off the ACLs, problem still persists. I thought maybe it was the no proxy-arp command that was causing the intermittent issues but I turned on proxy-arp and that did not fix it either.
FYI: All subnets do have internet access - All subnets are physically connected to 1 interface with sub-interfaces in use (fa0/0.25, etc) - the ip addresses I'm having trouble with are not accessible from any of the new subnets (.14, .15, .16, .18, ,28 .38 to name a few) but other close numbers are (.7 , .10, .21, .37, etc). These nodes are all connected to the same switch.
I'm stuck on this one, has anyone had similar issues with a cisco 2800 series router?

20 replies

by netman1958

If you go to the computer at 192.168.175.130 and run a traceroute to 192.168.25.38, is the first hop IP Address the same IP that is assigned to the subinterface on the router that is assigned to the VLAN for 192.168.175.130?

by mcooper

Yes.
If I run tracert as you specified, it shows me 192.168.175.5 (router's IP) for that subnet/vlan, then * * *.
If I run tracert for 192.168.25.37, I get the router's IP 192.168.175.5 and success to 192.168.25.37. I'm wondering if a simple reboot is needed. I'm going to do that now, I'll see if that fixes it.

by mcooper

Nothing changed after the reboot, it must be something in my configuration. I'm going to go home and think some more on this one...

by netman1958

You need to try that traceroute in reverse; that is traceroute from 192.168.25.38 to 192.168.175.130 and make sure the first hop is correct. If that test passes, post your router config and we'll take a look.

OH, also before you go too far in this, try disabling the firewall on the affected computer, if it is enabled. Sometimes the Windows firewall will allow same subnet traffic but not from a different subnet.

by mcooper

Here's an interesting thing, and maybe the answer to my question, I noticed that all the devices I was trying to access/ping were not computers - some were Wireless Access Points, some Printers/copiers, and a NAS. I swapped one of the access point's ports with a laptop, gave it the access point's IP address (.38), and I was able to ping it from the .175.130 ip address. I tried another one too, the .47 and was also successful.
Now for the $100 question, why do all of the access points (all same model and bought at the same time) with the same configuration accept pings/remote admin and one of them does not? What would keep the printers from responding to pings? I know this is probably not a question for this forum.

Thanks for all the help! Once you said to turn off the firewall, it got me thinking about the devices on the other end. I suppose I'm going to have to rethink my design to ensure all appropriate groups can get to the printers/NAS/etc.

by netman1958

Some printers/copiers while they don't exactly have firewalls, do allow you to specify the IP Addresses/subnets that can access them. Also, for security sometimes those devices are configured without a default gateway.

by tobif

The subnet mask tells each host (computer) on an IP network, what addresses should be directly available.
Although we're used to represent these addresses as 4 numbers, divided by dots, the IP address is, in fact, a binary number, consisting of 32 binary digits.

The subnet mask must begin with only binary "ones", and must finish with only binary "zeroes". Most convenient, is to split the subnet part of the address at 8, 16 or 24 digits. In the usual notation, this will give us typical masks, like 255.255.255.0 etc.

Also, in any subnet, two addresses are reserved for special use, namely "all zeroes" and "all ones".

The smallest possible subnet will have an address space of 2 bits, i.e. 4 addresses, out of which 2 addresses are reserved. So this network can cater only for a connection between two hosts.

If you want to have space for 25 addresses in each subnet, then a subnet with 16 addresses (4 bits) is too small, but a subnet of 32 addresses (5 bits) could work.

This will give you the following structure:
192.168.x.
0 --31
32 -- 63
64 -- 95
96 -- 127
128 -- 159
160 -- 191
192 -- 223
224 -- 255

And remember, that you can't use the first and the last address in each subnet.

Oh, and the subnet mask shall be 255.255.255.224

by mcooper

Thank you for the re-fresh course on sub-netting - I took the CCNA courses, but it has been a few years ago. I do not think my LAN design is incorrect. I use PAT to translate anything sent from my router to one outside IP address.
My LAN design is:
192.168.25.X 255.255.255.0
192.168.50.X 255.255.255.0
192.168.75.X 255.255.255.0
192.168.100.X 255.255.255.0
192.168.125.X 255.255.255.0
192.168.150.X 255.255.255.0
192.168.175.X 255.255.255.0
192.168.200.X 255.255.255.0
192.168.225.X 255.255.255.0
192.168.250.X 255.255.255.0
172.16.1.X 255.255.255.0
172.16.2.X 255.255.255.0
Also, I believe you can use the first subnet if you use the ip subnet-zero command.

Let me know if you see a flaw in my design, I appreciate your help:)

by tobif

I read your initial post too quickly, and thought you were incrementing the last group.

All looks fine, which also now have proven, as things started working.

by cg it

what's your route table look like?

router has to know how to handle the frames....

by mcooper

Here is the routing table from my router.

gw#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is 192.168.25.2 to network 0.0.0.0

C 192.168.75.0/24 is directly connected, FastEthernet0/0.75
C 192.168.225.0/24 is directly connected, FastEthernet0/0.225
C 192.168.150.0/24 is directly connected, FastEthernet0/0.150
C 192.168.25.0/24 is directly connected, FastEthernet0/0.25
C 192.168.125.0/24 is directly connected, FastEthernet0/0.125
172.16.0.0/24 is subnetted, 2 subnets
C 172.16.1.0 is directly connected, FastEthernet0/0.13
C 172.16.2.0 is directly connected, GigabitEthernet0/0/0.12
C 192.168.200.0/24 is directly connected, FastEthernet0/0.200
C 192.168.250.0/24 is directly connected, FastEthernet0/0.250
C 192.168.175.0/24 is directly connected, FastEthernet0/0.175
10.0.0.0/22 is subnetted, 1 subnets
S 10.1.0.0 is directly connected, GigabitEthernet0/0/0.12
C 192.168.50.0/24 is directly connected, FastEthernet0/0.50
C 192.168.100.0/24 is directly connected, FastEthernet0/0.100
S* 0.0.0.0/0 [1/0] via 192.168.25.2
gw#
gw#

by netman1958

Your route table looks fine. Run this debug to see if the router is routing properly:

First, create an extended access list; example:
"access-list 101 permit ip host 192.168.175.130 host 192.168.25.38"
"access-list 101 permit ip host 192.168.25.38 host 192.168.175.130"

Then:
"term mon"
"debug ip packet 101"

Then go to 192.168.175.130 and try to ping 192.168.25.38. Then examine the debug output to see how the router handled the packets.

by cg it

since the router knows the networks, and you have ip routing enabled ?? along with a routing protocol like RIP/EIGRP/OSPF ???? and your using the right encapsulation...the router should route frames between vlans

when you ping do you get a destination unreachable? or ???

since you can ping one way but not another, sounds like the router doesn't know the route back.

by mcooper

Thanks to everyone for replying to my problem so quickly! I really appreciate it!

The problem was not in the routing or design, it is in the devices themselves (actually it was a picnic error, but blaming the devices is easier)
Netman1958 told me to disable the firewalls on bother devices and try again. I should have already thought of that since that always caught me years ago in my CCNA courses. Anyway, I found that all the devices have something in common, they are all not computers - they are copiers, WAPs, NAS, etc. If I plugg in a laptop to their switch port, configure it to have the other devices IP address, I can successfully ping. I did not expect this to be the issues and I really did not think copiers would have a firewall (and on that note, I did not see anything like that in the configuration of the copier).
Thanks again for all the help everyone.

by mcooper

many of the devices I was trying to ping had the wrong default gateway.
A while ago, we added a internal router to allow for the vlans and I forgot to update some of the configurations of some of the static assignments.
Thanks again for all who assisted me with this issue:)

by cg it

computers, access points and whatnot. the network card should respond to arp and ping[icmp] requests. the wrong default gateway would account for no return messages....

Glad you got it worked out.....

by mcooper

I followed the steps you indicated and did not see any traffic going through the router. I tried pinging and tracert from both sources. Just to make sure I was doing it right, I tried another access-list I created earlier to see if I got any output and I did.
here is what I imputed:
conf t
ip access-list 198 permit ip host 192.168.175.130 host 192.168.25.47
ip access-list 198 permit ip host 192.168.25.47 host 192.168.175.130
exit
term mon
debug ip packet 198

When that didn't work, I tried debug ip packet 101 (acl created for traffic filtering for incoming on .75 network) It showed a bunch of traffic.

by netman1958

Try replacing "ip" in the access list with "icmp" and see if that makes a difference since you are pinging. For example:
ip access-list 198 permit icmp host 192.168.175.130 host 192.168.25.47
ip access-list 198 permit icmp host 192.168.25.47 host 192.168.175.130

by mcooper

I do not have any routing protocols enabled. I only have static routes configured on the router.

The pings failed with "request timed out"

I was not able to ping one way. I must have not been 100% clear in my posts. I could ping from 192.168.175.130 to most nodes on the 192.168.25.X network, but not all. I was able to ping from most hosts on the 192.168.25.X network to the 192.168.175.130 host.
The nodes I could not ping were not computers; all were other pieces of equipment that did not have ping/tracert functionality. I suppose they must be filtering traffic somehow, that's going to throw a kink in the network design plans.

Thanks for the help with this issue! I think I understand why they are not working; now if I can figure out how to fix it...

This discussion is closed to new replies.