Hello,
>> Do you have any explanation for this routing inversion
>> or a workaround/good practice to have a ping -I always working as intended?
>
> This is working as intended..
The ping always work without the -I for the same destination,
no pf, no multiple route tables. just a classic routin
On 2012-11-24, Gilles LAMIRAL wrote:
> When I do two tcpdump on each interface I see that
> when it fails the ping -I are just going on the wrong interface
> even if the routing table indicates the contrary.
Routes depend on the *destination* address only. Source address
has no effect on which r
Hello,
I'm currently testing the multirouting on openbsd 5.2
It works basically but I encounter an issue with ping -I depending on the
order the default routes are set.
The context:
interface em2: ip 192.168.102.2 gw 192.168.102.1
interface em3: ip 192.168.103.2 gw 192.168.103.1
In 3 separated
3 matches
Mail list logo