Re: default route -print

From: chris@nospam.com
Date: 09/15/02


From: chris@nospam.com
Date: Sat, 14 Sep 2002 19:57:40 -0700


On Thu, 12 Sep 2002 09:50:49 -0600, "NeoSadist" <ne0$@d1$t> wrote:

>I recently performed a Route -Print at the prompt, and I was surprised at
>what I saw. Can someone tell me what the 0.0.0.0,127.0.0.0, 224.0.0.0, and
>255.255.255.255 entries are? Are they involved in some loop-back? I was
>wanting to know, because I'm about to tighten down my network
>drastically.....
>
>===========================================================================
>Interface List
>===========================================================================
>===========================================================================
>Active Routes:
>Network Destination Netmask Gateway Interface Metric
> 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.101 1
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
> 192.168.1.0 255.255.255.0 192.168.1.101 192.168.1.101 1
> 192.168.1.101 255.255.255.255 127.0.0.1 127.0.0.1 1
> 192.168.1.255 255.255.255.255 192.168.1.101 192.168.1.101 1
> 224.0.0.0 224.0.0.0 192.168.1.101 192.168.1.101 1
> 255.255.255.255 255.255.255.255 192.168.1.101 192.168.1.101 1
>Default Gateway: 192.168.1.1
>===========================================================================
>Persistent Routes:
> None

I hope you don't take offense, but you may not be the correct person
to 'tighten network security' if you don't understand route, ips and
subnet masks.

The route table tells the system, where to go when it needs to reach a
particular address. It matches against the destination and subnet
masks listed above. Some of the routes listed are redundant. In some
cases, the routes point at each other.

Going line-by line:

>0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.101 1

Default route or last resort. If nothing else matches, go to the
gateway.

> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1

Anything matching 127.x.x.x is a loopback, send it to the loopback
address.

> 192.168.1.0 255.255.255.0 192.168.1.101 192.168.1.101 1

192.168.1.x is local on the same subnet, send it out the 192.168.1.101
nic.

> 192.168.1.101 255.255.255.255 127.0.0.1 127.0.0.1 1

Thats the local adapter, send to loopback.

> 192.168.1.255 255.255.255.255 192.168.1.101 192.168.1.101 1

Local subnet broadcast address, send it out the 192.168.1.101

> 224.0.0.0 224.0.0.0 192.168.1.101 192.168.1.101 1

Multicast addresses which should be treated as local.

> 255.255.255.255 255.255.255.255 192.168.1.101 192.168.1.101 1

Broadcast address, send it out the 192.168.1.101

>Default Gateway: 192.168.1.1

obvious



Relevant Pages

  • Re: Help requested with RIPv1 lan issues (UK school)
    ... > school network. ... > RIP v1 request traffic from our clients that cause our normal client to ... Yet then you go on to discuss RIP, static routes on clients etc. ... You say you have static routes on the clients to the 192.168.2.x subnet. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Help requested with RIPv1 lan issues (UK school)
    ... > school network. ... > RIP v1 request traffic from our clients that cause our normal client to ... Yet then you go on to discuss RIP, static routes on clients etc. ... You say you have static routes on the clients to the 192.168.2.x subnet. ...
    (microsoft.public.windows.server.networking)
  • Re: Help requested with RIPv1 lan issues (UK school)
    ... >> school network. ... The event log on the clients indicate ... > Yet then you go on to discuss RIP, static routes on clients etc. ... > You say you have static routes on the clients to the 192.168.2.x subnet. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Help requested with RIPv1 lan issues (UK school)
    ... >> school network. ... The event log on the clients indicate ... > Yet then you go on to discuss RIP, static routes on clients etc. ... > You say you have static routes on the clients to the 192.168.2.x subnet. ...
    (microsoft.public.windows.server.networking)
  • Re: Routing problems
    ... >gateway set to Linux box) can ALWAYS access machines on the .4 subnet, ... >subnet unless they static routes on them to the .4 subnet. ... only hear packets directed to them). ... I changed its default gateway to the ...
    (comp.os.linux.networking)