If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
How do I unscrew up the routing table?
I admit I was playing with the routing table, trying to learn it, but now
the fun is over because I screwed up and just want to get back to 'normal'. My network is "normal" in that: a. My router is 192.168.1.1 b. My desktop is 192.168.1.14 == it's dhcp but that's what it is below c. I know that 192.168.1.0 & 192.168.1.255 are "special" d. And that 127.0.0.1 is the "localhost" (and 127.0.0.0 must be "special") e. And that a netmask of 255's is all 1's (in binary) f. And that the "gateway" is just the "router" (of 192.168.1.1 below) g. And that 192.168.1.255 & 127.255.255.255 are "special" (somehow) h. And that 255.255.255.255 (not as a netmask) must also be "special" But ... what the heck are these numbers doing in the routing table below? A. 192.168.56.0 & 192.168.56.1 & 192.168.56.255 ? B. 224.0.0.0 ? C. 127.255.255.255.255 ? As admin, I tried to clear up the mess using: route delete * and route -f This gets me the following immediately thereafter: route print IPv4 Route Table ================================================== ========================= Active Routes: None Persistent Routes: None IPv6 Route Table ================================================== ========================= Active Routes: None Persistent Routes: None But when I reboot, this always comes up: route print IPv4 Route Table ================================================== ========================= Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.14 20 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 192.168.1.0 255.255.255.0 On-link 192.168.1.14 276 192.168.1.14 255.255.255.255 On-link 192.168.1.14 276 192.168.1.255 255.255.255.255 On-link 192.168.1.14 276 192.168.56.0 255.255.255.0 On-link 192.168.56.1 266 192.168.56.1 255.255.255.255 On-link 192.168.56.1 266 192.168.56.255 255.255.255.255 On-link 192.168.56.1 266 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 192.168.56.1 266 224.0.0.0 240.0.0.0 On-link 192.168.1.14 276 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 192.168.56.1 266 255.255.255.255 255.255.255.255 On-link 192.168.1.14 276 ================================================== ========================= Persistent Routes: None I admit I was playing with the routing table, trying to learn it, but now the fun is over because I screwed up and just want to get back to 'normal'. Assuming a "normal" home setup, with a router at 192.168.1.1 and with the router handing out addresses dynamically, what *should* my "route print" look like and how do I get *back* to the defaults? |
Ads |
#2
|
|||
|
|||
How do I unscrew up the routing table?
harry newton wrote:
I admit I was playing with the routing table, trying to learn it, but now the fun is over because I screwed up and just want to get back to 'normal'. My network is "normal" in that: a. My router is 192.168.1.1 b. My desktop is 192.168.1.14 == it's dhcp but that's what it is below c. I know that 192.168.1.0 & 192.168.1.255 are "special" d. And that 127.0.0.1 is the "localhost" (and 127.0.0.0 must be "special") e. And that a netmask of 255's is all 1's (in binary) f. And that the "gateway" is just the "router" (of 192.168.1.1 below) g. And that 192.168.1.255 & 127.255.255.255 are "special" (somehow) h. And that 255.255.255.255 (not as a netmask) must also be "special" But ... what the heck are these numbers doing in the routing table below? A. 192.168.56.0 & 192.168.56.1 & 192.168.56.255 ? Virtual Box network. You must have VirtualBox installed. B. 224.0.0.0 ? Multicast https://en.wikipedia.org/wiki/Multicast_address C. 127.255.255.255.255 ? -- Take care, Jonathan ------------------- LITTLE WORKS STUDIO http://www.LittleWorksStudio.com |
#3
|
|||
|
|||
How do I unscrew up the routing table?
harry newton wrote:
I admit I was playing with the routing table, trying to learn it, but now the fun is over because I screwed up and just want to get back to 'normal'. Why not just reset the router to factory specs? Hold the reset button in while powering up. |
#4
|
|||
|
|||
How do I unscrew up the routing table?
harry newton wrote:
A. 192.168.56.0 & 192.168.56.1 & 192.168.56.255 ? didn't your "route.exe print" give a list of interfaces before the routing table(s)? B. 224.0.0.0 ? multicast C. 127.255.255.255.255 ? loopback look like and how do I get *back* to the defaults? netsh.exe int ip reset then reboot |
#5
|
|||
|
|||
How do I unscrew up the routing table?
He who is Andy Burns said on Tue, 31 Oct 2017 21:01:44 +0000:
A. 192.168.56.0 & 192.168.56.1 & 192.168.56.255 ? didn't your "route.exe print" give a list of interfaces before the routing table(s)? Yes. But there is no reference in that list of interfaces to the IP addresses, so, until Jonathan N. Little mentioned that "A" was due to the VirtualBox software, I had not made any connection between: A. [192.168.56.0 & 192.168.56.1 & 192.168.56.255] & [VirtualBox] Here's that list of interfaces: route print ================================================== ========================= Interface List 8...0a 00 27 00 00 08 ......VirtualBox Host-Only Ethernet Adapter 11...00 26 55 53 28 ba ......Realtek PCIe GBE Family Controller 10...00 ff 84 f5 2c ec ......TAP-Windows Adapter V9 1...........................Software Loopback Interface 1 20...00 00 00 00 00 00 00 e0 Microsoft Teredo Tunneling Adapter 18...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2 16...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3 ================================================== ========================= B. 224.0.0.0 ? multicast C. 127.255.255.255.255 ? loopback Thanks. I don't completely understand them both (loopback & multicast) but they seem to be "normal" so I will ignore them for now because I'm looking for abnormal stuff as all I want to get back to is where you guys are normally (where I already deleted a dozen routes). look like and how do I get *back* to the defaults? netsh.exe int ip reset then reboot THANK YOU for that very nice command to reset my routing table back to "normal". I will try it after I send this post. Looking up the command just to be sure it doesn't do an "rm *" on me... netsh int ? (lists 13 "interface" command options) netsh int ip ? (lists 10 "ip" command options) netsh int ip reset ? (lists 1 result of "reset the IP configurations") Usage: reset Parameters: none Remarks: Removes all user configured settings. Restarting computer is required before the default settings to be effect. Before I "reset the ip configurations" & reboot, here's the output which for the first time shows the relationship between the VirtualBox and the IP address that Jonathan N. Little astutely pointed out to me earlier: Bear in mind that there is *no router* involved in this setup. I removed the router. And I added a second rooftop radio so that this setup is completly independent of my normal home network. For simplicity, this setup only has two components. 1. My rooftop radio (most of you might call it a "modem" but I'm on WISP) 2. My desktop computer (which is set to the static IP address 10.50.0.100) There's *nothing* else in the network at the moment. netsh int ip show route Publish Type Met Prefix Idx Gateway/Interface Name ------- -------- --- ------------------------ --- ------------------------ No Manual 256 0.0.0.0/0 11 10.50.0.1 No System 256 10.50.0.0/24 11 Local Area Connection No System 256 10.50.0.100/32 11 Local Area Connection No System 256 10.50.0.255/32 11 Local Area Connection No System 256 127.0.0.0/8 1 Loopback Pseudo-Interface 1 No System 256 127.0.0.1/32 1 Loopback Pseudo-Interface 1 No System 256 127.255.255.255/32 1 Loopback Pseudo-Interface 1 No System 256 192.168.56.0/24 8 VirtualBox Host-Only Network No System 256 192.168.56.1/32 8 VirtualBox Host-Only Network No System 256 192.168.56.255/32 8 VirtualBox Host-Only Network No System 256 224.0.0.0/4 1 Loopback Pseudo-Interface 1 No System 256 224.0.0.0/4 8 VirtualBox Host-Only Network No System 256 224.0.0.0/4 10 Ethernet No System 256 224.0.0.0/4 11 Local Area Connection No System 256 255.255.255.255/32 1 Loopback Pseudo-Interface 1 No System 256 255.255.255.255/32 8 VirtualBox Host-Only Network No System 256 255.255.255.255/32 10 Ethernet No System 256 255.255.255.255/32 11 Local Area Connection This is a *great* command to see the *relationship* between the IP address and the interface adapter! |
#6
|
|||
|
|||
How do I unscrew up the routing table?
He who is BurfordTJustice said on Tue, 31 Oct 2017 16:29:37 -0400:
You apparently have too much time on your hands.. All I really want to know is whether my routing table is *normal* for a Windows 10 desktop. As an experiment, I *removed* the router completely from the equation. In doing so, I set my desktop to a static IP address of 10.50.0.100, and I disconnected the *router* completely, so there is no router. It's just my computer and what you'd call a "modem" (but in my case, it's not a modem but a transceiver, which is effectively the same thing from your standpoint). C:\ route print IPv4 Route Table ================================================== ========================= Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 10.50.0.1 10.50.0.100 276 10.50.0.0 255.255.255.0 On-link 10.50.0.100 276 10.50.0.100 255.255.255.255 On-link 10.50.0.100 276 10.50.0.255 255.255.255.255 On-link 10.50.0.100 276 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 192.168.56.0 255.255.255.0 On-link 192.168.56.1 266 192.168.56.1 255.255.255.255 On-link 192.168.56.1 266 192.168.56.255 255.255.255.255 On-link 192.168.56.1 266 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 192.168.56.1 266 224.0.0.0 240.0.0.0 On-link 10.50.0.100 276 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 192.168.56.1 266 255.255.255.255 255.255.255.255 On-link 10.50.0.100 276 ================================================== ========================= Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 10.50.0.1 Default ================================================== ========================= Does your Win10 route print look that mine above? (Note that I do have VirtualBox running, which I think I'll remove.) |
#7
|
|||
|
|||
How do I unscrew up the routing table?
He who is Paul in Houston TX said on Tue, 31 Oct 2017 14:50:15 -0500:
I admit I was playing with the routing table, trying to learn it, but now the fun is over because I screwed up and just want to get back to 'normal'. Why not just reset the router to factory specs? Hold the reset button in while powering up. I'm confused by the routing table, but even more confused by what you just wrote about the *router*. Does the SOHO router have *anything* to do with the Windows 10 desktop routing table other than to assign a single IP address to the Windows 10 desktop? Isn't the *rest* of the routing table (other than that one line), created and maintained by Windows herself? Anyway, to completely *remove* the router from the equation, I set up a network to my ISP that is completely separate, so it's now just my Windows 10 desktop tied to the transceiver (it's what you'd call a modem but it's different in that it's a transceiver). The routing table was *still* immensely complex with no router in the equation. Does your route print look like mine? C:\ route print IPv4 Route Table ================================================== ========================= Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 10.50.0.1 10.50.0.100 276 10.50.0.0 255.255.255.0 On-link 10.50.0.100 276 10.50.0.100 255.255.255.255 On-link 10.50.0.100 276 10.50.0.255 255.255.255.255 On-link 10.50.0.100 276 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 192.168.56.0 255.255.255.0 On-link 192.168.56.1 266 192.168.56.1 255.255.255.255 On-link 192.168.56.1 266 192.168.56.255 255.255.255.255 On-link 192.168.56.1 266 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 192.168.56.1 266 224.0.0.0 240.0.0.0 On-link 10.50.0.100 276 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 192.168.56.1 266 255.255.255.255 255.255.255.255 On-link 10.50.0.100 276 ================================================== ========================= Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 10.50.0.1 Default ================================================== ========================= |
#8
|
|||
|
|||
How do I unscrew up the routing table?
He who is Jonathan N. Little said on Tue, 31 Oct 2017 14:56:04 -0400:
A. 192.168.56.0 & 192.168.56.1 & 192.168.56.255 ? Virtual Box network. You must have VirtualBox installed. How you knew that is beyond me, but you are correct, VirtualBox is installed. So that's part of my confusion. Thanks. B. 224.0.0.0 ? Multicast https://en.wikipedia.org/wiki/Multicast_address I don't understand that wikipedia page, but it does say they're local network not routable addresses, so I'll just ignore them as long as they're something that *everyone* has in their routing table and not just me. C. 127.255.255.255.255 ? Is this half the Internet? |
#9
|
|||
|
|||
How do I unscrew up the routing table?
harry newton wrote:
He who is Jonathan N. Little said on Tue, 31 Oct 2017 14:56:04 -0400: A. 192.168.56.0 & 192.168.56.1 & 192.168.56.255 ? Virtual Box network. You must have VirtualBox installed. How you knew that is beyond me, but you are correct, VirtualBox is installed. So that's part of my confusion. Thanks. Not a crystal ball, just know that 192.168.56.0 is VirtualBox's default network and I also use VirtualBox. ;-) -- Take care, Jonathan ------------------- LITTLE WORKS STUDIO http://www.LittleWorksStudio.com |
#10
|
|||
|
|||
How do I unscrew up the routing table?
harry newton wrote:
He who is Paul in Houston TX said on Tue, 31 Oct 2017 14:50:15 -0500: I admit I was playing with the routing table, trying to learn it, but now the fun is over because I screwed up and just want to get back to 'normal'. Why not just reset the router to factory specs? Hold the reset button in while powering up. I'm confused by the routing table, but even more confused by what you just wrote about the *router*. Does the SOHO router have *anything* to do with the Windows 10 desktop routing table other than to assign a single IP address to the Windows 10 desktop? Isn't the *rest* of the routing table (other than that one line), created and maintained by Windows herself? Anyway, to completely *remove* the router from the equation, I set up a network to my ISP that is completely separate, so it's now just my Windows 10 desktop tied to the transceiver (it's what you'd call a modem but it's different in that it's a transceiver). The routing table was *still* immensely complex with no router in the equation. Does your route print look like mine? C:\ route print IPv4 Route Table ================================================== ========================= Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 10.50.0.1 10.50.0.100 276 10.50.0.0 255.255.255.0 On-link 10.50.0.100 276 10.50.0.100 255.255.255.255 On-link 10.50.0.100 276 10.50.0.255 255.255.255.255 On-link 10.50.0.100 276 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 192.168.56.0 255.255.255.0 On-link 192.168.56.1 266 192.168.56.1 255.255.255.255 On-link 192.168.56.1 266 192.168.56.255 255.255.255.255 On-link 192.168.56.1 266 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 192.168.56.1 266 224.0.0.0 240.0.0.0 On-link 10.50.0.100 276 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 192.168.56.1 266 255.255.255.255 255.255.255.255 On-link 10.50.0.100 276 ================================================== ========================= Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 10.50.0.1 Default ================================================== ========================= You are correct. I was thinking of something else entirely. Sorry for the confusion. |
#11
|
|||
|
|||
How do I unscrew up the routing table?
He who is harry newton said on Wed, 1 Nov 2017 01:03:35 +0000 (UTC):
This is a *great* command to see the *relationship* between the IP address and the interface adapter! In an "admin" shell, I ran: netsh.exe int ip reset Resetting Global, OK! Resetting Interface, OK! Resetting Unicast Address, OK! Resetting Neighbor, OK! Resetting Path, OK! Resetting Route, OK! Resetting , failed. Access is denied. Resetting , OK! Restart the computer to complete this action. shutdown /r When it rebooted, I ran the route print again: route print route print ================================================== ========================= Active Routes: Network Destination Netmask Gateway Interface Metric 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 169.254.0.0 255.255.0.0 On-link 169.254.176.96 266 169.254.0.0 255.255.0.0 On-link 169.254.178.56 276 169.254.176.96 255.255.255.255 On-link 169.254.176.96 266 169.254.178.56 255.255.255.255 On-link 169.254.178.56 276 169.254.255.255 255.255.255.255 On-link 169.254.176.96 266 169.254.255.255 255.255.255.255 On-link 169.254.178.56 276 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 169.254.176.96 266 224.0.0.0 240.0.0.0 On-link 169.254.178.56 276 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 169.254.176.96 266 255.255.255.255 255.255.255.255 On-link 169.254.178.56 276 ================================================== ========================= Persistent Routes: None netsh int ip show route Publish Type Met Prefix Idx Gateway/Interface Name ------- -------- --- ------------------------ --- ------------------------ No System 256 127.0.0.0/8 1 Loopback Pseudo-Interface 1 No System 256 127.0.0.1/32 1 Loopback Pseudo-Interface 1 No System 256 127.255.255.255/32 1 Loopback Pseudo-Interface 1 No System 256 169.254.0.0/16 8 VirtualBox Host-Only Network No System 256 169.254.0.0/16 11 Local Area Connection No System 256 169.254.176.96/32 8 VirtualBox Host-Only Network No System 256 169.254.178.56/32 11 Local Area Connection No System 256 169.254.255.255/32 8 VirtualBox Host-Only Network No System 256 169.254.255.255/32 11 Local Area Connection No System 256 224.0.0.0/4 1 Loopback Pseudo-Interface 1 No System 256 224.0.0.0/4 8 VirtualBox Host-Only Network No System 256 224.0.0.0/4 10 Ethernet No System 256 224.0.0.0/4 11 Local Area Connection No System 256 255.255.255.255/32 1 Loopback Pseudo-Interface 1 No System 256 255.255.255.255/32 8 VirtualBox Host-Only Network No System 256 255.255.255.255/32 10 Ethernet No System 256 255.255.255.255/32 11 Local Area Connection So I guess all *that* stuff is normal. Of course, until and unless I set my desktop to the same 10.0.50.x subnet as my "modem" (actgually it's a transceiver), I wasn't on the net. But I guess this solves the problem of resetting the desktop back to normal. Thanks. |
#12
|
|||
|
|||
How do I unscrew up the routing table?
He who is Jonathan N. Little said on Tue, 31 Oct 2017 21:54:09 -0400:
Not a crystal ball, just know that 192.168.56.0 is VirtualBox's default network and I also use VirtualBox. ;-) Thanks for putting two and two together because I didn't know that VirtualBox was there until you said so. The later command from Andy Burns puts the two together though: netsh int ip show route After setting my IP address on the desktop to a static 10.50.0.100, that command reports the relationship between IP and adapter: netsh int ip show route Publish Type Met Prefix Idx Gateway/Interface Name ------- -------- --- ------------------------ --- ------------------------ No Manual 256 0.0.0.0/0 11 10.50.0.1 No System 256 10.50.0.0/24 11 Local Area Connection No System 256 10.50.0.100/32 11 Local Area Connection No System 256 10.50.0.255/32 11 Local Area Connection No System 256 127.0.0.0/8 1 Loopback Pseudo-Interface 1 No System 256 127.0.0.1/32 1 Loopback Pseudo-Interface 1 No System 256 127.255.255.255/32 1 Loopback Pseudo-Interface 1 No System 256 169.254.0.0/16 8 VirtualBox Host-Only Network No System 256 169.254.176.96/32 8 VirtualBox Host-Only Network No System 256 169.254.255.255/32 8 VirtualBox Host-Only Network No System 256 224.0.0.0/4 1 Loopback Pseudo-Interface 1 No System 256 224.0.0.0/4 8 VirtualBox Host-Only Network No System 256 224.0.0.0/4 10 Ethernet No System 256 224.0.0.0/4 11 Local Area Connection No System 256 255.255.255.255/32 1 Loopback Pseudo-Interface 1 No System 256 255.255.255.255/32 8 VirtualBox Host-Only Network No System 256 255.255.255.255/32 10 Ethernet No System 256 255.255.255.255/32 11 Local Area Connection In this situation, there are only two devices on the network. 1. The desktop computer at 10.50.0.100 2. The "modem" (which for me is a rooftop radio) at a gateway of 10.50.0.1 |
#13
|
|||
|
|||
How do I unscrew up the routing table?
He who is Paul in Houston TX said on Tue, 31 Oct 2017 21:02:09 -0500:
You are correct. I was thinking of something else entirely. Sorry for the confusion. Well, thanks to your suggestion, I *removed* the router completely from the equation by setting up a second rooftop radio (let's call it a "modem" for now). With this second "modem", I was able to set up a completely separate network from my normal home network. The home network has a router but this separate network has just the desktop computer and the "modem" and that's it. The routing table was still pretty complex, but the command from Andy Burns along with the hints from you and Jonathan goes a long way toward *explaining* why there are so many strange lines. This is a *great* command for tying together the IP address and the interface, where the "route print" command doesn't do that directly. netsh int ip show route And this is a great command for resetting everything back to defaults: netsh int ip reset Thanks! |
#14
|
|||
|
|||
How do I unscrew up the routing table?
harry newton wrote:
Bear in mind that there is *no router* involved in this setup. Well 10.50.0.1 *is* you default gateway, if that wasn't acting as a router you wouldn't have internet connectivity. This is a *great* command to see the *relationship* between the IP address and the interface adapter! This powershell command will show you all IP addresses to do with all interfaces and their status, paste it into a powershell window get-netIpAddress | format-table -property * My own script based on that command filters the list down to IPv4 addresses, excludes interfaces that windows won't make use of, and uses CIDR notation. It shouldn't mind being pasted into a powershell window with the line-breaks as they are below get-netIpAddress -addressState preferred -addressFamily ipv4 | format-table -property interfaceAlias, prefixOrigin, @{ label="ipAddress"; expression={ $_.ipAddress + "/" + $_.prefixLength} } You could save that as a handy .ps1 script, but to run it you'll need to jigger about with your powershell execution policy. https://blog.netspi.com/15-ways-to-bypass-the-powershell-execution-policy |
#15
|
|||
|
|||
How do I unscrew up the routing table?
harry newton wrote:
C. 127.255.255.255.255 ? Is this half the Internet? No 1/256th, it is an address (ignoring the spurious 5th octet), not a mask. |
|
Thread Tools | |
Display Modes | Rate This Thread |
|
|