Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Pages: 1 ... 8 9 [10]
 91 
 on: July 08, 2019, 11:27:23 PM 
Started by dominix - Last post by snarked
Use the routed /64 reverse.  Example:

0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.4.0.0.0.d.0.0.0.0.7.4.0.1.0.0.2.ip6.arpa. 1d IN PTR snarked-1.subnet.ipv6.he.net.

 92 
 on: July 08, 2019, 05:10:19 PM 
Started by dominix - Last post by dominix
;; ANSWER SECTION:
2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.c.3.3.0.a.0.0.0.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN PTR tunnel61427-pt.tunnel.tserv14.sea1.ipv6.he.net.

how do I proceed ?

 93 
 on: July 08, 2019, 05:23:26 AM 
Started by tMHru - Last post by cholzhauer
You have to have a router somewhere...the thing that's hosting your IPv6 tunnel.

 94 
 on: July 06, 2019, 06:05:51 AM 
Started by tMHru - Last post by tMHru
Can the non-working computer ping the router ahead of it?

I have no router, but switch with 16 ports instead.

Yes, from 2nd host I can ping ipv6.google.com, I can ping :2 - remote gw of he.net, and I can ping 1st host ipv6 addresses, and vice versa - when I ping three v6 addresses on 2nd host from 1st host the pings passing ok.

Moreover, I did tests with IRC server connections, and this is what I received:
>irc *635 -h 2001:470:28:*::123 efnet.portlane.se
*** Connecting to port 6667 of server efnet.portlane.se
*** Couldn't bind to IRCHOST
[ Whois *635!*@tunnel*-pt.tunnel.tserv24.sto1.ipv6.he.net (Network) ]
-- I tried to connect with this ::123 host to efnet.portlane.se (v6 compatible server), but I get "Couldn't bind to IRCHOST" and then I get connection with default :2 host as you see, which is resolved.

Another test with standard telnet:
>telnet -b 2001:470:28:*::90 efnet.portlane.se 6667
Trying 2a00:1a28:1100:7::1337...
Connected to efnet.portlane.se.
Escape character is '^]'.
NOTICE AUTH :*** Processing connection to efnet.portlane.se
NOTICE AUTH :*** Looking up your hostname...
NOTICE AUTH :*** Checking Ident
NOTICE AUTH :*** Couldn't look up your hostname
NOTICE AUTH :*** Got Ident response
-- as you can notice - the connection passes ok, even irc server drop me notice about unresolved host which is :90 one.

At first I thought it was ircII (irc client) problem - but I compiled newest version and got the same "Couldn't bind to IRCHOST".

Any ideas? :) I still wonder - why 1st host have this "ip6tnl0" in ip list while 2nd host does not...

 95 
 on: July 05, 2019, 08:02:32 PM 
Started by tMHru - Last post by cholzhauer
Can the non-working computer ping the router ahead of it?

 96 
 on: July 05, 2019, 07:29:47 AM 
Started by tMHru - Last post by tMHru
Different versions of the “ip” program, or different OSs.

Both of them are " Linux Mint 17.3 Rosa", the first is armvl7 media player, the second 'usual computer' with core2duo.

Still I don't get why 2nd host (core2duo) cannot use assigned v6 addresses within my IP range of the tunnel - like this one -  2001:470:28:*::123

I see that tunnel is working:
64 bytes from 2001:470:27:*::1: icmp_seq=1 ttl=64 time=19.2 ms
64 bytes from 2001:470:27:*::1: icmp_seq=2 ttl=64 time=19.2 ms

I see that mine side :2 is visible to irc/web, but - other IPs are not, still...
what is this, can someone tell ?

BTW, I do not see no "ip6tnl0" mention on 2nd host "ip a"...might be this is the main problem ?

 97 
 on: July 04, 2019, 11:29:30 PM 
Started by alainj - Last post by alainj
If you're unable to ping your public IP address, that's your problem.

Thanks for your answer.
The issue is solved for me now.

What I had to do: change cable modem configuration from router to bridge.
Then the wan interface of my DD-WRT got the public IP (and was pingable from the outside).

So the conditions to create the tunnel were met and it is indeed created now.

Next step: add the correct configuration to the clients to be able to visit something like ipv6.google.com for testing purpose.

Thanks again!

Al

 98 
 on: July 04, 2019, 07:16:05 PM 
Started by alainj - Last post by cholzhauer
If you're unable to ping your public IP address, that's your problem.

If you have a firewall after your modem/router, look there.  You can contact your ISP and see if they block ICMP, if they don't, it's in DDWRT somewhere.

 99 
 on: July 04, 2019, 02:31:30 PM 
Started by alainj - Last post by alainj
Hi,

I'm afraid this is a classic question but I can't find my way through and maybe someone may help to solve the issue.

I try to create a first tunnel and get the message:
IP is not ICMP pingable. Please make sure ICMP is not blocked. If you are blocking ICMP, please allow 66.220.2.74 through your firewall.

My setup:
Linksys router with DD-WRT.

In the router firewall, the option "Block anonymous Wan requests (ping) is not checked. And to be absolutely sure, I also tried with no firewall at all.

I used alternatively Ubuntu (no firewall on it) or OS X (firewall temporarily deactivated) as an OS, using NAT (client machine is 192.168.2.4)

If I try to ping my public IP from another place on the internet, I get no answer. 95.182.244.x

I tried to make a packet capture targeting Protocol 41 when using the HE form to create the tunnel. But I did it on the client, not on the router. No reaction. But I can't tell if it's because the ISP does not allow it or router doesn't "forward" it to the client machine.

Is there some test I'm not doing right or other tests I should attempt?

many thanks, in advance!

Al

 100 
 on: July 04, 2019, 08:30:16 AM 
Started by tMHru - Last post by snarked
Different versions of the “ip” program, or different OSs.

Pages: 1 ... 8 9 [10]