On Thu, Nov 13, 2014, at 07:02 AM, Tom Eastep wrote:
> You have the same /64 routed out of both sit1 and eth0 -- that won't fly.
That has been that way -- apparently incorrectly -- for the longest time :-/
Testing on a couple of boxes with older os (opensuse <= 13.1), no problems.
After os upgrade (to 13.2), with of the expected slew of packages upgraded, as
well as mv to most recent shorewall pkgs, this issue crops up.
Fixed, so that instead of
shorewall6-lite show routing | egrep "^2001|^default"
2001:XXX:XXX5:XXX::/64 dev eth1 proto kernel metric 256
2001:XXX:XXX4:XXX::/64 dev sit1 proto kernel metric 256
2001:XXX:XXX4:XXX::/64 dev eth0 proto kernel metric 256
default via 2001:XXX:XXX4:XXX::1 dev sit1 metric 1024
I've now, correctly,
shorewall6-lite show routing | egrep "^2001|^default"
2001:XXX:XXX5:XXX::/64 dev eth1 proto kernel metric 256
2001:XXX:XXX4:XXX::/64 dev sit1 proto kernel metric 256
default via 2001:XXX:XXX4:XXX::1 dev sit1 metric 1024
And back in business
ping6 -c1 2001:XXX:XXX4:XXX::1
PING 2001:XXX:XXX4:XXX::1(2001:XXX:XXX4:XXX::1) 56 data bytes
64 bytes from 2001:XXX:XXX4:XXX::1: icmp_seq=1 ttl=64 time=154
ms
--- 2001:XXX:XXX4:XXX::1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 154.963/154.963/154.963/0.000 ms
On Thu, Nov 13, 2014, at 12:00 AM, Simon Hobson wrote:
> Just one of several areas where you need to unlearn what you learned about
> IPv4.
no kidding !
Thanks!
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
_______________________________________________
Shorewall-users mailing list
Shorewall-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shorewall-users
