Am I the only one ssh'ing into link-local addresses from openwrt devices? I came across a recent regression that makes this impossible, and couldn't find any report on google / this list.

It's bugging the hell out of me on recent trunks

(last known good rev: r36140, first known broken: r38505, but didn't bisect further)

root@OpenWrt_r38505:/# ssh fe80::f8d1:11ff:fea0:fc%wlan0
ssh: Exited: Error resolving 'fe80::f8d1:11ff:fea0:fc' port 'wlan0'. Servname not supported for ai_socktype
root@OpenWrt_r38505:/# ssh [fe80::f8d1:11ff:fea0:fc%wlan0]
ssh: Exited: Error resolving '[fe80::f8d1:11ff:fea0:fc' port 'wlan0]'. Servname not supported for ai_socktype
root@OpenWrt_r38505:/# opkg list dropbear
dropbear - 2013.59-1

while on r36140 I could perfectly do:

root@OpenWrt_r36140:~# ssh fe80::6670:2ff:fe3d:a0f9%wlan1
root@fe80::6670:2ff:fe3d:a0f9%wlan1's password:
root@OpenWrt_r36140:~# opkg list dropbear
dropbear - 2012.55-2

Any pointers on this regression? or workarounds?
I first thought this would be related to the busybox-menuconfig changes, but then i remembered this is actually dropbear, so unrelated... I dug around menuconfig, and checked dropbear Makefile, but there aren't many knobs to tweak

It might perfectly be an upstream bug, so i'll poke around git logs and try to bisect a little

Cheers!

gui::/128
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Reply via email to