Default route nonsense

altae · 08 Aug 2016

Any network experts here that can tell me what on earth my system is doing? Today I noticed that I cannot ping anything on my network. I took a look into the routing table and found out that there is a route 192.168.1.0 mask 255.255.255.0 gateway 192.168.1.1 interface 127.0.0.1 ????? Really, what miracle, you cannot connect to anything within 192.168.1.0 through the loopback adapter? What a surprise! I can delete it but the system creates it again with every reboot. So I've fixed it by entering a permanent static route to 192.168.1.0 through the correct network interface. But this is only a workaround. Can somebody tell me how to permanently get rid of that idiotic entry?

Samuria · 08 Aug 2016

Can you run this tool by right clicking and choosing run as admin then post results http://www.crewetown.co.uk/wireless.exe it does all networks and will give us an idea whats going on

altae · 08 Aug 2016

Here are the results...

Samuria · 08 Aug 2016

I would say the problem are around the fact your using a proxy AVKProxy so everything will be routed via the proxy you can stop it sc stop "AVKProxy"
sc config "AVKProxy" start= disabled

altae · 08 Aug 2016

I don't use no proxy. Everything that runs under the name "AVK" belongs to the AV/ Firewall.

bro67 · 09 Aug 2016

192.168.1.0 is the routing table for all IP's below it. 192.168.1.1/24 is the IP that computers use to connect to the Gateway to get their IP lease from. 127.0.0.1 is for Local Host. If it is working, do not change anything. Otherwise you will break the routing table.

altae · 09 Aug 2016

127.0.0.1 is the loopback adapter. It's impossible to connect to the LAN through the loopback adapter. Traffic to the LAN needs to go through the interface that is connected to the router (gateway).

bro67 · 09 Aug 2016

altae said:

127.0.0.1 is the loopback adapter. It's impossible to connect to the LAN through the loopback adapter. Traffic to the LAN needs to go through the interface that is connected to the router (gateway).

You did not even read what I had posted. 127.0.0.1 is looked at by any host as the "Localhost", not Loopback. It is also how the OS checks to make sure that the adapter is enabled or disabled.

As long as you see in Routes and on the adapter, that you have a proper IP Scheme and your Gateway Address is 192.168.1.1, it will work. The Gateway handles all routing of all traffic, even if you have the device set with a Static IP.

If you are running a Firewall, it can cause no traffic to go outside of the computer to the Gateway.

bro67 · 09 Aug 2016

Your routing table is all jacked up. You have the VMware set for 192.168.195.1, which means that if you are trying to connect to it, you will never be able to from another machine. If you are using the Fritzbox for handling any routing and firewall, you need to go check those settings.

altae · 09 Aug 2016

The VMWare entry is not relevant here, that's the entry for the host only network. I don't use that, my virtual machine is directly connected to the router in bridged mode. The VM's internal ip is assigned by the router (static ip) and it's 192.168.1.172. What's more the VM's connectivity works flawlessly so we can leave that aside.

Once more, I'm talking about the entry that sends all traffic form my PC to an address within 192.168.1.0/24 through the interface that is referred to as 127.0.0.1 which would be the loopback adapter. The entry is marked with a red arrow in the attached image. To circumvent it I need to create a permanent static route, marked with yellow arrows in the same image. What's more there is a second image showing the list of interfaces on my system which should also clarify that it's the interface that is the problem, not the destination. It's completely ok for the routing table to contain an entry for localhost. But it's not ok to route traffic to the LAN through the loopback adapter (interface 127.0.0.1).