Unsubscribe
Hello All,
After having a look in iptables, I am able to solve this issue.
added following line in iptables
iptables -t mangle -A OUTPUT -s 192.168.20.10 -p tcp -j DIVERT
thanks much,
Regards,
-Abdul Jaleel
On Mon, Nov 16, 2015 at 3:31 PM, jaleel wrote:
> Hello All,
>
>
rule add fwmark 1 lookup 100
ip route add local 0.0.0.0/0 dev lo table 100
For the packet generated locally, I think I need to set the mangle table in
OUTPUT chain so that HAProxy will capture locally generated packet as well.
how do I create the OUPUT chain mangle table?
Regards,
-Abdul jaleel K
On Fri, Nov 13, 2015 at 1:12 PM, Aleksandar Lazic
wrote:
> Hi.
>
> But do you really think this is a haproxy Problem?
>
> Am 13-11-2015 08:38, schrieb Aleksandar Lazic:
>
>> Am 13-11-2015 06:14, schrieb jaleel:
>>
>>> It works if HAProxy and backend are in
It works if HAProxy and backend are in different box, but when both are in
same box it didn't work
On Fri, Nov 13, 2015 at 1:56 AM, Igor Cicimov <
ig...@encompasscorporation.com> wrote:
>
> On 13/11/2015 1:04 AM, "jaleel" wrote:
> >
> > Hello,
> &g
VRIP 10.200.3.84
When traffic comes to 10.200.3.84:7000, the routing to server2 is
successful and end-to-end communication is fine. But the response from
server1 (192.168.10.10:9001) is not reaching HAProxy.
I cannot have 3rd box for HAProxy alone.
Any suggestions
Thank you
-Abdul Jaleel
6 matches
Mail list logo