[SunHELP] About route question (very interesting topic)

Wed Sep 5 11:53:45 CDT 2001

Sorry, but I don't have enough CPU cyles left in my old brain to scratch out
a decent answer for this odd behaviour. I can tell you with excellent
authority that the default gateway needs to be the address of the router for
that VLAN (not to brag, but I only admin as a sideline & hobby, I am
actually a network engineer by trade).

If you want to forward me a detailed network drawing that includes addresses
of major nodes (incl. netmask) and the configs of your switches/routers I
can definately produce a quick and accurate answer. But, please remember
that you will compromise security by releasing such information. If you
choose to take me up on my offer please as a minimum delete any SNMP
information (espcially community strings which are really a password) from
your configs.

Also remember that if you have static routes programmed into your equipment
that a default gateway is irrelavent. I never suggest static routes in
hosts, but someone may have done it. I **really** don't suggest it for Unix
hosts unless unavoidable. For the hell of it try a netstat -r on a Unix
machine and include that in the package. There is also an equivalent to
netstat -r for Windows.

What I'm getting at here, is that the anomoly rests in the Windows world,
not the Unix world. Another possiblity is that the network does not truly
use VLANs (you can get VLAN-like behaviour without having a true VLAN).

<having read reply more carefully> No, Windows is not VLAN-aware. No O/S
should *ever* be VLAN-aware, as it would break the reasons for having
VLAN's. VLAN's only exist in the network world. To the attached O/S, it
appears to have a LAN that is physically separate from the other LANs.

> -----Original Message-----
> From: John Lee [mailto:johnlee at sc.mcel.mot.com]
> Sent: Tuesday, September 04, 2001 9:48 PM
> To: sunhelp at sunhelp.org
> Subject: RE: [SunHELP] About route question (very interesting topic)
> 
> 
> Hi Fogg,
> 
> Thanks for your input.
> 
> Actually, I don't think my NT machine is broken because all 
> our more than
> 200 NT machines have the same case. This is an interesting 
> thing. Let me
> decribe it in detail.
> 
> On one subnet 200.10.2.x(mask is 255.255.255.0), If I set one 
> NT machine's
> default gateway as its IP(for example: 200.10.2.25), then run tracert
> command, the result will be as below:
> -----------------------------------------
> c:>tracert 200.2.1.27
> Tracing route to 200.2.1.27 over a maximum of 30 hops
> 1    <10ms    <10ms    <10ms    200.3.1.254
> 2    <10ms    <10ms    <10ms    200.2.1.27
> -----------------------------------------
> If I run traceroute command  on a solaris machine with 
> IP=200.10.2.26, the
> result will be:
> -----------------------------------------
> %traceroute 200.2.1.27
> traceroute to 200.2.1.27 (200.2.1.27), 30 hops max, 40 byte packets
> 1    200.10.2.254(200.10.2.254)     0.397 ms  0.361 ms  0.322 ms
> 2    200.4.3.254(200.4.3.254) 0.514 ms *  0.499 ms
> 3    200.2.1.27(200.2.1.27)     4.116 ms *  3.323 ms
> ----------------------------------------
> 
> From above, We can see NT machine's IP traffic route is different with
> Solaris machine. What I want to do is let Solaris machine go 
> through the
> same route as NT machine. I don't know how to do. It seems 
> that NT machine
> is VLAN aware, but Solaris isn't.
> 
> By the way, Many of my colleagues think it is strange thing. 
> But it is true
> and I have tested on serveral subnets. Our network equiment 
> include Cisco
> and CableTron.
> 
> I think this is an interesting topic worth of discussing. I 
> don't know if I
> need install the third-party software on Solaris so that it 
> can be VLAN
> aware.
> 
> Thanks for all your input !
> 
> Best Regards
> John
> 
> 
> 
> 
> -----Original Message-----
> From: Fogg, James [mailto:JFogg at vicinity.com]
> Sent: Tuesday, September 04, 2001 9:16 PM
> To: 'sunhelp at sunhelp.org'
> Subject: RE: [SunHELP] About route question
> 
> 
> Your NT machine is actually broken. Its default gateway should be the
> gateway for the VLAN router. MS networking uses broadcast netbios
> annoucements to "find" each other and build the network browse lists.
> Because of this, the brokeness isn't apparent.
> 
> > -----Original Message-----
> > From: John Lee [mailto:johnlee at sc.mcel.mot.com]
> > Sent: Tuesday, September 04, 2001 2:50 AM
> > To: sunhelp at sunhelp.org
> > Subject: [SunHELP] About route question
> >
> >
> > Greetings Everyone,
> >
> > I encounted a route question and want to get help from you.
> >
> > We have a network with VLAN enabled. On this network, if one
> > NT machine have
> > its default gateway same IP address as its IP, it will have
> > no problem in
> > connection to other network nodes. But for a Solaris machine,
> > it can't.
> >
> > Can anyone advise me why ?
> >
> > Regards.
> > John
> >
> > _______________________________________________
> > SunHELP maillist  -  SunHELP at sunhelp.org
> > http://www.sunhelp.org/mailman/listinfo/sunhelp
> >
> _______________________________________________
> SunHELP maillist  -  SunHELP at sunhelp.org
> http://www.sunhelp.org/mailman/listinfo/sunhelp
> 
> 
> _______________________________________________
> SunHELP maillist  -  SunHELP at sunhelp.org
> http://www.sunhelp.org/mailman/listinfo/sunhelp
> 