Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 11 May 2001 18:02:20 -0400
From:      "Louis A. Mamakos" <louie@TransSys.COM>
To:        Jun-ichiro itojun Hagino <itojun@iijlab.net>
Cc:        Nick Rogness <nick@rogness.net>, freebsd-net@FreeBSD.ORG
Subject:   Re: gif tunnel woes 
Message-ID:  <200105112202.f4BM2K256031@whizzo.transsys.com>
In-Reply-To: Your message of "Sat, 12 May 2001 05:16:27 %2B0900." <20010511201628.133D47D4@starfruit.itojun.org> 
References:  <Pine.BSF.4.21.0104290302520.70248-100000@cody.jharris.com> <20010511201628.133D47D4@starfruit.itojun.org> 

next in thread | previous in thread | raw e-mail | index | archive | help
> 
> 	my preference is to dropp support for multi-destination mode from
> 	gif(4), as the multi-destination behavior is violating network layering
> 	(rt_gateway is in inner header, and gif(4) multi-destination mode
> 	uses it to determinte outer header).

There's certainly a bunch of NBMA network media out there.  The problem is
abusing the routing table next hop as a way to specify the remote 
tunnel endpoint.  This should be an attribute of the gif interface,
configured outside of the routing infrastructure.  Or, perhaps treated
like ARP for ethernet; it's just an accident that the "MAC" address for
a multi-point NBMA tunnel is an IPv4/IPv6 address.

louie


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200105112202.f4BM2K256031>