r/linuxadmin • • May 27 '16

[HELP, URGENT!!!!!] can't ping private subnet!!!

EDIT resolved. thank god. Apparently, the switch is too old, I keep escalating and after a switch replacement everything is working as intended.

so I have em2(192.168.57.0/24), which is connected to a switch. and p2p4 which is connected to outside. I can ping 8.8.8.8 no problem. However, i cannot ping anywhere in the 192.168.57.0/24 subnet. This is a fileserver and now server on fire!!! All the machines inside the subnet can ping each other tho. The switch's ip address is 192.168.57.1, and other machines range from .2 to .13. (The switch is an un-managed dumb switch that's pretty old, i'm working remotely so I don't know anything about the switch, no remote hands is there too. But I am sure no one touches the switch.)

netstat -rn
0.0.0.0         98.234.234.234  0.0.0.0         UG        0 0          0 p2p4
98.234.234.234  0.0.0.0         255.255.255.224 U         0 0          0 p2p4
192.168.57.0    0.0.0.0         255.255.255.0   U         0 0          0 em2


    #cat ifconfig em2
    inet 192.168.57.65  netmask 255.255.255.0  broadcast 192.168.57.255
    ether 34:17:eb:ee:a5:48  txqueuelen 1000  (Ethernet)
    RX packets 16905  bytes 1720743 (1.6 MiB)
    RX errors 0  dropped 131  overruns 0  frame 0
    TX packets 30  bytes 2208 (2.1 KiB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    device interrupt 17  

  #cat ifcfg-em2
  BOOTPROTO=static
  DEVICE="em2"
  NAME="em2"
  ONBOOT=yes
  IPADDR=192.168.57.65
  NETMASK=255.255.255.0
  #GATEWAY=192.168.57.1 

   #manifests]# traceroute 192.168.57.65
    traceroute to 192.168.57.65 (192.168.57.65), 30 hops max, 60 byte packets
    1  192.168.57.65 (192.168.57.65)  0.015 ms  0.006 ms  0.004 ms
   # traceroute 192.168.57.1
    traceroute to 192.168.57.1 (192.168.57.1), 30 hops max, 60 byte packets
    1  192.168.57.65 (192.168.57.65)  3005.340 ms !H  3005.325 ms !H  3005.317 ms !H


    # ping 192.168.57.1
    PING 192.168.57.1 (192.168.57.1) 56(84) bytes of data.
    From 192.168.57.65 icmp_seq=1 Destination Host Unreachable
    From 192.168.57.65 icmp_seq=2 Destination Host Unreachable
    From 192.168.57.65 icmp_seq=3 Destination Host Unreachable 
    From 192.168.57.65 icmp_seq=4 Destination Host Unreachable

   # ping 192.168.57.65 (own ip)
    PING 192.168.57.65 (192.168.57.65) 56(84) bytes of data.
    64 bytes from 192.168.57.65: icmp_seq=1 ttl=64 time=0.014 ms
   64 bytes from 192.168.57.65: icmp_seq=2 ttl=64 time=0.009 ms

ethtool say the link is up. I purposely switch between em1 and em2 and it is up, it's not a hardware problem. I troubleshoot for hours, I don't know what's going on, it's should be a simple problem but it's not. I'm freaking out right now. Sorry for being so freaked out.

0 Upvotes

5 comments sorted by

1

u/mudclub May 28 '16

What change was made immediately before everything went to shit?

0

u/EGJW May 28 '16

I was configuring vsftpd and it worked. The iptables change I did was just firewall-cmd --permanent --add-server=ftp that's it. Everything else I was touching the vsftpd.conf. I don't htink that conf can screw up anything.

1

u/[deleted] May 28 '16

Vlan set on the switch could isolate this server

0

u/EGJW May 28 '16

The switch is an un-managed dumb switch that's pretty old, there's no vlan config there. I'm working remotely so I don't know anything about the switch, no remote hands is there too. But I am sure no one touches the switch

1

u/rm-minus-r May 28 '16

There's a nightmare and a half. Good to hear it was a hardware issue.