0

I have two webservers. Webserver A has this route (netstat -r):

Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
192.168.40.0    0.0.0.0         255.255.255.0   U         0 0          0 eth0

and Webserver B has this route instead:

Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
192.168.40.0    *               255.255.255.0   U         0 0          0 eth0

Is there a difference?

I have timeout problems while trying to connect my netbeans with xdebug on webserver A and get "Waiting for Connection" in netbeans which stays forever, is it related to the route?

Update:

Output of ip route list:

Webserver A:

default via 192.168.40.20 dev eth0
192.168.40.0/24 dev eth0 proto kernel scope link src 192.168.40.44

Webserver B:

default via 192.168.40.20 dev eth0
192.168.40.0/24 dev eth0  proto kernel  scope link  src 192.168.40.47
  • What OS do you use? – Anton Danilov Jul 31 '19 at 8:01
  • I am using openSUSE Linux – Black Jul 31 '19 at 8:02
  • 1
    So don't use the deprecated tools (ifconfig, route). Check the output of ip route list and you will see the difference. Paste the output into the question. Also you can resolve the actual route with ip route get <dst> command. Try to use it to troubleshoot your issue. – Anton Danilov Jul 31 '19 at 8:04
  • 1
    Seems like you have different versions of netstat. Check the output of netstat --version. There isn't the difference between routing configuration. – Anton Danilov Jul 31 '19 at 8:10
  • 1
    The difference in the source address attribute is related with assigned address on the eth0 interface, not more else. – Anton Danilov Jul 31 '19 at 8:11
3
  1. Don't use the deprecated tools like ifconfig, route and so on. Use the tools from iproute package.

    • ip route list - to check the routing table
    • ip route get <dst> - resolve the actual route - the packets to the specified destination will go through this route.
  2. The difference in the output is related with different versions of netstat tool.

  3. The routing configuration on the hosts is the same.
  4. To troubleshoot the connectivity issues you can use the tcpdump at first step.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.