diff options
| author | Jorge Boncompte <jorge@dti2.net> | 2007-05-04 01:00:32 +0200 |
|---|---|---|
| committer | Adrian Bunk <bunk@stusta.de> | 2007-05-04 01:00:32 +0200 |
| commit | c5807ace66d5085ed94608a7e9a084085ea57ede (patch) | |
| tree | f5129ba423df42b1d0f9decec62bc340103e1abd /drivers | |
| parent | 4879e0dfe9c9199e55566a6025a729854bb2a00e (diff) | |
| download | linux-stable-c5807ace66d5085ed94608a7e9a084085ea57ede.tar.gz linux-stable-c5807ace66d5085ed94608a7e9a084085ea57ede.tar.bz2 linux-stable-c5807ace66d5085ed94608a7e9a084085ea57ede.zip | |
[NETFILTER]: ip_nat_proto_gre: do not modify/corrupt GREv0 packets through NAT
While porting some changes of the 2.6.21-rc7 pptp/proto_gre conntrack
and nat modules to a 2.4.32 kernel I noticed that the gre_key function
returns a wrong pointer to the GRE key of a version 0 packet thus
corrupting the packet payload.
The intended behaviour for GREv0 packets is to act like
ip_conntrack_proto_generic/ip_nat_proto_unknown so I have ripped the
offending functions (not used anymore) and modified the
ip_nat_proto_gre modules to not touch version 0 (non PPTP) packets.
Signed-off-by: Jorge Boncompte <jorge@dti2.net>
Signed-off-by: Patrick McHardy <kaber@trash.net>
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions