[prev in list] [next in list] [prev in thread] [next in thread]
List: systalk
Subject: [Systalk]Re: test ... ingnore ... test
From: "GK64 () aol ! com" <GK64 () https2 ! mine ! nu>
Date: 2001-02-23 12:50:22
[Download RAW message or body]
----- Original Message -----
From: GK64@https2.mine.nu
To: SYSTALK@DHS.ORG
Sent: Tuesday, February 27, 2001 8:44 AM
Subject: Fw: test ... ingnore ... test
----- Original Message -----
From: GK64
To: systalk@dhs.org
Sent: Tuesday, February 27, 2001 8:38 AM
Subject: test ... ingnore ... test
if you dont segment your phys nets.
every cruft must has its routing tables manualy set.
Because default behavior for IP is
dest-IP in same segment ?(compare MASK with dest IP)
yes->ARP (BROADCAST - will not route) get phys MAC addr for IP
----- ok->deliver
no->ARP(BROADCAST) default GATEWAY getphys MAC addr
----- ok->Gataway gets the packet hopfully he can deliver
so if i.e 192.168.0.4 is on different phys segment than your
192.168.0.2
default routing from 192.168.0.4 can not reach 192.168.0.2
the solution is. you must add manual added route to it
for every machine in your privat network.
i.e on the 192.168.0.4 : route add 192.168.0.2 mask 255.255.255.255 192.168.0.3
on the 192.168.0.2 : route add 192.168.0.4 mask 255.255.255.255 192.168.0.1
But if your phys segments are logical (by IP) separatet,
Default routing will deliver. So you have not to worry and
mantain routing tables. Wich can be very large if your Network grows.
so every phys node should be a 192.168.x.0/24 net
GK64... GertK...
[Attachment #3 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.60.2296.0" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 \
2px solid; MARGIN-RIGHT: 0px"> <DIV style="FONT: 10pt arial">----- Original Message \
----- </DIV> <DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=GK64@https2.mine.nu
href="mailto:GK64@https2.mine.nu">GK64@https2.mine.nu</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=SYSTALK@DHS.ORG
href="mailto:SYSTALK@DHS.ORG">SYSTALK@DHS.ORG</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, February 27, 2001 8:44
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Fw: test ... ingnore ...
test</DIV>
<DIV><BR></DIV>
<DIV> </DIV>
<DIV style="FONT: 10pt arial">----- Original Message -----
<DIV style="BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> <A
title=GK64@64GK.GK href="mailto:GK64@64GK.GK">GK64</A> </DIV>
<DIV><B>To:</B> <A title=systalk@dhs.org
href="mailto:systalk@dhs.org">systalk@dhs.org</A> </DIV>
<DIV><B>Sent:</B> Tuesday, February 27, 2001 8:38 AM</DIV>
<DIV><B>Subject:</B> test ... ingnore ... test</DIV></DIV>
<DIV><BR></DIV>
<DIV><FONT face=Arial size=2>if you dont segment your phys nets.</FONT></DIV>
<DIV><FONT face=Arial size=2>every cruft must has its routing tables manualy
set.</FONT></DIV>
<DIV><FONT face=Arial size=2>Because default behavior for IP
is </FONT></DIV>
<DIV><FONT face=Arial size=2>dest-IP in same segment ?(</FONT><FONT face=Arial
size=2>compare MASK with dest IP)</FONT></DIV>
<DIV><FONT face=Arial size=2>yes->ARP (BROADCAST - will not route) get phys
MAC addr for IP</FONT></DIV>
<DIV><FONT face=Arial size=2> ----- ok->deliver</FONT></DIV>
<DIV><FONT face=Arial size=2>no->ARP(BROADCAST) default GATEWAY
getphys MAC addr </FONT></DIV>
<DIV><FONT face=Arial size=2> ----- ok->Gataway gets the
packet hopfully he can deliver</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>so if i.e 192.168.0.4 is on different phys
segment than your</FONT></DIV>
<DIV><FONT face=Arial size=2>192.168.0.2</FONT></DIV>
<DIV><FONT face=Arial size=2>default routing from 192.168.0.4 can not reach
192.168.0.2</FONT></DIV>
<DIV><FONT face=Arial size=2>the solution is. you must add manual added
route to it</FONT></DIV>
<DIV><FONT face=Arial size=2>for every machine in your privat
network.</FONT></DIV>
<DIV><FONT face=Arial size=2>i.e on the 192.168.0.4 : route add 192.168.0.2
mask 255.255.255.255 192.168.0.3</FONT></DIV>
<DIV><FONT face=Arial size=2>on the 192.168.0.2 : route add 192.168.0.4 mask
255.255.255.255 192.168.0.1</FONT> </DIV>
<DIV><FONT face=Arial size=2>But if your phys segments are logical (by
IP) separatet,</FONT></DIV>
<DIV><FONT face=Arial size=2>Default routing will deliver. So you have not to
worry and</FONT></DIV>
<DIV><FONT face=Arial size=2>mantain routing tables. Wich can be very large if
your Network grows.</FONT></DIV>
<DIV><FONT face=Arial size=2>so every phys node should be
a 192.168.x.0/24 net</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV> <FONT face=Arial size=2>GK64...
GertK...</FONT></DIV></BLOCKQUOTE></BODY></HTML>
_______________________________________________
DHS Systalk Discussion List Systalk@dhs.org
To manage your subscription, please goto:
http://www.dhs.org/mailman/listinfo/systalk
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic