Oh yes. Sorry I didn't mention that it works now. I switched back to the "good old way" and this works far better than the new way.

Hm... Ok thanks. I'll try that. Then I didn't really understand the news about the new method for dynamic endpoint updates.

Hm. Does anyone have an advice on this?

Hi,

I have an issue with the update of the dynamic endpoints. When I use https://<USERNAME>:<PASSWORD>@ipv4.tunnelbroker.net/nic/update?hostname=<TUNNEL_ID> it will give me "badip". I always have to specify a valid IP Address. Is there another way to update the endpoint?

Thanks.

A tunnel server in Hamburg would be really cool

Ok I just tested it. Proto 41 is passing freely and I have noticed that the problems begin at a specific time. From about 18:00 (UTC) onwards the connection is being reset nearly every hour. Before that time everything seems to work fine.

I have just installed a new kernel on my home computer. Maybe it is the tunnel on my local side which isn't working well as I had kernel 3.0 RC5 before.

I can't test it right now however do you know which ports have to be opened for a working tunnel?

Since tserv6.fra1 was down and I got my tunnel set up again I'm experiencing very strange problems. My IPv6 connect is experiencing a reset about every hour. On my server I'm running shorewall and I have defined the connect to tserv6.fra1 as a tunnel.

Does anyone have a hint what could cause these problems?

Fixed it: It was my IPv6 privacy extension -.-

Got it running now. For some reason some necessary rules in my shorewall configuration have disappeared.

I've had a look at my configuration. It looks good for me. I can ping the IPv4 of the tunnel server however I can't reach the IPv6. May I send you my configuration?

Will you post any news here on this issue? Currently I still can't get a connect.