On 11/23/2017 08:07 AM, Tom Hetmer wrote:
> OK, and the results from 0.92? Good too?
> Testing the last working version doesn't help much. :-)
0.92 behaves the same. *Neither* version does what you want. I wrote my
email to show you that it's not a regression because it doesn't work the
way you wa
e: "Tom Hetmer" , 882...@bugs.debian.org
> Datum: 11/23/17 17:03
> Předmět: Re: Bug#882331: mtr: source routing with --address does not work
>
> You've got something else going on.
>
> I did a brand new install of Debian stable, created in a KVM VM using
> the follo
You've got something else going on.
I did a brand new install of Debian stable, created in a KVM VM using
the following command:
virt-install -n test --os-type=Linux --os-variant=debiansqueeze
--ram=512 --vcpus=1 --disk path=test.img,bus=virtio,size=10 --graphics
none --location
http://ftp.us.debi
You're expecting too much of the -a option. It does not do source
routing at all. When using "mtr -a", "ping -I", "traceroute -s", etc.,
the source IP address will change, but the destination route is still
chosen by the system routing table. This is useful when the remote end
treats the various IP
Package: mtr
Version: 0.92-1
Severity: normal
Hi,
there is a regression in 0.92.
Specifying an interface with --address is broken.
-a, --address ADDRESS bind the outgoing socket to ADDRESS
ie.
mtr -4 --address 213.198.94.174 ic.cz
will not get routed through the interface with the 213.1
5 matches
Mail list logo
