Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - daviessm

Pages: [1]
1
Fixed it now...seems that destroying and re-adding the tunnel a couple of times seems to have cleared something out. Thanks for looking though :)

2
It's not, no - previously I was on an ADSL connection. Now I'm on a cable connection and the computer now connects directly to the cable modem and receives an IP address from it. Previously it was in the DMZ of my ADSL modem/router.

If anything this connection should have been simpler to set up!

3
Yes, sorry I should have mentioned that! The update page seemed to accept the new address and gave me some nice green text saying it was all ok.

4
Hi,

I've had a tunnel to HE which has been working fine since May last year. I've now moved house and am using a different ISP (Virgin cable in the UK) and the tunnel seems to have stopped working. It comes up alright but never receives any packets.

Can anyone help? Let me know what information you need and I'll provide it.

Thanks!

5
IPv6 on Linux & BSD & Mac / Re: problems after reboot
« on: August 03, 2008, 03:50:32 AM »
I got it fixed - I'd specified the endpoint of my SIT tunnel as my external IP instead of the local one in the DMZ that my external router rewrites packets with - so my server was sending them out with a different source address from what it was receiving them back with in the destination address field, and not understanding what to do with them.

6
IPv6 on Linux & BSD & Mac / Re: problems after reboot
« on: August 03, 2008, 02:13:06 AM »
Hi, even with both FORWARD and INPUT set with policy ACCEPT I'm still having the same problem..thanks though!

7
IPv6 on Linux & BSD & Mac / Re: problems after reboot
« on: August 02, 2008, 02:04:04 PM »
Just to add to this, ipv6 routing seems to be working - using tcpdump I can see that packets from my laptop are routed correctly down sit1 and responses (ping responses or connection handshakes) are correctly returning down it (viewed by a tcpdump on eth1) but the packets still seem to disappear after that and don't show up on the tcpdump on sit1!

I'm probably missing a sysctl setting or something (not IPv6 forwarding) but I have no idea which one!

Please help :) Thanks

8
IPv6 on Linux & BSD & Mac / problems after reboot [solved]
« on: July 30, 2008, 01:18:45 PM »
Hi, I've had a tunnel working for the past few months with no problems but the server rebooted due to a power outage yesterday and now I'm having a problem with the tunnel!

After a bit of sleuthing I've discovered that the SIT tunnel seems to work. By running wireshark I can see that when I send a ping packet, it leaves sit1 (my tunnel interface) and is then encapsulated in IPv4 and sent on to the remote host. I can then see the returning echo reply coming down my IPv4 eth1 - but the packet never shows up on sit1.

Since wireshark sees packets before they hit netfilter my first thought was that iptables was blocking the incoming protocol 41 packets but it's not. IPv4 and 6 forwarding are enabled in the kernel but there must be some setting I'm missing that causes the incoming packets to vanish after they're received on the IPv4 side!

Any help would be appreciated - I can provide configs and anything, just let me know what you need! :)

Thanks for any help,
Steve

Pages: [1]