I think I have found the solution. Modifying the masq file into: eth0:5:1.2.3.5 1.2.3.4 1.2.3.5 tcp 15000 eth0:6:1.2.3.6 1.2.3.4 1.2.3.6 tcp 15000
It works now. Many thanks Tom. sangprabv [email protected] On May 26, 2010, at 9:08 AM, Tom Eastep wrote: > On 5/25/10 6:50 PM, sangprabv wrote: >> Hi Tom, >> Thanks for the reply. OK I will try to explain more :) >> I have these eth configurations on my firewall: >> My WAN >> eth0 1.2.3.4 >> eth0:5 1.2.3.5 >> eth0:6 1.2.3.6 >> >> My LAN >> eth1 192.168.1.1 >> >> I register eth0:5 (1.2.3.5) that will be used by my application A >> and > eth0:6 (1.2.3.6) that will be used by my application B. Both > applications are in my firewall. When I try to connect to my partner > using application A and B, it always detected as eth0 (1.2.3.4) rather > then eth0:5 (1.2.3.5) and eth0:6 (1.2.3.6). > >> I also have add this rule in masq: >> eth0:5 192.168.1.1 1.2.3.5 tcp 15000 >> eth0:6 192.168.1.1 1.2.3.6 tcp 15000 > > You also say that you have added these rules; what appears before them? > Like in almost all Shorewall configuration files, the first rule that > matches a connection determines the outcome. > > -Tom > -- > Tom Eastep \ When I die, I want to go like my Grandfather who > Shoreline, \ died peacefully in his sleep. Not screaming like > Washington, USA \ all of the passengers in his car > http://shorewall.net \________________________________________________ > > ------------------------------------------------------------------------------ > > _______________________________________________ > Shorewall-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/shorewall-users ------------------------------------------------------------------------------ _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
