t makes a
difference. To my knowledge its routing table is correct:
default 2a01:348:6:13a::1 UGSgif0
2a01:348:6:13a::1 link#6 UHLgif0
2a01:348:6:13a::2 link#6 UHL lo0
Am I missing something?
y are all destined for the bridge interface.)
--
Jay L. T. Cornwall
http://www.jcornwall.me.uk/
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
to route packets correctly across
those subnets. That may not be how it works in practice.
If it does not work, I would question why not. If it does work then I
would expect the same behaviour on each of a bridge's constituent
interfaces?
--
Jay L. T. Cornwall
http://www.jcornwall.
rver to the network gateway - previously
it was the .22 gateway - and now all of the LAN PCs can communicate
without additional routing information. Inter-subnet packets will bounce
off the FreeBSD server, rather than staying inside the L2 switch, but
that's OK.
--
Jay L. T. Cornwall
ht