routing patches seem to break output nat
Hi
We have applied the routing patches from http://www.ssi.bg/%7Eja/#routes. To 2.6.15 this seems to have broken our output natting. Has anyone else experienced this or any advice on how to fix. Is this working on the newer kernel i.e. 2.6.19 ? Any help would be appreciated.
Signature · 8 lines
Tim Haak email: [email protected] cel: 0837787100 First love is only a little foolishness and a lot of curiosity, no really self-respecting woman would take advantage of it. -- George Bernard Shaw, "John Bull's Other Island"
begin:vcard
fn:Tim Haak
n:Haak;Tim
email;internet:[email protected]
tel;cell:+28 83 778 7100
version:2.1
end:vcard
_______________________________________________
LARTC mailing list
[email protected]
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Hi
We have applied the routing patches from http://www.ssi.bg/%7Eja/#routes. To 2.6.15 this seems to have broken our output natting. Has anyone else experienced this or any advice on how to fix. Is this working on the newer kernel i.e. 2.6.19 ? Any help would be appreciated.
Signature · 1 line
Tim Haak
begin:vcard
fn:Tim Haak
n:Haak;Tim
email;internet:[email protected]
tel;cell:+28 83 778 7100
version:2.1
end:vcard
_______________________________________________
LARTC mailing list
[email protected]
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Hello,
Quoted 5 lines · Tim Haak
We have applied the routing patches from
http://www.ssi.bg/%7Eja/#routes. To 2.6.15 this seems to have broken our output natting. Has anyone else experienced this or any advice on how to fix. Is this working on the newer kernel i.e. 2.6.19 ? Any help would be appreciated.
Month ago Bart Duchesne found a problem with the
routes patch for 2.6 where reply packet for -j DNAT connections initiated in OUTPUT are dropped in pre-routing. I now updated the patches and if you have the same problem you can try the new diffs from today, eg.
http://www.ssi.bg/~ja/routes-2.6.19-13.diff
The fix for old patches is to remove the following extra check
(2 lines from net/ipv4/route.c) which obviously aborts ip_route_input() with EINVAL for RTN_LOCAL when replies from remote host are destined to our local IP:
+ if (lsrc && res.type != RTN_UNICAST && res.type != RTN_NAT)
+ goto e_inval;
Regards
--
Julian Anastasov <[email protected]>
_______________________________________________
LARTC mailing list
[email protected]
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Hi
thanks for the quick response that seemed to work :)
Tim Haak
email: [email protected] cel: 0837787100
The executioner is, I hear, very expert, and my neck is very slender.
-- Anne Boleyn
Quoted 22 lines · Julian Anastasov
Hello,
Quoted 2 lines · Tim Haak
We have applied the routing patches from http://www.ssi.bg/%7Eja/#routes. To 2.6.15 this seems to have broken our output natting. Has anyone else experienced this or any advice on how to fix. Is this working on the newer kernel i.e. 2.6.19 ? Any help would be appreciated.
Month ago Bart Duchesne found a problem with the
routes patch for 2.6 where reply packet for -j DNAT connections initiated
in OUTPUT are dropped in pre-routing. I now updated the patches and if you have the same problem you can try the new diffs from today, eg.http://www.ssi.bg/~ja/routes-2.6.19-13.diff
The fix for old patches is to remove the following extra check
(2 lines fromnet/ipv4/route.c) which obviously abortsip_route_input()with EINVAL forRTN_LOCALwhen replies from remote host are destined to our local IP:(quoted diff) +2
-0+ if (lsrc && res.type != RTN_UNICAST && res.type != RTN_NAT) + goto e_inval;
Quoted 6 lines
Regards
--
Julian Anastasov <[email protected]>
_______________________________________________
LARTC mailing list
[email protected]
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc