neighbor discovery problem
mat at FreeBSD.org
Tue Aug 12 12:11:43 UTC 2008
+-le 12.08.2008 12:50:35 +0100, Pete French a dit :
|> Hum, 2a01:678:1:443::443 is a /64, and 2a01:678:100:2:: is on a /48, both
|> have the "same" gateway, that is, the same box, which has :
|> inet6 2a01:678:1:443:: prefixlen 64
|> inet6 2a01:678:100:: prefixlen 48
| O.K., that should work. My best advice here is to do what I did - which is
| to disable 'pf' entirely and see if it works then. When it does you know
| the IPv6 config is correct and can then work out which rule in 'pf' is
| stopping it working when enabled. Sorry, but I van't think of anything else
| right now, and I guess that may not be an option on a production machine.
Well, stopping the firewall a few seconds can't do really bad things, and,
well, pfctl -d, wait a bit, try again, still no luck...
The network is pretty simple,
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::207:e9ff:fe0e:dead%em0 prefixlen 64 scopeid 0x1
inet6 2a01:678:1:443:: prefixlen 64
inet6 2a01:678:100:: prefixlen 48
first machine :
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
inet6 fe80::2d0:dead:beef:cafe%bridge0 prefixlen 64 scopeid 0x4
inet6 2a01:678:1:443::443 prefixlen 64
destination machine :
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::2b0:d0ff:fee1:c05f%fxp0 prefixlen 64 scopeid 0x1
inet6 2a01:678:100:2:: prefixlen 48
All three ports on a switch.
I don't believe it's a problem in if_bridge(4) because it's the same if I try
from outside my network.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20080812/cab7f083/attachment.pgp
More information about the freebsd-stable