Re: IPv6 Woes...
- From: "Bruce M. Simpson" <bms@xxxxxxxxxxx>
- Date: Mon, 25 Jun 2007 20:05:32 +0100
Is your routing table correct? My default route entry for IPv6 just looks like this:
default fe80::%gif0 UGS gif0
and gif0 just looks like this:
gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
tunnel inet a.b.c.d -> x.x.x.x
inet6 fe80::XXX:XXX:XXXX%gif0 prefixlen 64 scopeid 0x8
inet6 2001:ZZZ:ZZZ::ZZZZ:ZZZZ prefixlen 128
In the output you posted, the next-hop of 2001:4980:1::5 will need to be resolved via NDP (hence the LW flags).
You already have a 1:1 endpoint mapping due to the use of the gif IPIP header, so the upstream shouldn't need any other tag to demux your traffic. You shouldn't need to do anything special with Ethernet in your configuration.
Hope this helps.
BMS
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: IPv6 Woes...
- From: Eric F Crist
- Re: IPv6 Woes...
- References:
- IPv6 Woes...
- From: Eric F Crist
- IPv6 Woes...
- Prev by Date: Re: [6.x] problem with AIO, non-blocking sockets on freebSD and IE7 on windows.
- Next by Date: Re: [6.x] problem with AIO, non-blocking sockets on freebSD and IE7 on windows.
- Previous by thread: IPv6 Woes...
- Next by thread: Re: IPv6 Woes...
- Index(es):
Relevant Pages
|
