Hello, I've been googling around for an answer to this, and even resorted to reading the FAQ :) without really finding the answer I want. I have recently started using aiccu with an ayiya tunnel on a laptop, with IPv6 connectivity everywhere I go as a goal. However, I often use a wireless network where most ports are blocked, so this did not work as well as I hoped for. I have read the FAQ and do understand that aiccu is deliberately designed to allow blocking by a local policy. So if I can't get the network adminstrators to open ports 3874/tcp and 5072/udp then my tunnel will not work. That's OK. I can live with it. But the problem I'm facing is that aiccu never tear down or disably the tunnel, even if it is blocked for a long time. This effectively creates an IPv6 blackhole. The typical situation is - aiccu is started on a net where ports 3874/tcp and 5072/udp are open and the tunnel comes up just fine - the laptop is moved to another IPv4 net where it gets a new IPv4 address - ports 3874/tcp and 5072/udp are blocked so aiccu cannot update the tunnel - aiccu keeps the tunnel interface up, using the previuosly assigned IPv4 address as local address - since the tunnel interface is up, the default IPv6 route is also there, tricking applications into believing that they have IPv6 connectivity Result: A large black hole. Would it be possible to change aiccu into detecting this situation and either completely disable the tunnel or at least remove the default route when the POP is unreacheable? This illustrates the problem. aiccu is using non-existing local ipv4 address: This makes heartbeat fail, but aiccu does not seem to worry about the socket failure; I assume the failing heartbeat will properly disable the tunnel at the POP end, but I would have liked it to disable the tunnel at the local end too. Bjørn