On 3/30/2014 2:16 PM, İlker Aktuna wrote:
>
>>
>> Btw, my Shorewall configuration works by tracling the pakets on both
>> ISP connections. So if a connection is made through ppp1, all packets
>> of the same session go through that interface. Why doesn't this work
>> for packets incoming to that
>
> Btw, my Shorewall configuration works by tracling the pakets on both
> ISP connections. So if a connection is made through ppp1, all packets
> of the same session go through that interface. Why doesn't this work
> for packets incoming to that interface ?
>
>It does work that way.
What d
On 3/30/2014 7:09 AM, İlker Aktuna wrote:
> Hi Tom,
>
> I'm sorry that I come back so late. I was busy with other issues.
>
> I tried both of your suggestions but neither has helped me. Actually
> I was looking for a port based routing mechanism but it seems that it
> is not possible even with th
On 3/30/2014 7:30 AM, İlker Aktuna wrote:
> Keeping the port busy with another app is not reasonable. If I do that,
> Asterisk can not bind on the other interfaces.
>
> What about rejecting packets with source port 5060 going out from ppp1 ?
> They will try to go out from ppp0 ? Would that work
Keeping the port busy with another app is not reasonable. If I do that,
Asterisk can not bind on the other interfaces.
What about rejecting packets with source port 5060 going out from ppp1 ?
They will try to go out from ppp0 ? Would that work ?
And shall I have to masq these packets with ppp0
Hi Tom,
I'm sorry that I come back so late. I was busy with other issues.
I tried both of your suggestions but neither has helped me.
Actually I was looking for a port based routing mechanism but it seems that it
is not possible even with the so valuable ip-tables of linux. (weird ?)
Now I have
