Hurricane Electric's IPv6 Tunnel Broker Forums
May 25, 2013, 06:40:04 pm *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: Welcome to Hurricane Electric's Tunnelbroker.net forums!
 
   Home   Help Search Login Register  
Pages: 1 [2]
  Print  
Author Topic: Double-check IPv6to4 settings, please?  (Read 4142 times)
Keiro
Newbie
*
Posts: 12


View Profile
« Reply #15 on: September 29, 2010, 11:48:53 am »

Added! Cheesy

Should work now... I think. One more question:

Would this work so long as I assign other IPs, say: 2001:470:c:67f::3 for example, to other domains on the server?
Logged
broquea
Senior Network Engineer, SEVEN Networks (AS19733)
Hero Member
*****
Posts: 1379



View Profile WWW
« Reply #16 on: September 29, 2010, 11:50:18 am »

Yes, but you'll never be able to set reverse DNS since you are using the link /64 and not the routed /64.
Logged
Keiro
Newbie
*
Posts: 12


View Profile
« Reply #17 on: September 29, 2010, 11:51:46 am »

Ah! Okay, so to make sure I can set reverse DNS, how would I proceed in this manner?
Logged
broquea
Senior Network Engineer, SEVEN Networks (AS19733)
Hero Member
*****
Posts: 1379



View Profile WWW
« Reply #18 on: September 29, 2010, 11:53:05 am »

Configure IPs out of your routed /64 instead, on your server. Then you can control rDNS after delegation to whatever server or service you will use to manage it. Broker accounts get access to dns.he.net automatically if you want to use that service.
Logged
Keiro
Newbie
*
Posts: 12


View Profile
« Reply #19 on: September 29, 2010, 11:55:11 am »

Gotcha, that's what I was trying to learn how to do, to route IPs out of my assigned /64.

Thanks a whole bunch for the help so far!

I'll be dropping by that service in a bit to check it out.

Edit: So, I click on Routed /48 and I see a bunch of stuff, in my tunnel detail list.
« Last Edit: September 29, 2010, 01:00:49 pm by Keiro » Logged
Keiro
Newbie
*
Posts: 12


View Profile
« Reply #20 on: January 29, 2011, 04:13:48 am »

Jesus.

It took several hours of banging my head against the wall this morning.

Turns out it's not CSF at fault.

It's the darned kernel. We're running pre-2.6.20. Which means CSF kills the connections unintentionally.

HOWEVER! I can at least say that IPv6in4 now works!

Try checking shatteredtears.com via IPv6.  Grin

So... the solution is to essentially disable CSF and/or upgrade to post-2.6.2x kernel and reenable CSF to make it work.

For now, I'm just going to wait for a kernel upgrade and leave CSF disabled. :/
Logged
Pages: 1 [2]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!