SOLVED Can't reach default gateway and the Internet?

[ChicagoGregg]

Good evening,

I thought I was onto something with another post from 2012 titled "Unable to ping outside of the jail". It eluded to enabling promiscuous mode.

On the other hand, this really comes down to a basic networking issue. For some reason, I cannot ping the default route IP from the NAS, but I can ping it just fine with all other network devices on the network.

Here's the layout:

I have NAS running within ESXi. Promiscuous mode is on in the ESXi vSwitch0.
Router / Default Route: 192.168.0.1
NAS: 192.168.0.11/16
DHCP for hosts 192.168.1.100-.254 (Basically, 192.168.0.x are for network duties (router, nas, my lab DC, App servers, etc.), 192.168.1.100-.254 are for devices connecting in otherwise (wifi))

Other hosts on the 192.168.x.x network can ping 192.168.0.1, 192.168.0.11 (nas), and other hosts on the network just fine (icmp replies).
NAS can ping hosts on the 192.168.x.x hosts, but can't ping the router 192.168.0.1. Nor can it ping Internet IP addresses (I tried pinging my VPS and a few others).

From NAS:

---

root@vp1nas01[~]# ifconfig -a
vmx0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
description: vmx0
options=e403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
ether 00:0c:29:c5:d4:d6
inet 192.168.0.11 netmask 0xffff0000 broadcast 192.168.255.255
media: Ethernet autoselect
status: active
nd6 options=9<PERFORMNUD,IFDISABLED>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
inet 127.0.0.1 netmask 0xff000000
groups: lo
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
pflog0: flags=0<> metric 0 mtu 33160
groups: pflog
root@vp1nas01[~]# ping 192.168.0.1 # router
usage: ping [-AaDdfnoQqRrv] [-c count] [-G sweepmaxsize] [-g sweepminsize]
[-h sweepincrsize] [-i wait] [-l preload] [-M mask | time] [-m ttl]
[-P policy] [-p pattern] [-S src_addr] [-s packetsize] [-t timeout]
[-W waittime] [-z tos] host
ping [-AaDdfLnoQqRrv] [-c count] [-I iface] [-i wait] [-l preload]
[-M mask | time] [-m ttl] [-P policy] [-p pattern] [-S src_addr]
[-s packetsize] [-T ttl] [-t timeout] [-W waittime]
[-z tos] mcast-group
root@vp1nas01[~]# ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
--- 192.168.0.1 ping statistics ---
9 packets transmitted, 0 packets received, 100.0% packet loss
root@vp1nas01[~]# ping 192.168.0.20
PING 192.168.0.20 (192.168.0.20): 56 data bytes
64 bytes from 192.168.0.20: icmp_seq=0 ttl=128 time=0.314 ms
64 bytes from 192.168.0.20: icmp_seq=1 ttl=128 time=0.213 ms
--- 192.168.0.20 ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.150/0.222/0.314/0.053 ms
root@vp1nas01[~]# ping 192.168.1.121
PING 192.168.1.121 (192.168.1.121): 56 data bytes
64 bytes from 192.168.1.121: icmp_seq=0 ttl=128 time=1.144 ms
64 bytes from 192.168.1.121: icmp_seq=1 ttl=128 time=0.264 ms
--- 192.168.1.121 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.231/0.478/1.144/0.385 ms

---

Any ideas???

Thanks in advance!

-gregg

 

[ChicagoGregg]

Hello,

I resolved this issue. It wound up being a route that I had on my router. Oops! I just reworked some networking recently and forgot about that one.

Please disregard this thread.

Thanks. :)

-gregg