Configure VLAN using 2 lan card between 2 hosts

[Youlette Etienne_2]

I currently have this scenario configured and working between 2 hosts. However, I am encountering a problem with configuring this between two additional (separate from the above) hosts.

The VLAN IPs are on subnet 172.17.4.0.

host#1:
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 lo0 4136
172.17.4.4 172.17.4.4 UH 0 lan2 4136
172.20.15.91 172.20.15.91 UH 0 lan1 4136
172.20.15.0 172.20.15.91 U 2 lan1 1500
172.17.4.0 172.17.4.4 U 2 lan2 1500
172.17.4.0 172.17.4.1 UG 0 lan2 0
127.0.0.0 127.0.0.1 U 0 lo0 0
default 172.20.15.1 UG 0 lan1 0

host#2:
Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 lo0 4136
172.17.4.3 172.17.4.3 UH 0 lan1 4136
172.20.15.90 172.20.15.90 UH 0 lan0 4136
172.20.15.0 172.20.15.90 U 2 lan0 1500
172.17.4.0 172.17.4.3 U 2 lan1 1500
127.0.0.0 127.0.0.1 U 0 lo0 0
default 172.20.15.1 UG 0 lan0 0

host#3:
Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 lo0 4136
172.17.4.2 172.17.4.2 UH 0 lan1 4136
172.20.15.89 172.20.15.89 UH 0 lan0 4136
172.20.15.0 172.20.15.89 U 2 lan0 1500
172.17.4.0 172.17.4.2 U 2 lan1 1500
127.0.0.0 127.0.0.1 U 0 lo0 0
default 172.20.15.1 UG 0 lan0 0

I can ping host#2 from host#3 and vice versa:
ping 172.17.4.2
PING 172.17.4.2: 64 byte packets
64 bytes from 172.17.4.2: icmp_seq=0. time=0. ms
64 bytes from 172.17.4.2: icmp_seq=1. time=0. ms

But I cannot ping host#3 or host#2 from host#1, or vice versa. host#1 VLAN IP
172.17.4.5 is unreachable:
ping 172.17.4.2
PING 172.17.4.2: 64 byte packets
---172.17.4.2 PING Statistics----
22 packets transmitted, 0 packets received, 100% packet loss

I also swapped host#1 and host#2 VLAN IP addresses to make sure that the IPs were valid. host#1 was still unreachable, yet host#2 and host#3 could communicate via the VLAN IPs.

Help! I don't see where the issue is. Thanks

[Steven E. Protter · Accepted solution]

Shalom,

It could be network masking problems.

I would need to see ifconfig data on the netmask to begin analyzing the problem.

My take so far is that this is complex, perhaps moreso than it needs to be.

SEP

[Mridul Shrivastava]

R u able to ping default gateway 172.20.15.1 from host#1, if u r not able to ping gateway itself then we have to check that first before moving forward.

[Youlette Etienne_2]

It turned out that the network admin did not configure the ports at the switch as I thought. That's what the problem is.
Thanks for responding

[Youlette Etienne_2]

...