On 2025-10-14 00:03, Bill Sommerfeld via openindiana-discuss wrote:
On 10/13/25 13:41, Bill Sommerfeld wrote:
On 10/13/25 11:12, Predrag Zečević via openindiana-discuss wrote:
Does anyone is seeing same issue as me?
:; pfexec mtr --report-wide --report-cycles 5 --aslookup
pkg.openindiana.org
Start: 2025-10-13T20:03:44+0200
HOST: solarix Loss% Snt Last Avg Best Wrst StDev
mtr: mtr-packet reported invalid argument
I'm seeing the same thing for IPv4 but not IPv6 destinations.
I'll dig into this further when I get a chance.
The problem appears to be in the /usr/sbin/mtr-packet program (which
holds the setuid part of mtr).
If you revert to the mtr-0.95 version of the mtr-packet binary, mtr
starts working again.
Looking at truss output, the mtr-0.96 version fails a repeated bind()
syscall with a changed local address:
943929: getsockname(3, 0xFFFFFAFFFFDFC0B0, 0xFFFFFAFFFFDFC0AC,
SOV_DEFAULT) = 0
943929: AF_INET name = 0.0.0.0 port = 0
943929: bind(3, 0xFFFFFAFFFFDFC4B8, 16, SOV_XPG4_2) = 0
943929: AF_INET name = 127.0.0.1 port = 0
...
943929: getsockname(3, 0xFFFFFAFFFFDFB2A0, 0xFFFFFAFFFFDFB29C,
SOV_DEFAULT) = 0
943929: AF_INET name = 127.0.0.1 port = 0
943929: bind(3, 0x0041C518, 16, SOV_XPG4_2) Err#22 EINVAL
943929: AF_INET name = 173.11.94.227 port = 0
while the mtr-0.95 version doesn't call bind() at all.
- Bill
Thanks for info and tip
Regards> _______________________________________________
openindiana-discuss mailing list
[email protected]
https://openindiana.org/mailman/listinfo/openindiana-discuss
--
Predrag Zečević
_______________________________________________
openindiana-discuss mailing list
[email protected]
https://openindiana.org/mailman/listinfo/openindiana-discuss
