- 1. iptable_nat seriously b0rken (score: 1)
- Author: Jan Rekorajski <baggins@xxxxxxxxxxxxxxxxx>
- Date: Wed, 5 Jul 2000 01:11:42 +0200
- Please CC answers to me as I'm not subscribed to the lists. The problem is simple, iptable_nat kills sit tunnels, see this: 7: sit1@lec0: <POINTOPOINT,MULTICAST,NOARP,UP> mtu 1480 qdisc noqueue link/
- /archives/netdev/2000-07/msg00007.html (9,554 bytes)
- 2. Re: iptable_nat seriously b0rken (score: 1)
- Author: Rusty Russell <rusty@xxxxxxxxxxxxxxxx>
- Date: Thu, 06 Jul 2000 14:09:44 +1000
- Dave, please merge. Having tunnels pass the entunnelled packets through the LOCAL_OUT hook is nicer anyway (from a filtering and least-surprise perspective), and allows my connection tracking code to
- /archives/netdev/2000-07/msg00010.html (11,898 bytes)
- 3. Re: iptable_nat seriously b0rken (score: 1)
- Author: "David S. Miller" <davem@xxxxxxxxxx>
- Date: Thu, 6 Jul 2000 18:44:51 -0700
- Since ip_gre and ipip are basically identical, fixed them too. Patch applied, thanks. Later, David S. Miller davem@xxxxxxxxxx
- /archives/netdev/2000-07/msg00011.html (8,658 bytes)
- 4. Re: iptable_nat seriously b0rken (score: 1)
- Author: kuznet@xxxxxxxxxxxxx
- Date: Fri, 7 Jul 2000 16:35:29 +0400 (MSK DST)
- Well, Paul, but could you drop a note, _why_ it failed to work without this? Seems, something is more fundamentally wrong yet. It is not a minor surprise. 8) Alexey
- /archives/netdev/2000-07/msg00014.html (8,686 bytes)
- 5. iptable_nat seriously b0rken (score: 1)
- Author: Jan Rekorajski <baggins@xxxxxxxxxxxxxxxxx>
- Date: Wed, 5 Jul 2000 01:11:42 +0200
- Please CC answers to me as I'm not subscribed to the lists. The problem is simple, iptable_nat kills sit tunnels, see this: 7: sit1@lec0: <POINTOPOINT,MULTICAST,NOARP,UP> mtu 1480 qdisc noqueue link/
- /archives/netdev/2000-07/msg00100.html (9,554 bytes)
- 6. Re: iptable_nat seriously b0rken (score: 1)
- Author: Rusty Russell <rusty@xxxxxxxxxxxxxxxx>
- Date: Thu, 06 Jul 2000 14:09:44 +1000
- Dave, please merge. Having tunnels pass the entunnelled packets through the LOCAL_OUT hook is nicer anyway (from a filtering and least-surprise perspective), and allows my connection tracking code to
- /archives/netdev/2000-07/msg00103.html (11,925 bytes)
- 7. Re: iptable_nat seriously b0rken (score: 1)
- Author: "David S. Miller" <davem@xxxxxxxxxx>
- Date: Thu, 6 Jul 2000 18:44:51 -0700
- Since ip_gre and ipip are basically identical, fixed them too. Patch applied, thanks. Later, David S. Miller davem@xxxxxxxxxx
- /archives/netdev/2000-07/msg00104.html (8,778 bytes)
- 8. Re: iptable_nat seriously b0rken (score: 1)
- Author: kuznet@xxxxxxxxxxxxx
- Date: Fri, 7 Jul 2000 16:35:29 +0400 (MSK DST)
- Hello! Well, Paul, but could you drop a note, _why_ it failed to work without this? Seems, something is more fundamentally wrong yet. It is not a minor surprise. 8) Alexey
- /archives/netdev/2000-07/msg00107.html (8,746 bytes)
This search system is powered by
Namazu