Source routing, sort of
Quoted 2 lines · Michael T. Babcock
I'm assuming some basic source NATting is required; off to read the docs again ...
I hate self-follow-ups, but after reading the SNAT target for iptables, that's exactly what I need, except on a 2.2.19 kernel. I'd love to migrate to 2.4.x but we have a driver that doesn't work properly on 2.4, so we're stuck on 2.2.x for the reasonable future.
Any way to do SNAT or another way to do what I described using 2.2.x?
Signature · 7 lines
Michael T. Babcock CTO, FibreSpeed Ltd. (Hosting, Security, Consultation, Database, etc) http://www.fibrespeed.net/~mbabcock/ _______________________________________________ LARTC mailing list / [email protected] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
Quoted 2 lines
Any way to do SNAT or another way to do what I described using 2.2.x?
You could try something like :
ip route add 192.168.1.0/24 dev ipsec0 src 192.168.1.1
^^^^^^^^^^^^^^^
To enforce specific source-address selection.
Jerome Petazzoni <skaya at enix dot org>
--
'I'll tell you this!' shouted Rincewind. 'I'd rather trust me than history! Oh, shit, did I just say that?'
(Interesting Times)
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/