I am trying to use pTRTd to allow IPv6-4 translation. My current setup involves the following interfaces:
1. eth0 - This is the LAN port with 192.168.10.x (IPv4 only) network with a DHCP server and connected to a switch to allow multiple hosts to connect to the network.
2. eth1 - This is the WAN port with both an IPv4 and an IPv6 address created using a prefix advertised by an RADVD server.
3. tap0 - This is the TAP device created by pTRTd to allow translation. The prefix assigned to pTRTd is aaaa:bbbb:cccc:dddd::

From within my box, I can ping hosts on the 192.168.10.xxx network. I can also ping the hosts using IPv6 via aaaa:bbbb:cccc:dddd::192.168.10.xxx

Now, I want my WAN devices to be able to do this as well. I am not an expert at Linux Networking. My gut feel is that I need to somehow accept packets coming into eth1 destined for the aaaa:bbbb:cccc:dddd network and route it to the tap0 interface (and vice versa). Can someone please help me out with this?

Thanks,
MT

I am having the same problem with ptrtd.
It works on the same box that it is run on...

Is it possible to set up a route to the machine running ptrtd
and access its functionality from a LAN?
eg: will it forward a range of IPv6 addresses on ethX to
IPv4 addresses on ethY ?

Thanks

In case anyone needs this in the future...
Here is a configuration that works for me.

Machine 1 (which runs ptrtd) RHEL5.2: 2.6.18-92.el5

/etc/sysconfig/network:

IPv6FORWARDING=yes

/etc/sysconfig/network-scripts/ifcfg-eth0:

IPV6_ROUTER=yes

/etc/sysctl.conf:

net.ipv6.conf.add.forwarding=1

Check:
sysctl -a | grep forward | grep ipv6
sudo /sbin/ipv6tables -L

sudo ip -6 addr add dev eth0 3ffe:ffff:fff:f::100/64

sudo ./ptrtd -p 3ffe:abcd:1234:9876::

Machine: 2 (client of ptrtd) FC4: 2.6.17-1.2139

sudo ip -6 addr add dev eth1 3ffe:ffff:fff:f::101/64

sudo ip -6 route add 3ffe:abcd:1234:9876/64 dev eth1
via 3ffe:ffff:fff:f::100

Testing (from machine 2):

ping6 3ffe:abcd:1234:9876::192.168.0.150
ssh 3ffe:abcd:1234:9876::192.168.0.150
telnet 3ffe:abcd:1234:9876::74.125.67.100 80
GET / HTTP/1.0<cr>
<cr>

FYI: In case anyone is using ptrtd...

There is bug in ptrtd that causes it to fail under
heavy traffic conditions. I reported it to the author
of ptrtd and he reports that he is no longer supporting
it. I have attached a patch file provided by J.Koenig
of fr.eu.org. He also has an updated version of ptrtd
at: http://jk.fr.eu.org/debian/etch/ptrtd_0.5.2-1~14.tar.gz

Regards

Attached Files

ptrtd-short-write-fix.txt (1.7 KB, 0 views)

The latest ptrtd is archived at:

http://code.google.com/p/ptrtd/