[6bone] .NET and ripng
Barker, Ron, vpe
Ron.Barker@v-pe.de
Tue, 10 Dec 2002 17:18:20 +0100
This is a multi-part message in MIME format.
------_=_NextPart_001_01C2A067.C1058187
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Has any one had in experience with using .NET as a Router. We are =
haveing a rough time! The set up consist of a CISCO 2500 advertising a =
sub net prefix. There are two routers attached to the et0
interface, one is a netbsdsand one is a .NET. Each router subsequently =
advertises subnets to other host.
The problem is that the nedbsd + any host on the subnet ( i.e., either a =
UNIX or .NET/XP ) behaves as expected. The host receives a prefix and =
default route from the router. However, the .NET / XP
used a router behaves in a totally different manner. =20
1. The .NET router receives the prefix and default route from the CISCO =
as expected, same as netbsd.
2. The .NET router does not provide the host on the next subnet with a =
default route, only a prefix.
3. The .NET + Host do not send RIP info hence the CISCO router has no =
route info.
4. Adding a static route does not seem to help
Any ideas.
Thanks
Ron
Dr. Ronald D. Barker
Vodafone Pilotentwicklung GmbH
Chiemgaustr. 116
D-81549 Munich
Germany
Fon +49 (89) 95 410 -0
Fax +49 (89) 95 410 -111
www.v-pe.de
------_=_NextPart_001_01C2A067.C1058187
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.6249.1">
<TITLE>.NET and ripng</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<BR>
<P><FONT SIZE=3D2 FACE=3D"Arial">Has any one had in experience with =
using .NET as a Router. We are haveing a rough time! The set =
up consist of a CISCO 2500 advertising a sub net prefix. There are =
two routers attached to the et0 interface, one is a netbsdsand one is a =
.NET. Each router subsequently advertises subnets to other =
host.</FONT></P>
<P><FONT SIZE=3D2 FACE=3D"Arial">The problem is that the nedbsd + any =
host on the subnet ( i.e., either a UNIX or .NET/XP ) behaves as =
expected. The host receives a prefix and default route from the =
router. However, the .NET / XP used a router behaves in a totally =
different manner. </FONT></P>
<P><FONT SIZE=3D2 FACE=3D"Arial">1. The .NET router receives the prefix =
and default route from the CISCO as expected, same as netbsd.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">2. The .NET router does not provide =
the host on the next subnet with a default route, only a prefix.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">3. The .NET + Host do not send RIP =
info hence the CISCO router has no route info.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">4. Adding a static route does =
not seem to help</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Arial">Any ideas.</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Arial">Thanks</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Ron</FONT>
</P>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<P><FONT SIZE=3D2 FACE=3D"Arial">Dr. Ronald D. Barker</FONT>
<BR><FONT SIZE=3D1 FACE=3D"Arial">Vodafone Pilotentwicklung GmbH</FONT>
<BR><FONT SIZE=3D1 FACE=3D"Arial">Chiemgaustr. 116</FONT>
<BR><FONT SIZE=3D1 FACE=3D"Arial">D-81549 Munich</FONT>
<BR><FONT SIZE=3D1 FACE=3D"Arial">Germany</FONT>
<BR><FONT SIZE=3D1 FACE=3D"Arial">Fon +49 (89) 95 410 -0</FONT>
<BR><FONT SIZE=3D1 FACE=3D"Arial">Fax +49 (89) 95 410 -111</FONT>
<BR><FONT COLOR=3D"#FF0000" SIZE=3D1 FACE=3D"Arial">www.v-pe.de</FONT>
</P>
<BR>
</BODY>
</HTML>
------_=_NextPart_001_01C2A067.C1058187--