Le 27/01/2012 23:16, David Gersic a écrit : > I can use a couple of IPaddr2 RAs to bind 10.0.0.1 and 131.156.21.44 to eth3, > so no problems there. Then I just need to add the rules to iptables. On the > stop action, deleting the rules shouldn't be any big deal to do with > "iptables -t nat -D PREROUTING ...". > > So I guess I'll be writing an RA for this. I'll think some more about it over > the weekend, but I'm thinking that the interface (eth3), external ip > (131.156.21.44), external port (80), internal ip (10.0.0.1) and internal port > (8080) should be the required parameters. The rest can be hard coded in the > RA script. I'm looking at the 'portblock' RA as a possible starting point, > though it may be easier to start from scratch. > > Actions start and stop should be easy enough. Actions status and monitor > don't really make any sense, though, so I'm not sure what I'll do with those.
Writing your own RA is probably the best solution, the fastest would be to create a LSB script that only does the routing/firewalling part and to create a group that includes this lsb and your IPaddr2 resource(s). -- Cheers, Florian Crouzat _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
