Quantcast
Viewing latest article 4
Browse Latest Browse All 72

IP6 and ping !

  • Ah, looks as if you may have routing and/or firewall issues.

Do you have static route entries:
      a) in 192.168.2.254 that indicates how to get to the 192.168.4.0/24 network?
            which is via the Vyatta at 192.168.2.50

  • This the rule I have created on Vyatta before :
  • yatta@vyatta:~$ configure
  • [edit]
  • vyatta@vyatta# show protocols
  •  static {
  •      route 192.168.2.0/24 {
  •          next-hop 192.168.4.1 {
  •          }
  •      }
  •  }
  • [edit]
  • vyatta@vyatta#
          b) in 192.168.4.1  that indicates how to get to the 192.168.2.0/24 network?
                which is via the ISP-Rtr at 192.168.2.254
  • the vyatta is DMZ configured on my ISP so I can reach my ISP router behind vyatta network

That coupled with possible mixed DNS entries, and IPv4 -vs- IPv6 operations in Windows could be some cause of confusion.

Try these tests:
1) from a device on 192.168.2.0 (not the ESXi srvr, not the Vyatta, not the ISP rtr) network - laptop on WLAN perhaps:
     a) ping 192.168.4.2

C:\>ping 192.168.4.2
Pinging 192.168.4.2 with 32 bytes of data
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.4.2:
 Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

     b) ping DC -4     (or whatever the DNS name for 192.168.4.2 is)
     c) repeat for .3 , EX, .4, FS

C:\>ping dc -4
Pinging DC [192.168.4.2] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.4.2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\>ping fs -4

Pinging FS [192.168.4.4] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.4.4:

   Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


2) from a device on 192.168.4.0 (not Vyatta, not ESXi) - perhaps EX again
     a) ping the laptop's IPv4 address

C:\Users\info>ping 192.168.2.111
Pinging 192.168.2.111 with 32 bytes of data:
Reply from 192.168.2.111: bytes=32 time=1ms TTL=127
Reply from 192.168.2.111: bytes=32 time<1ms TTL=127
Reply from 192.168.2.111: bytes=32 time<1ms TTL=127
Reply from 192.168.2.111: bytes=32 time<1ms TTL=127
Ping statistics for 192.168.2.111:

   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

   Minimum = 0ms, Maximum = 1ms, Average = 0ms

C:\Users\info>

Do you any firewalls enabled on any of the Windows computers (which Win has on by default), if so, pings will fail.

Do you have any firewall rules on the Vyatta that would block pings going through?

Your ESXi has only one NIC as 192.168.2.10 -and- therefore you must have the servers and Vyatta as VMs in the 192.168.4.0 network which is a different vSwitch interface -and- the Vyatta has its interfaces: 1 in the vSwitch physical port out, and the other in the local vSwitch (no network port) - true ????

My ESXI has one physical NIC which is 192.168.2.10, Vyatta is VM with two virtuals NICs

this my Network Diagram

Image may be NSFW.
Clik here to view.




Viewing latest article 4
Browse Latest Browse All 72

Trending Articles