Skip to contentSkip to conversation

IPv6 Router and NAT/connection tracking

DISCUSSION Internet Protocol version Six 2 participants 2 messages Jun 19, 2003 – Jun 20, 2003

lore
Share & tools
lore
#0 lore raw

I'm connected via IPv6-in-IPv4 and I have a /48 assigned to this box, and I want the box to act as a router for my machines which it's doing nicely, only the conntrack thing is annoying the hell outta me ;) Will that solve it (ACCEPTING in both directions)?

And so what you are saying is that I should do this?:
iptables -I INPUT -p 41 -j ACCEPT
iptables -I OUTPUT -p 41 -j ACCEPT
iptables -I PREROUTING -p 41 -j ACCEPT -> not sure about this one

or am I wrong/forgetting something? :)

Thanks for your help, greatly appreciated

Quoted 31 lines

----------------------------------------
From: Joel Newkirk <[email protected]>
Sent: Thu Jun 19 00:28:57 GMT+02:00 2003
To: Internet Protocol version Six <[email protected]>
Subject: Re: IPv6 Router and NAT/connection tracking

Quoted 12 lines · Internet Protocol version Six

Hello all, I have a box that's configured as a firewall and router for IPv6, which is doing it's job fine, well, fine.., IPv6 connections keep timing out, they work for a second or 30 and then it timesout -> connections, ping6, traceroutes, ... from the Internet to the IPv6 address behind the router don't work anymore. Also if I do a ping6 or make a connection to a remote IPv6 host on the Internet it doesn't work, however if I ping6 the router from the network, everything works again...for about 30 seconds again, and then the problem begins again...

Quoted 4 lines

I was told that this is caused by NAT/connection tracking. Is there *any* solution to this? This is really annoying as I *need* NAT, but also want to give IPv6 connectivity to other machines on the LAN.

Are you directly connected to an IPv6 router, or are you connecting via an ipv6_over_ipv4 tunnel of some sort?

If you are direct, then I think all you need to do is work with ip6tables. (not sure, not done this)

Quoted 12 lines

If you are using a tunnel, then that tunnel will either be using a specific protocol or port number, which you could explicitly ACCEPT in all directions to avoid conntrack interference. For example, tspc (freenet6.net) uses TCP 4343 to talk to the server to create the tunnel, and the tunnel itself is protocol 41.

j

-----------------------------------------------------
Mail.be, WebMail and Virtual Office
http://www.mail.be

#1 lore raw
Quoted 5 lines · Internet Protocol version Six

I'm connected via IPv6-in-IPv4 and I have a /48 assigned to this box, and I want the box to act as a router for my machines which it's doing nicely, only the conntrack thing is annoying the hell outta me ;) Will that solve it (ACCEPTING in both directions)?

Quoted 8 lines

And so what you are saying is that I should do this?:
iptables -I INPUT -p 41 -j ACCEPT
iptables -I OUTPUT -p 41 -j ACCEPT
iptables -I PREROUTING -p 41 -j ACCEPT -> not sure about this one

or am I wrong/forgetting something? :)

Thanks for your help, greatly appreciated

AFAIK that is correct. (however the PREROUTING one wouldn't work, would need to be NAT table, and would be unnecessary anyway since that chain is supposed to have an ACCEPT policy - NAT in NAT table, filter in FILTER table) The two rules, INPUT and OUTPUT, should overcome any failure of the state machine to recognize intermittent tunnel traffic as ESTABLISHED.

Regarding 'internal' ipv6 traffic within your network, I suspect you should be using ip6tables there if needed. (ip6tables won't see 6in4 tunnel traffic though, since the tunnel itself is IPv4)

I haven't configured my gateway as an ipv6 router yet, however. I have a single address ATM from freenet6. When I get the chance to tinker (a few weeks from now at least) I want to configure ipv6 on my desktop as well as my server and see what there is to see.

j