Windows 10: Interfaces and Routing via CMD

Little background, I keep randomly losing connecting and my network and file paths are just a disaster. My networking interfaces kept randomly disappearing. Also even though I've downloaded the correct drivers from the manufacturer, they never actually update. I came across this while looking up the IPv6 prefix addresses in an attempt to, at the very least, make sure everything is setup correctly.


C:\Users\AccountName>netsh
netsh>int ipv6
netsh interface ipv6>show route

Publish Type Met Prefix Idx Gateway/Interface Name
------- -------- --- ------------------------ --- ------------------------
No Manual 256 ::/0 6 2601:547:c502:353f:fa2d:c0ff:fe88:6f15
No Manual 256 ::/0 7 fe80::fa2d:c0ff:fe88:6f15
No System 256 ::1/128 1 Loopback Pseudo-Interface 1
No Manual 256 2601:547:c502:353f::/64 7 Wi-Fi
No System 256 2601:547:c502:353f::6348/128 7 Wi-Fi
No System 256 2601:547:c502:353f:946:e5d0:c398:ae24/128 7 Wi-Fi
No System 256 2601:547:c502:353f:d87d:f815:e3e0:4d50/128 7 Wi-Fi
No System 256 fe80::/64 7 Wi-Fi
No System 256 fe80::/64 6 Ethernet
No System 256 fe80::/64 39 Local Area Connection* 15
No System 256 fe80::d87d:f815:e3e0:4d50/128 7 Wi-Fi
No System 256 fe80::dcb1:b550:4988:cd34/128 6 Ethernet
No System 256 fe80::f4a3:4d15:2a51:51ba/128 39 Local Area Connection* 15
No System 256 ff00::/8 1 Loopback Pseudo-Interface 1
No System 256 ff00::/8 7 Wi-Fi
No System 256 ff00::/8 6 Ethernet
No System 256 ff00::/8 39 Local Area Connection* 15



Now, the web page said:

"The IP-HTTPS prefix is defined as a route on a Forefront UAG DirectAccess server. To view the IP-HTTPS prefix assigned to a node in an array, from the command prompt, run netsh int ipv6 show route, or route print. In the resulting table, you should see a record with: Publish=Yes, Interface Name contains the string iphttps, and a Prefix of /64. The IP-HTTPS prefix of the node appears before the /64 suffix. The route associated with the IP-HTTPS network interface is set to a 64-bit prefix and is published to the clients connected to this node. "


How do I fix this? I'm just returning to Windows from Mac because of this exact file system issue. I haven't used Windows since XP and I'm clueless how to fix this.

:)

 

Network Routing Tables


Hi everyone!


I recently started using a VPN. However some websites block VPN ips so I can't visit them.
To solve this problem I would like to add the blocked website's IP to my route table.
It works fine on my other laptops but on my PC it doesn't seem to function. I ran the following command as an administrator in my cmd. Got the OK! feedback message but I still get blocked from visiting the website when on a VPN.


Code: Route add [website IP] [Default Gateway][/quote]


At the bottom of this screenshot :






you can see that the IP is indeed added to the list but sadly it doesn't function. I have been suggested to reinstall my Windows 10 but was wondering if there aren't any other solutions to this problem.


Thanks in advance!

 

GPS on N8 - see route step by step

If by step by step, you mean a text listing of your route with turns listed, this is not available. This would be a useful feature and maybe you could contact the Nokia Beta Lab to ask if it can be added to a future version. It is however possible to
see a graphical display of your route.

 

Default route nonsense


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).