Bug 162029 - mtr does not work with --address option
mtr does not work with --address option
Product: Fedora
Classification: Fedora
Component: mtr (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Phil Knirsch
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2005-06-29 06:08 EDT by Alexander Lukyanov
Modified: 2015-03-04 20:14 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-05 11:11:54 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Alexander Lukyanov 2005-06-29 06:08:06 EDT
Description of problem:
mtr does not work with --address option, fails with a bogus error message

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. run 'mtr --address a.b.c.d', where a.b.c.d is an IP address on local network
Actual results:
mtr: failed to bind to interface: Socket operation on non-socket

Expected results:
mtr should start emitting IP packets with the given address as source.

Additional info:
strace shows that mtr tries to bind file descriptor 0:
bind(0, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 128) = -1
ENOTSOCK (Socket operation on non-socket)
Comment 1 Phil Knirsch 2005-09-05 08:29:53 EDT
Looking into it, something seems broken here...

Read ya, Phil
Comment 2 Phil Knirsch 2005-09-05 11:11:54 EDT
OK, interface got set before the any sockets were opened. The latest development
version will have a fix.

Keep in mind though that the --address option is really limited to IPv4 ip
addresses at the moment.

Read ya, Phil
Comment 3 Fedora Update System 2006-03-27 11:52:31 EST
mtr-0.71-0.FC4.1 has been pushed for FC4, which should resolve this issue.  If these problems are still present in this version, then please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.