Public bug reported:
I'm trying to implement a routing short-cut solution, whose requirement is as
following:
server1 sends ip packets(destined to server3) to server2 via an ip tunnel
between them, server2 forwards the ip tunnel's output (the inner ip packets) to
server3. Each server has only one NIC and a public ip associated with it. All
servers can communicate with each other. All server are installed with ubuntu.
I'm sure the ip tunnel between server1 and server2 was configured correctly and
worked well. server2's ip_forward was enabled too. On server2's ip tunnel
interface, I can capture the traffic from server1 to server3. But server2 does
not forward the ip tunnel's output at all.
According to ip tunnel's implementation, the inner ip should be put back to
recieve queue -- netif_rx(), then if its destination is not the local host, ip
forward should forward it again. Is it right?
I switch server2's OS to fedora, and replace ip tunnel with gre tunnel (because
seems ubuntu's ip tunnel can't communicate with fedora's ip tunnel), then this
solution can work.
Many documents on the Internet show it's not a hard problem to forward ip
tunnel's output. So I guess there may be a bug in ubuntu's protocol stack.
I don't get the exact version of my ubuntu, but the uname command shows the
following:
$ uname -a
Linux ubuntu 2.6.24-26-server #1 SMP Tue Dec 1 18:26:43 UTC 2009 x86_64
GNU/Linux
** Affects: ubuntu
Importance: Undecided
Status: New
--
seems packets from ip tunnel are not put back into recieve queue again
https://bugs.launchpad.net/bugs/619750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
