On 2006-07-22, Bruce Penrod wrote:

> ssh: connect to host fe80::5efe:192.168.1.1 port 22: Invalid argument

If you run it under strace will it tell you what arguments were used and
so give you a further clue?

This is a line from strace output using IPv4 and broken for convenient
newsreading.

connect(3, {sa_family=AF_INET, sin_port=htons(22),
sin_addr=inet_addr("217.155.xxx.yyy")}, 16) = 0

--
Elvis Notargiacomo master AT barefaced DOT cheek
http://www.notatla.org.uk/goen/
One of my other 11 computers runs Minix.

Thanks for that. I was able to see that the connect() call didn't like
the address argument. After a little more ipv6 research, I discovered
that the link scope ipv6 addresses must have a link specified, i.e. the
interface/device. This means that such addresses must be done like this:

fe80::5efe:192.168.1.1%eth0

Some commands, like ping6 have an argument to allow specifying the
device separately, but ssh does not. If I had set up global scope
addresses this wouldn't have happened and I would have missed the
opportunity to learn this.

Bruce

all mail refused wrote:
> On 2006-07-22, Bruce Penrod wrote:
>
>
>>ssh: connect to host fe80::5efe:192.168.1.1 port 22: Invalid argument
>
>
> If you run it under strace will it tell you what arguments were used and
> so give you a further clue?
>
> This is a line from strace output using IPv4 and broken for convenient
> newsreading.
>
> connect(3, {sa_family=AF_INET, sin_port=htons(22),
> sin_addr=inet_addr("217.155.xxx.yyy")}, 16) = 0
>