ipv6 and freebsd

[gahn]

Thanks Steve:

We use fec0::... as global unique IPv6 address in the lab environment. the IPv6 routers in our lab uses fec0:0:5::/64 with eui-64 addressing scheme (for testing).

>From the host "lab" (freebsd) machine, it clearly sees two link-local addresses for two IPv6 routers via RA messages. the IP routers also sent But why not the host "lab" configure itself with global unique address with prefix fec0:0:5:0::/64 (provided by the routers)?

What shall I do to accomplish this on FreeBSD?



--- On Thu, 2/12/09, Steve Bertrand <steve at ibctech.ca> wrote:

> From: Steve Bertrand <steve at ibctech.ca>
> Subject: Re: ipv6 and freebsd
> To: ipfreak at yahoo.com
> Cc: "freebsd general questions" <freebsd-questions at freebsd.org>
> Date: Thursday, February 12, 2009, 6:20 AM
> gahn wrote:
> > Thanks Steve:
> > 
> > the router that sending RA is juniper and the protocol
> router-advertisement has been activated:
> > 
> > ga at lab_1> show interfaces fe-0/0/3
> > ...
> > 
> >   Logical interface fe-0/0/3.170 (Index 70) (SNMP
> ifIndex 59) 
> > ...
> >       Addresses, Flags: Is-Preferred
> >         Destination: fe80::/64, Local:
> fe80::214:f600:aa2c:d403
> >       Addresses, Flags: Is-Preferred Is-Primary
> >         Destination: fec0:10:5::/64, Local:
> fec0:10:5:0:214:f600:aa2c:d403
> 
> fec0::/10 was deprecated per RFC3879. Perhaps the Juniper
> unit is
> obeying this and just not sending the prefix in the
> advertisement?
> 
> Everything else looks good, so lets test that possibility
> (as remote as
> it is). Take your tcpdump one step further:
> 
> > lab# tcpdump -n -i bge1 ip6
> > tcpdump: verbose output suppressed, use -v or -vv for
> full protocol decode
> > listening on bge1, link-type EN10MB (Ethernet),
> capture size 96 bytes
> > 17:55:44.027565 IP6 fe80::214:f600:aa2c:3c03 >
> ff02::1: ICMP6, router advertisement, length 24
> > 18:02:46.283353 IP6 fe80::214:f600:aa2c:d403 >
> ff02::1: ICMP6, router advertisement, length 24
> 
> # tcpdump -n -i bge1 -s 0 -w /path/to/file.pcap ip6
> 
> After a time of that running (there won't be any STDOUT
> output), stop
> the capture, and open the file in Wireshark. (I've
> never figured out
> how to get tcpdump to read the data portion of the packets
> from a file).
> 
> With the -s0, it will capture the headers and the data of
> each packet,
> so you should be able to tell whether the RA announcements
> do actually
> contain the prefix you are trying to get configured.
> 
> Something that I should have asked from the get-go...do you
> have any
> sort of firewall running on the box?
> 
> I'll set this up in my lab here today. Although we
> don't have any
> Juniper units, I'll see if I can recreate the problem
> with Cisco
> hardware. You may also want to test using a non-deprecated
> address
> space. The documentation address may work for instance.
> 
> Steve
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe at freebsd.org"