VLAN

Kernels & Hardware, configuring network, installing services

VLAN

Postby jihan139 » 2018-06-26 12:48

I have 2 vlans, VLAN3 and VLAN10
on VLAN3 i have 3 Debian servers a 32bit and a 64bit, on VLAN10 I have my backup server.

The 64bit server have no problems pinging the backup server on VLAN10, but the 32bit can't

does anyone have an ide where to start looking, everything is fine in /etc/network/interfaces
jihan139
 
Posts: 2
Joined: 2018-06-26 12:44

Re: VLAN

Postby p.H » 2018-06-26 17:09

Please post raw FACTS, not your interpretation of them.
How are the VLANs interconnected ?
jihan139 wrote:The 64bit server have no problems pinging the backup server on VLAN10, but the 32bit can't

How does it fail ? What happens exactly ? Please post the raw output.
What about the other way around ?
Also, traceroute may provide more information than ping.
jihan139 wrote:everything is fine in /etc/network/interfaces

Please post the contents of all involved hosts so that we can see by ourselves.
Also post the routing tables and firewall rules (iptables, nftables, whatever you use) of all involved hosts and routers.
p.H
 
Posts: 403
Joined: 2017-09-17 07:12

Re: VLAN

Postby jihan139 » 2018-06-27 05:34

The VLANS are connected through a asa 5510 cisco firewall with tagged ports.

When I ping from the 32bit the following happens:
r2p@DKSISESKORRINGICONNEX01:~$ ping 192.168.10.150
PING 192.168.10.150 (192.168.10.150) 56(84) bytes of data.
^C
--- 192.168.10.150 ping statistics ---
11 packets transmitted, 0 received, 100% packet loss, time 10229ms

But from the 64Bit:
r2p@DKSISEARRIVAVOIPLIVE:~$ ping 192.168.10.150
PING 192.168.10.150 (192.168.10.150) 56(84) bytes of data.
64 bytes from 192.168.10.150: icmp_seq=1 ttl=128 time=0.403 ms
64 bytes from 192.168.10.150: icmp_seq=2 ttl=128 time=0.472 ms
64 bytes from 192.168.10.150: icmp_seq=3 ttl=128 time=0.481 ms
64 bytes from 192.168.10.150: icmp_seq=4 ttl=128 time=0.521 ms
64 bytes from 192.168.10.150: icmp_seq=5 ttl=128 time=0.508 ms
64 bytes from 192.168.10.150: icmp_seq=6 ttl=128 time=0.546 ms
^C
--- 192.168.10.150 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5064ms
rtt min/avg/max/mdev = 0.403/0.488/0.546/0.050 ms

both on same vlan pining the same server on diffrent vlan

pinging the 32 bit server from vlan 10 is no problem:
Pinging 192.168.3.65 with 32 bytes of data:
Reply from 192.168.3.65: bytes=32 time=1ms TTL=64
Reply from 192.168.3.65: bytes=32 time=1ms TTL=64
Reply from 192.168.3.65: bytes=32 time=1ms TTL=64
Reply from 192.168.3.65: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.3.65:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms


32bit:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto ens192
iface ens192 inet static
address 192.168.3.65
netmask 255.255.255.0
gateway 192.168.3.1


ip a from 32bit:
2: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:50:56:94:4e:88 brd ff:ff:ff:ff:ff:ff
inet 192.168.3.65/24 brd 192.168.3.255 scope global ens192
valid_lft forever preferred_lft forever
inet6 fe80::250:56ff:fe94:4e88/64 scope link
valid_lft forever preferred_lft forever

64bit:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto ens192
iface ens192 inet static
address 192.168.3.70
netmask 255.255.255.0
gateway 192.168.3.1

ip a 64bit
2: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:50:56:94:4e:e2 brd ff:ff:ff:ff:ff:ff
inet 192.168.3.70/24 brd 192.168.3.255 scope global ens192
valid_lft forever preferred_lft forever
inet6 fe80::250:56ff:fe94:4ee2/64 scope link
valid_lft forever preferred_lft forever

Edit*

traceroute for google.com
r2p@DKSISESKORRINGICONNEX01:~$ traceroute google.com
google.com: Temporary failure in name resolution
Cannot handle "host" cmdline arg `google.com' on position 1 (argc 1)

traceroute for vlan10 (unreacable)
r2p@DKSISESKORRINGICONNEX01:~$ traceroute 192.168.10.150
traceroute to 192.168.10.150 (192.168.10.150), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *

traceroute from 64bit to vlan 10
root@DKSISEARRIVAVOIPLIVE:~# traceroute 192.168.10.150
traceroute to 192.168.10.150 (192.168.10.150), 30 hops max, 60 byte packets
1 veeam.protracking.local (192.168.10.150) 0.442 ms * *
jihan139
 
Posts: 2
Joined: 2018-06-26 12:44


Return to System configuration

Who is online

Users browsing this forum: No registered users and 7 guests

fashionable