<html>
I'm afraid that I've to bug you again :-) as I've no clue where to ask
questions about RAFIXD.<br><br>
When running it at home, it looks like Windows XP keeps the rogue RA in
memory and keeps using it...<br><br>
Note: as I'm running RAFIXD on Fedora rather than on *BSD, I had to
modify it to use PF_PACKET rather than BPF to send the RA with
lifetime=0...<br><br>
Note2: running TCPDUMP on another machine indicates that the fix RA is
sent from a MAC source address of all 0. Which is the expected behavior
when you look at the code. <br><br>
Note3: in my set-up, the rogue RA is sent by the one and only IPv6 router
of my network.<br><br>
For info, here is a TCPDUMP of the fix RA:<br>
<i>20:28:13.395158 <b><u>00:00:00:00:00:00 (oui Ethernet)</u></b> >
33:33:00:00:00:01 (oui Unknown), ethertype IPv6 (0x86dd), length 70:
(class 0x60, hlim 255, next-header: ICMPv6 (58), length: 16)
fe80::204:27ff:fefd:5240 > ip6-allnodes: [icmp6 sum ok] ICMP6, router
advertisement, length 16<br>
hop limit 0, Flags [none],
pref medium, router lifetime 0s, reachable time 0s, retrans time
0s<br><br>
</i>In short, it seems to me that there are 2 problems with RAFIXD:<br>
- does not work at least for Windows XP<br>
- the source MAC address is the null address<br><br>
Is the correct behavior of RAFIXD confirmed in real deployment?<br><br>
Thanks in advance for any piece of information<br><br>
-eric<br><br>
<br><br>
</html>