RE: SSH into my mac does not work properly.

[Simon Fogarty]

I’m with tim,

If all devices are on the same network then ssh machine name should be fine 
from the ssh client on the windows machine.



From: macvisionaries@googlegroups.com [mailto:macvisionaries@googlegroups.com] 
On Behalf Of Jonathan Cohn
Sent: Friday, 9 February 2018 8:53 AM
To: macvisionaries@googlegroups.com
Subject: Re: SSH into my mac does not work properly.

Well, you gave conflicting information from what I did.  So to be clear your 
statement is probably right as long as there is exactly one device providing 
all network connectivity.

But perhaps we will learn more soon about the number of access points and 
routers that he has.

On Feb 8, 2018, at 2:47 PM, Tim Kilburn 
<kilbu...@me.com<mailto:kilbu...@me.com>> wrote:

Hi,

That shouldn't make any difference.  If they are both connected through the 
same router, and if you haven't configured private networks within the WiFi 
configurations, then you should be able to talk between devices.

• determine the IP addresses of each.
• from the Mac, see if you can ping the Windows box.  To accomplish this in 
Terminal, type "ping -c 5 IP_Address_of_Windows_Box".  If it answers, then 
they're seeing each other and there's something else going on.

Later...

Tim Kilburn
Fort McMurray, AB Canada

On Feb 8, 2018, at 12:19, Anders Holmberg 
<and...@pipkrokodil.se<mailto:and...@pipkrokodil.se>> wrote:

Hi!
Well the machines are on the same network but i have the machine i ssh from 
connected via cable.
THe mac is wirelessly connected.
Does it matter if i have both a 2.5 gz and 5Gz network.
/A


8 feb. 2018 kl. 16:15 skrev Jonathan Cohn 
<jon.c.c...@gmail.com<mailto:jon.c.c...@gmail.com>>:

Hello,

This message means that the computer you are ssh from does not know the correct 
path to the  10.0.0.0/24 network. So I expect your machines are on separate 
networks or perhaps you are not connected to a network at all for the source 
machine.

Generally, for IPv4 what happens when they connect to a network is that the 
machine will do a DHCP query to the all broadcast address 255.255.255.255 and 
the DHCP server (usually your router) will respond with a few pieces of 
information.

1. An IP address that your computer can use for a time.
2. How long until that IP address is available for reassignment.
3. The address of the default router.
4. The Netmask of the current network.
5. The DNS servers to use to translate from names to IP addresses.

That default route listed above means that any information not on the local 
network will be sent to the default router to forward onto a different network. 
The default router can do four things with your traffic being requested to be 
sent:
1. It can forward it to the destination / next router in the path to the 
destination.
2. It can send back a network unreachable message.
3. It can send back a host unreachable message.
4. It can just drop the packet and say nothing back to your computer.

If you are getting the network unreachable it means either your system doesn’t 
have a location on your network to send the information addressed  to the 
10.x.x.x network or it forwarded it to a router that gave back a message 
indicating that it could not forward to the 10 network.

Now the 10 network is very special. It was the original Arpanet network and 
once Arpanet was disbanded it was not allowed to be routed over the Internet, 
so it is exclusively used as a private network.

I think that is enough of an Internet lesson today.

Best wishes,

Jonathan Cohn
On Feb 8, 2018, at 9:42 AM, Anders Holmberg 
<and...@pipkrokodil.se<mailto:and...@pipkrokodil.se>> wrote:

Hi!
Ok, more on this thread.
I typed wrong the first time i did it and that’s why i get the not routed to 
host message.
Now when i type ssh andersholmberg@10.0.1.8<mailto:andersholmberg@10.0.1.8> i 
get the network is not reacchable.
Even though the remote login is turned on so i am a bit confused.
/A


7 feb. 2018 kl. 21:21 skrev Chris Moore 
<chris.w...@gmail.com<mailto:chris.w...@gmail.com>>:

Did you allow your mac to accept remote logins?  This is done in system 
preferences, sharing.  It also shows the format of the ssh command.  This 
command looks like”:
ssh user@computer-name
When prompted for the password you would enter the password for your mac user.

HTH
Chris


On Feb 7, 2018, at 2:59 PM, Bill Gallik 
<wfgal...@icloud.com<mailto:wfgal...@icloud.com>> wrote:

I wonder, are you using the  key after typing in your password?

My thought is that you may need to terminate the password string with a line 
feed rather than a carriage return (M rather than J).

It’s been a lot of years since I worked on a UNIX system, but if memory serves 
me correctly the carriage return and the line feed are treated as different 
animals.

I think you may be able to use the line feed by entering M.

I’d be curious if this helps, please let me know?

HTH


- Bill f

RE: SSH into my mac does not work properly.

[Simon Fogarty]

If your using windows to ssh in to the mac

What ssh application are you using on the windows machine?

Secondly are you sure the ssh option is enabled on your mac?

Ssh on windows needs an ssh server like open ssh if you try to access that from 
the mac.

From: macvisionaries@googlegroups.com [mailto:macvisionaries@googlegroups.com] 
On Behalf Of Tim Kilburn
Sent: Friday, 9 February 2018 8:47 AM
To: macvisionaries@googlegroups.com
Subject: Re: SSH into my mac does not work properly.

Hi,

That shouldn't make any difference.  If they are both connected through the 
same router, and if you haven't configured private networks within the WiFi 
configurations, then you should be able to talk between devices.

• determine the IP addresses of each.
• from the Mac, see if you can ping the Windows box.  To accomplish this in 
Terminal, type "ping -c 5 IP_Address_of_Windows_Box".  If it answers, then 
they're seeing each other and there's something else going on.

Later...

Tim Kilburn
Fort McMurray, AB Canada

On Feb 8, 2018, at 12:19, Anders Holmberg 
<and...@pipkrokodil.se<mailto:and...@pipkrokodil.se>> wrote:

Hi!
Well the machines are on the same network but i have the machine i ssh from 
connected via cable.
THe mac is wirelessly connected.
Does it matter if i have both a 2.5 gz and 5Gz network.
/A


8 feb. 2018 kl. 16:15 skrev Jonathan Cohn 
<jon.c.c...@gmail.com<mailto:jon.c.c...@gmail.com>>:

Hello,

This message means that the computer you are ssh from does not know the correct 
path to the  10.0.0.0/24 network. So I expect your machines are on separate 
networks or perhaps you are not connected to a network at all for the source 
machine.

Generally, for IPv4 what happens when they connect to a network is that the 
machine will do a DHCP query to the all broadcast address 255.255.255.255 and 
the DHCP server (usually your router) will respond with a few pieces of 
information.

1. An IP address that your computer can use for a time.
2. How long until that IP address is available for reassignment.
3. The address of the default router.
4. The Netmask of the current network.
5. The DNS servers to use to translate from names to IP addresses.

That default route listed above means that any information not on the local 
network will be sent to the default router to forward onto a different network. 
The default router can do four things with your traffic being requested to be 
sent:
1. It can forward it to the destination / next router in the path to the 
destination.
2. It can send back a network unreachable message.
3. It can send back a host unreachable message.
4. It can just drop the packet and say nothing back to your computer.

If you are getting the network unreachable it means either your system doesn’t 
have a location on your network to send the information addressed  to the 
10.x.x.x network or it forwarded it to a router that gave back a message 
indicating that it could not forward to the 10 network.

Now the 10 network is very special. It was the original Arpanet network and 
once Arpanet was disbanded it was not allowed to be routed over the Internet, 
so it is exclusively used as a private network.

I think that is enough of an Internet lesson today.

Best wishes,

Jonathan Cohn
On Feb 8, 2018, at 9:42 AM, Anders Holmberg 
<and...@pipkrokodil.se<mailto:and...@pipkrokodil.se>> wrote:

Hi!
Ok, more on this thread.
I typed wrong the first time i did it and that’s why i get the not routed to 
host message.
Now when i type ssh andersholmberg@10.0.1.8<mailto:andersholmberg@10.0.1.8> i 
get the network is not reacchable.
Even though the remote login is turned on so i am a bit confused.
/A


7 feb. 2018 kl. 21:21 skrev Chris Moore 
<chris.w...@gmail.com<mailto:chris.w...@gmail.com>>:

Did you allow your mac to accept remote logins?  This is done in system 
preferences, sharing.  It also shows the format of the ssh command.  This 
command looks like”:
ssh user@computer-name
When prompted for the password you would enter the password for your mac user.

HTH
Chris


On Feb 7, 2018, at 2:59 PM, Bill Gallik 
<wfgal...@icloud.com<mailto:wfgal...@icloud.com>> wrote:

I wonder, are you using the  key after typing in your password?

My thought is that you may need to terminate the password string with a line 
feed rather than a carriage return (M rather than J).

It’s been a lot of years since I worked on a UNIX system, but if memory serves 
me correctly the carriage return and the line feed are treated as different 
animals.

I think you may be able to use the line feed by entering M.

I’d be curious if this helps, please let me know?

HTH


- Bill from Ino, Wisconsin
- "Always acknowledge a fault. This will throw those in authority off their 
guard and give you an opportunity to commit more."
- US Humorist, Mark Twain (1835 - 1910)

On Feb 7, 2018, at 1:37 PM, Anders Holmberg 
<and...@pipkrokodil.se&

Re: SSH into my mac does not work properly.

[Anders Holmberg]

Hi!
Not really but i am intrested so i will digg this when my i am a bit more 
inspired.
/A

> 10 feb. 2018 kl. 17:31 skrev Jonathan Cohn :
> 
> that does not make sense to me I would expect the Open SSH server should only 
> be needed when going from Mac to Linux. Did you find an explanation on line 
> of why you needed the server also? 
> 
> 
>   Best wishes,
> 
> Jonathan Cohn
> 
> 
> 
>> On Feb 9, 2018, at 7:53 PM, Anders Holmberg > > wrote:
>> 
>> Hi guys!
>> I have resolved the issue.
>> It was on my Linux machine the problem was.
>> I had to install the openssh-server.
>> Now things are working as expected.
>> THanks for all your great help anyway!
>> /A
>> 
>>> 8 feb. 2018 kl. 21:47 skrev Tim Kilburn >> >:
>>> 
>>> Hi,
>>> 
>>> Conflicting but not.  As you've mentioned, if there's multiple routers, 
>>> then it's possible that alternative networks are being created so that 
>>> connectivity is complicated.  Although, in a perfect world, if everything 
>>> is going through one Access Point using a basic, default style of 
>>> configuration, whether devices are connected wirelessly or via ethernet, 
>>> and whether 2.4 G or 5 G, DHCP services should be handing out through a 
>>> single subnet, so connections between devices should be possible.
>>> 
>>> Later...
>>> 
>>> Tim Kilburn
>>> Fort McMurray, AB Canada
>>> 
>>> On Feb 8, 2018, at 12:53, Jonathan Cohn >> > wrote:
>>> 
>>> Well, you gave conflicting information from what I did.  So to be clear 
>>> your statement is probably right as long as there is exactly one device 
>>> providing all network connectivity. 
>>> 
>>> But perhaps we will learn more soon about the number of access points and 
>>> routers that he has. 
>>> 
 On Feb 8, 2018, at 2:47 PM, Tim Kilburn > wrote:
 
 Hi,
 
 That shouldn't make any difference.  If they are both connected through 
 the same router, and if you haven't configured private networks within the 
 WiFi configurations, then you should be able to talk between devices.
 
 • determine the IP addresses of each.
 • from the Mac, see if you can ping the Windows box.  To accomplish this 
 in Terminal, type "ping -c 5 IP_Address_of_Windows_Box".  If it answers, 
 then they're seeing each other and there's something else going on.
 
 Later...
 
 Tim Kilburn
 Fort McMurray, AB Canada
 
 On Feb 8, 2018, at 12:19, Anders Holmberg > wrote:
 
 Hi!
 Well the machines are on the same network but i have the machine i ssh 
 from connected via cable.
 THe mac is wirelessly connected.
 Does it matter if i have both a 2.5 gz and 5Gz network.
 /A
 
> 8 feb. 2018 kl. 16:15 skrev Jonathan Cohn  >:
> 
> Hello,
> 
> This message means that the computer you are ssh from does not know the 
> correct path to the  10.0.0.0/24 network. So I expect your machines are 
> on separate networks or perhaps you are not connected to a network at all 
> for the source machine.
> 
> Generally, for IPv4 what happens when they connect to a network is that 
> the machine will do a DHCP query to the all broadcast address 
> 255.255.255.255 and the DHCP server (usually your router) will respond 
> with a few pieces of information.
> 
> 1. An IP address that your computer can use for a time.
> 2. How long until that IP address is available for reassignment.
> 3. The address of the default router.
> 4. The Netmask of the current network.
> 5. The DNS servers to use to translate from names to IP addresses.
> 
> That default route listed above means that any information not on the 
> local network will be sent to the default router to forward onto a 
> different network. The default router can do four things with your 
> traffic being requested to be sent:
> 1. It can forward it to the destination / next router in the path to the 
> destination.
> 2. It can send back a network unreachable message.
> 3. It can send back a host unreachable message.
> 4. It can just drop the packet and say nothing back to your computer.
> 
> If you are getting the network unreachable it means either your system 
> doesn’t have a location on your network to send the information addressed 
>  to the 10.x.x.x network or it forwarded it to a router that gave back a 
> message indicating that it could not forward to the 10 network.
> 
> Now the 10 network is very special. It was the original Arpanet network 
> and once Arpanet was disbanded it was not allowed to be routed over the 
> 

Re: SSH into my mac does not work properly.

[Anders Holmberg]

Hi!
Thanks a lot.
Though i wish i could do it like you suggest.
But apple Music doesn’t support cromecast.
/A

> 10 feb. 2018 kl. 17:23 skrev Tim Kilburn :
> 
> Ahh.  That's the logic.  Yes, the Extreme doesn't have the AirPlay like the 
> Express.  You do what you have to do and if it works, good on you.
> 
> Have a good one..
> 
> Later...
> 
> Tim Kilburn
> Fort McMurray, AB Canada
> 
> On Feb 10, 2018, at 02:22, Anders Holmberg  > wrote:
> 
> Hi Tim!
> THe reason for that configuration is that the Airport express is connected to 
> my stereo which is close to my Linux machine.
> /A
> 
>> 9 feb. 2018 kl. 21:01 skrev Tim Kilburn > >:
>> 
>> Hi Anders,
>> 
>> Essentially, according to your explanation, all should be one network.  
>> Efficiency-wise, I'm not sure why the Express is the first device in the 
>> network.  The processor in an Extreme is much more powerful than that in an 
>> Express.  If it was my network, with those specific devices, I'd have the 
>> Extreme wired to the cable modem and thus also have your Linux box wired to 
>> the Extreme.  You could then still wirelessly connect the two Expresses to 
>> the network as extenders or whatever other use you've determined for them.  
>> This would make it so that the Extreme, with the more powerful processor was 
>> the head end handling the DHCP and NAT giving your network a little bit more 
>> efficiency.
>> 
>> That all being said, whatever Airport device is at the head end, should 
>> normally allow all traffic internally and only restrict traffic coming from 
>> the outside world.  That's the normal configuration anyway.
>> 
>> Later...
>> 
>> 
>> Tim Kilburn
>> Fort McMurray, AB Canada
>> 
>> On Feb 9, 2018, at 12:37, Anders Holmberg > > wrote:
>> 
>> Hi!
>> Ok, i haven’t gave much of info about my connection.
>> THe Cable modem is in bridge mode and has an airport express connected to it 
>> via cable.
>> That airport express is in nat mode and has an airport extreme and another 
>> airport express connected wirelessly.
>> THe airport express connected to the cable modem has a wired connection to 
>> my linux machine.
>> THe macbook air is connected wirelessly to my network.
>> If you want more info please let me know and i dig this up.
>> Thanks for your help GUYS!
>> /A
>> 
>>> 8 feb. 2018 kl. 20:53 skrev Jonathan Cohn >> >:
>>> 
>>> Well, you gave conflicting information from what I did.  So to be clear 
>>> your statement is probably right as long as there is exactly one device 
>>> providing all network connectivity. 
>>> 
>>> But perhaps we will learn more soon about the number of access points and 
>>> routers that he has. 
>>> 
 On Feb 8, 2018, at 2:47 PM, Tim Kilburn > wrote:
 
 Hi,
 
 That shouldn't make any difference.  If they are both connected through 
 the same router, and if you haven't configured private networks within the 
 WiFi configurations, then you should be able to talk between devices.
 
 • determine the IP addresses of each.
 • from the Mac, see if you can ping the Windows box.  To accomplish this 
 in Terminal, type "ping -c 5 IP_Address_of_Windows_Box".  If it answers, 
 then they're seeing each other and there's something else going on.
 
 Later...
 
 Tim Kilburn
 Fort McMurray, AB Canada
 
 On Feb 8, 2018, at 12:19, Anders Holmberg > wrote:
 
 Hi!
 Well the machines are on the same network but i have the machine i ssh 
 from connected via cable.
 THe mac is wirelessly connected.
 Does it matter if i have both a 2.5 gz and 5Gz network.
 /A
 
> 8 feb. 2018 kl. 16:15 skrev Jonathan Cohn  >:
> 
> Hello,
> 
> This message means that the computer you are ssh from does not know the 
> correct path to the  10.0.0.0/24 network. So I expect your machines are 
> on separate networks or perhaps you are not connected to a network at all 
> for the source machine.
> 
> Generally, for IPv4 what happens when they connect to a network is that 
> the machine will do a DHCP query to the all broadcast address 
> 255.255.255.255 and the DHCP server (usually your router) will respond 
> with a few pieces of information.
> 
> 1. An IP address that your computer can use for a time.
> 2. How long until that IP address is available for reassignment.
> 3. The address of the default router.
> 4. The Netmask of the current network.
> 5. The DNS servers to use to translate from names to IP addresses.
> 
> That default route listed above means that any information not 

Re: SSH into my mac does not work properly.

[Jonathan Cohn]

that does not make sense to me I would expect the Open SSH server should only 
be needed when going from Mac to Linux. Did you find an explanation on line of 
why you needed the server also? 


Best wishes,

Jonathan Cohn



> On Feb 9, 2018, at 7:53 PM, Anders Holmberg  wrote:
> 
> Hi guys!
> I have resolved the issue.
> It was on my Linux machine the problem was.
> I had to install the openssh-server.
> Now things are working as expected.
> THanks for all your great help anyway!
> /A
> 
>> 8 feb. 2018 kl. 21:47 skrev Tim Kilburn > >:
>> 
>> Hi,
>> 
>> Conflicting but not.  As you've mentioned, if there's multiple routers, then 
>> it's possible that alternative networks are being created so that 
>> connectivity is complicated.  Although, in a perfect world, if everything is 
>> going through one Access Point using a basic, default style of 
>> configuration, whether devices are connected wirelessly or via ethernet, and 
>> whether 2.4 G or 5 G, DHCP services should be handing out through a single 
>> subnet, so connections between devices should be possible.
>> 
>> Later...
>> 
>> Tim Kilburn
>> Fort McMurray, AB Canada
>> 
>> On Feb 8, 2018, at 12:53, Jonathan Cohn > > wrote:
>> 
>> Well, you gave conflicting information from what I did.  So to be clear your 
>> statement is probably right as long as there is exactly one device providing 
>> all network connectivity. 
>> 
>> But perhaps we will learn more soon about the number of access points and 
>> routers that he has. 
>> 
>>> On Feb 8, 2018, at 2:47 PM, Tim Kilburn >> > wrote:
>>> 
>>> Hi,
>>> 
>>> That shouldn't make any difference.  If they are both connected through the 
>>> same router, and if you haven't configured private networks within the WiFi 
>>> configurations, then you should be able to talk between devices.
>>> 
>>> • determine the IP addresses of each.
>>> • from the Mac, see if you can ping the Windows box.  To accomplish this in 
>>> Terminal, type "ping -c 5 IP_Address_of_Windows_Box".  If it answers, then 
>>> they're seeing each other and there's something else going on.
>>> 
>>> Later...
>>> 
>>> Tim Kilburn
>>> Fort McMurray, AB Canada
>>> 
>>> On Feb 8, 2018, at 12:19, Anders Holmberg >> > wrote:
>>> 
>>> Hi!
>>> Well the machines are on the same network but i have the machine i ssh from 
>>> connected via cable.
>>> THe mac is wirelessly connected.
>>> Does it matter if i have both a 2.5 gz and 5Gz network.
>>> /A
>>> 
 8 feb. 2018 kl. 16:15 skrev Jonathan Cohn >:
 
 Hello,
 
 This message means that the computer you are ssh from does not know the 
 correct path to the  10.0.0.0/24 network. So I expect your machines are on 
 separate networks or perhaps you are not connected to a network at all for 
 the source machine.
 
 Generally, for IPv4 what happens when they connect to a network is that 
 the machine will do a DHCP query to the all broadcast address 
 255.255.255.255 and the DHCP server (usually your router) will respond 
 with a few pieces of information.
 
 1. An IP address that your computer can use for a time.
 2. How long until that IP address is available for reassignment.
 3. The address of the default router.
 4. The Netmask of the current network.
 5. The DNS servers to use to translate from names to IP addresses.
 
 That default route listed above means that any information not on the 
 local network will be sent to the default router to forward onto a 
 different network. The default router can do four things with your traffic 
 being requested to be sent:
 1. It can forward it to the destination / next router in the path to the 
 destination.
 2. It can send back a network unreachable message.
 3. It can send back a host unreachable message.
 4. It can just drop the packet and say nothing back to your computer.
 
 If you are getting the network unreachable it means either your system 
 doesn’t have a location on your network to send the information addressed  
 to the 10.x.x.x network or it forwarded it to a router that gave back a 
 message indicating that it could not forward to the 10 network.
 
 Now the 10 network is very special. It was the original Arpanet network 
 and once Arpanet was disbanded it was not allowed to be routed over the 
 Internet, so it is exclusively used as a private network.  
 
 I think that is enough of an Internet lesson today.
 
 Best wishes,
 
 Jonathan Cohn  
> On Feb 8, 2018, at 9:42 AM, Anders Holmberg  > wrote:
> 
> Hi!
> Ok, more on this 

Re: SSH into my mac does not work properly.

[Tim Kilburn]

Ahh.  That's the logic.  Yes, the Extreme doesn't have the AirPlay like the 
Express.  You do what you have to do and if it works, good on you.

Have a good one..

Later...

Tim Kilburn
Fort McMurray, AB Canada

On Feb 10, 2018, at 02:22, Anders Holmberg  wrote:

Hi Tim!
THe reason for that configuration is that the Airport express is connected to 
my stereo which is close to my Linux machine.
/A

> 9 feb. 2018 kl. 21:01 skrev Tim Kilburn  >:
> 
> Hi Anders,
> 
> Essentially, according to your explanation, all should be one network.  
> Efficiency-wise, I'm not sure why the Express is the first device in the 
> network.  The processor in an Extreme is much more powerful than that in an 
> Express.  If it was my network, with those specific devices, I'd have the 
> Extreme wired to the cable modem and thus also have your Linux box wired to 
> the Extreme.  You could then still wirelessly connect the two Expresses to 
> the network as extenders or whatever other use you've determined for them.  
> This would make it so that the Extreme, with the more powerful processor was 
> the head end handling the DHCP and NAT giving your network a little bit more 
> efficiency.
> 
> That all being said, whatever Airport device is at the head end, should 
> normally allow all traffic internally and only restrict traffic coming from 
> the outside world.  That's the normal configuration anyway.
> 
> Later...
> 
> 
> Tim Kilburn
> Fort McMurray, AB Canada
> 
> On Feb 9, 2018, at 12:37, Anders Holmberg  > wrote:
> 
> Hi!
> Ok, i haven’t gave much of info about my connection.
> THe Cable modem is in bridge mode and has an airport express connected to it 
> via cable.
> That airport express is in nat mode and has an airport extreme and another 
> airport express connected wirelessly.
> THe airport express connected to the cable modem has a wired connection to my 
> linux machine.
> THe macbook air is connected wirelessly to my network.
> If you want more info please let me know and i dig this up.
> Thanks for your help GUYS!
> /A
> 
>> 8 feb. 2018 kl. 20:53 skrev Jonathan Cohn > >:
>> 
>> Well, you gave conflicting information from what I did.  So to be clear your 
>> statement is probably right as long as there is exactly one device providing 
>> all network connectivity. 
>> 
>> But perhaps we will learn more soon about the number of access points and 
>> routers that he has. 
>> 
>>> On Feb 8, 2018, at 2:47 PM, Tim Kilburn >> > wrote:
>>> 
>>> Hi,
>>> 
>>> That shouldn't make any difference.  If they are both connected through the 
>>> same router, and if you haven't configured private networks within the WiFi 
>>> configurations, then you should be able to talk between devices.
>>> 
>>> • determine the IP addresses of each.
>>> • from the Mac, see if you can ping the Windows box.  To accomplish this in 
>>> Terminal, type "ping -c 5 IP_Address_of_Windows_Box".  If it answers, then 
>>> they're seeing each other and there's something else going on.
>>> 
>>> Later...
>>> 
>>> Tim Kilburn
>>> Fort McMurray, AB Canada
>>> 
>>> On Feb 8, 2018, at 12:19, Anders Holmberg >> > wrote:
>>> 
>>> Hi!
>>> Well the machines are on the same network but i have the machine i ssh from 
>>> connected via cable.
>>> THe mac is wirelessly connected.
>>> Does it matter if i have both a 2.5 gz and 5Gz network.
>>> /A
>>> 
 8 feb. 2018 kl. 16:15 skrev Jonathan Cohn >:
 
 Hello,
 
 This message means that the computer you are ssh from does not know the 
 correct path to the  10.0.0.0/24 network. So I expect your machines are on 
 separate networks or perhaps you are not connected to a network at all for 
 the source machine.
 
 Generally, for IPv4 what happens when they connect to a network is that 
 the machine will do a DHCP query to the all broadcast address 
 255.255.255.255 and the DHCP server (usually your router) will respond 
 with a few pieces of information.
 
 1. An IP address that your computer can use for a time.
 2. How long until that IP address is available for reassignment.
 3. The address of the default router.
 4. The Netmask of the current network.
 5. The DNS servers to use to translate from names to IP addresses.
 
 That default route listed above means that any information not on the 
 local network will be sent to the default router to forward onto a 
 different network. The default router can do four things with your traffic 
 being requested to be sent:
 1. It can forward it to the destination / next router in the path to the 
 destination.
 2. It can send back a network unreachable message.

Re: SSH into my mac does not work properly.

[Anders Holmberg]

Hi Tim!
THe reason for that configuration is that the Airport express is connected to 
my stereo which is close to my Linux machine.
/A

> 9 feb. 2018 kl. 21:01 skrev Tim Kilburn :
> 
> Hi Anders,
> 
> Essentially, according to your explanation, all should be one network.  
> Efficiency-wise, I'm not sure why the Express is the first device in the 
> network.  The processor in an Extreme is much more powerful than that in an 
> Express.  If it was my network, with those specific devices, I'd have the 
> Extreme wired to the cable modem and thus also have your Linux box wired to 
> the Extreme.  You could then still wirelessly connect the two Expresses to 
> the network as extenders or whatever other use you've determined for them.  
> This would make it so that the Extreme, with the more powerful processor was 
> the head end handling the DHCP and NAT giving your network a little bit more 
> efficiency.
> 
> That all being said, whatever Airport device is at the head end, should 
> normally allow all traffic internally and only restrict traffic coming from 
> the outside world.  That's the normal configuration anyway.
> 
> Later...
> 
> 
> Tim Kilburn
> Fort McMurray, AB Canada
> 
> On Feb 9, 2018, at 12:37, Anders Holmberg  > wrote:
> 
> Hi!
> Ok, i haven’t gave much of info about my connection.
> THe Cable modem is in bridge mode and has an airport express connected to it 
> via cable.
> That airport express is in nat mode and has an airport extreme and another 
> airport express connected wirelessly.
> THe airport express connected to the cable modem has a wired connection to my 
> linux machine.
> THe macbook air is connected wirelessly to my network.
> If you want more info please let me know and i dig this up.
> Thanks for your help GUYS!
> /A
> 
>> 8 feb. 2018 kl. 20:53 skrev Jonathan Cohn > >:
>> 
>> Well, you gave conflicting information from what I did.  So to be clear your 
>> statement is probably right as long as there is exactly one device providing 
>> all network connectivity. 
>> 
>> But perhaps we will learn more soon about the number of access points and 
>> routers that he has. 
>> 
>>> On Feb 8, 2018, at 2:47 PM, Tim Kilburn >> > wrote:
>>> 
>>> Hi,
>>> 
>>> That shouldn't make any difference.  If they are both connected through the 
>>> same router, and if you haven't configured private networks within the WiFi 
>>> configurations, then you should be able to talk between devices.
>>> 
>>> • determine the IP addresses of each.
>>> • from the Mac, see if you can ping the Windows box.  To accomplish this in 
>>> Terminal, type "ping -c 5 IP_Address_of_Windows_Box".  If it answers, then 
>>> they're seeing each other and there's something else going on.
>>> 
>>> Later...
>>> 
>>> Tim Kilburn
>>> Fort McMurray, AB Canada
>>> 
>>> On Feb 8, 2018, at 12:19, Anders Holmberg >> > wrote:
>>> 
>>> Hi!
>>> Well the machines are on the same network but i have the machine i ssh from 
>>> connected via cable.
>>> THe mac is wirelessly connected.
>>> Does it matter if i have both a 2.5 gz and 5Gz network.
>>> /A
>>> 
 8 feb. 2018 kl. 16:15 skrev Jonathan Cohn >:
 
 Hello,
 
 This message means that the computer you are ssh from does not know the 
 correct path to the  10.0.0.0/24 network. So I expect your machines are on 
 separate networks or perhaps you are not connected to a network at all for 
 the source machine.
 
 Generally, for IPv4 what happens when they connect to a network is that 
 the machine will do a DHCP query to the all broadcast address 
 255.255.255.255 and the DHCP server (usually your router) will respond 
 with a few pieces of information.
 
 1. An IP address that your computer can use for a time.
 2. How long until that IP address is available for reassignment.
 3. The address of the default router.
 4. The Netmask of the current network.
 5. The DNS servers to use to translate from names to IP addresses.
 
 That default route listed above means that any information not on the 
 local network will be sent to the default router to forward onto a 
 different network. The default router can do four things with your traffic 
 being requested to be sent:
 1. It can forward it to the destination / next router in the path to the 
 destination.
 2. It can send back a network unreachable message.
 3. It can send back a host unreachable message.
 4. It can just drop the packet and say nothing back to your computer.
 
 If you are getting the network unreachable it means either your system 
 doesn’t have a location on your network to send the information addressed  
 to the 10.x.x.x 

Re: SSH into my mac does not work properly.

[Anders Holmberg]

Hi guys!
I have resolved the issue.
It was on my Linux machine the problem was.
I had to install the openssh-server.
Now things are working as expected.
THanks for all your great help anyway!
/A

> 8 feb. 2018 kl. 21:47 skrev Tim Kilburn :
> 
> Hi,
> 
> Conflicting but not.  As you've mentioned, if there's multiple routers, then 
> it's possible that alternative networks are being created so that 
> connectivity is complicated.  Although, in a perfect world, if everything is 
> going through one Access Point using a basic, default style of configuration, 
> whether devices are connected wirelessly or via ethernet, and whether 2.4 G 
> or 5 G, DHCP services should be handing out through a single subnet, so 
> connections between devices should be possible.
> 
> Later...
> 
> Tim Kilburn
> Fort McMurray, AB Canada
> 
> On Feb 8, 2018, at 12:53, Jonathan Cohn  > wrote:
> 
> Well, you gave conflicting information from what I did.  So to be clear your 
> statement is probably right as long as there is exactly one device providing 
> all network connectivity. 
> 
> But perhaps we will learn more soon about the number of access points and 
> routers that he has. 
> 
>> On Feb 8, 2018, at 2:47 PM, Tim Kilburn > > wrote:
>> 
>> Hi,
>> 
>> That shouldn't make any difference.  If they are both connected through the 
>> same router, and if you haven't configured private networks within the WiFi 
>> configurations, then you should be able to talk between devices.
>> 
>> • determine the IP addresses of each.
>> • from the Mac, see if you can ping the Windows box.  To accomplish this in 
>> Terminal, type "ping -c 5 IP_Address_of_Windows_Box".  If it answers, then 
>> they're seeing each other and there's something else going on.
>> 
>> Later...
>> 
>> Tim Kilburn
>> Fort McMurray, AB Canada
>> 
>> On Feb 8, 2018, at 12:19, Anders Holmberg > > wrote:
>> 
>> Hi!
>> Well the machines are on the same network but i have the machine i ssh from 
>> connected via cable.
>> THe mac is wirelessly connected.
>> Does it matter if i have both a 2.5 gz and 5Gz network.
>> /A
>> 
>>> 8 feb. 2018 kl. 16:15 skrev Jonathan Cohn >> >:
>>> 
>>> Hello,
>>> 
>>> This message means that the computer you are ssh from does not know the 
>>> correct path to the  10.0.0.0/24 network. So I expect your machines are on 
>>> separate networks or perhaps you are not connected to a network at all for 
>>> the source machine.
>>> 
>>> Generally, for IPv4 what happens when they connect to a network is that the 
>>> machine will do a DHCP query to the all broadcast address 255.255.255.255 
>>> and the DHCP server (usually your router) will respond with a few pieces of 
>>> information.
>>> 
>>> 1. An IP address that your computer can use for a time.
>>> 2. How long until that IP address is available for reassignment.
>>> 3. The address of the default router.
>>> 4. The Netmask of the current network.
>>> 5. The DNS servers to use to translate from names to IP addresses.
>>> 
>>> That default route listed above means that any information not on the local 
>>> network will be sent to the default router to forward onto a different 
>>> network. The default router can do four things with your traffic being 
>>> requested to be sent:
>>> 1. It can forward it to the destination / next router in the path to the 
>>> destination.
>>> 2. It can send back a network unreachable message.
>>> 3. It can send back a host unreachable message.
>>> 4. It can just drop the packet and say nothing back to your computer.
>>> 
>>> If you are getting the network unreachable it means either your system 
>>> doesn’t have a location on your network to send the information addressed  
>>> to the 10.x.x.x network or it forwarded it to a router that gave back a 
>>> message indicating that it could not forward to the 10 network.
>>> 
>>> Now the 10 network is very special. It was the original Arpanet network and 
>>> once Arpanet was disbanded it was not allowed to be routed over the 
>>> Internet, so it is exclusively used as a private network.  
>>> 
>>> I think that is enough of an Internet lesson today.
>>> 
>>> Best wishes,
>>> 
>>> Jonathan Cohn  
 On Feb 8, 2018, at 9:42 AM, Anders Holmberg > wrote:
 
 Hi!
 Ok, more on this thread.
 I typed wrong the first time i did it and that’s why i get the not routed 
 to host message.
 Now when i type ssh andersholmberg@10.0.1.8 
  i get the network is not reacchable.
 Even though the remote login is turned on so i am a bit confused.
 /A
 
> 7 feb. 2018 kl. 21:21 skrev Chris Moore  >:
> 
> Did you allow your mac to 

Re: SSH into my mac does not work properly.

[Jonathan Cohn]

I would not expect the message network unavailable in this case, unless the 
Airports that are not directly connected to the Cable are misconfigured. 

If SSH Server is incorrectly configured you should get a port unreachable. If 
the 10.0.1 network is properly configured in your house than I  would expect a 
host unreachable if the ping command had failed.

Essentially there are four levels of unreachable messages that I remember from 
the standards:
1. Port unreachable  Computer can be found but no service is available for the 
specified protocol / TCP Port.
2. Administratively prohibited Generally means a firewall indicates you are 
trying to get to a protected service from a unsafe source.
3. Host unreachable The network being specified is found but could not find any 
computer listening to the IP address specified.
4. Network unreachable Can’t find any device in the subnet you are attempting 
to communicate with.

So, after you have verified that you can ping the host try ssh short name@!$ 
If this is the first time connecting you should get a message like:
The authenticity of host '127.0.0.1 (127.0.0.1)' can't be established.
ECDSA key fingerprint is SHA256:GM+iiwF/NURk+aPPEnA0hKIUGkbx6fBJ6Xr5dqbQNbA.
Are you sure you want to continue connecting (yes/no)? 
just say yes and then it will prompt for a password. If you are going to be 
using ssh frequently between these machines you might want to look at putting 
your ssh public key onto the Macintosh .ssh directory so you don’t get prompted 
by a password each time. I haven’t configured this in too long to remember the 
exact procedure.

> On Feb 9, 2018, at 2:47 PM, Tim Kilburn  wrote:
> 
> Hi,
> 
> OK, then we don't have a network/subnet problem.  It's either a blocked 
> connection, or the simple problem is the username/password authentication 
> issue.  When attempting to connect via ssh, in the username@IP_Address 
> syntax, the username is what MacOS knows as the Short name.  That is, the 
> account name.  The account name or short name are different than what a user 
> sees at the Login screen etc.  This name is usually the name of your Home 
> folder and can also be confirmed in Users & Groups. In Users & Groups in 
> System Prefs, unlock the lock, interact with the Users, Groups & Login 
> Options list and VO-shift-m on your account.  Select Advanced from the 
> contextual menu and the account name is available in this Advanced dialog.  
> Make sure not to change anything in this dialog as you can mess up things 
> royally.  I'd just hit the Cancel button after confirming the account name.
> 
> So, now that you know the account name, that is the one you use before the @ 
> sign in the username@IP_Address syntax.  It should then ask for your 
> password.  If this doesn't allow connection, you can check in System Prefs, 
> in the Sharing pane under Remote Login, and make sure that your user is 
> permitted to use the Remote Login service.
> 
> Later...
> 
> 
> Tim Kilburn
> Fort McMurray, AB Canada
> 
> On Feb 9, 2018, at 12:33, Anders Holmberg  > wrote:
> 
> Hi!
> Ok, i can ping from my mac to my Linux machine and no packets get lost.
> The other way it works too.
> /A
> 
>> 8 feb. 2018 kl. 20:47 skrev Tim Kilburn > >:
>> 
>> Hi,
>> 
>> That shouldn't make any difference.  If they are both connected through the 
>> same router, and if you haven't configured private networks within the WiFi 
>> configurations, then you should be able to talk between devices.
>> 
>> • determine the IP addresses of each.
>> • from the Mac, see if you can ping the Windows box.  To accomplish this in 
>> Terminal, type "ping -c 5 IP_Address_of_Windows_Box".  If it answers, then 
>> they're seeing each other and there's something else going on.
>> 
>> Later...
>> 
>> Tim Kilburn
>> Fort McMurray, AB Canada
>> 
>> On Feb 8, 2018, at 12:19, Anders Holmberg > > wrote:
>> 
>> Hi!
>> Well the machines are on the same network but i have the machine i ssh from 
>> connected via cable.
>> THe mac is wirelessly connected.
>> Does it matter if i have both a 2.5 gz and 5Gz network.
>> /A
>> 
>>> 8 feb. 2018 kl. 16:15 skrev Jonathan Cohn >> >:
>>> 
>>> Hello,
>>> 
>>> This message means that the computer you are ssh from does not know the 
>>> correct path to the  10.0.0.0/24 network. So I expect your machines are on 
>>> separate networks or perhaps you are not connected to a network at all for 
>>> the source machine.
>>> 
>>> Generally, for IPv4 what happens when they connect to a network is that the 
>>> machine will do a DHCP query to the all broadcast address 255.255.255.255 
>>> and the DHCP server (usually your router) will respond with a few pieces of 
>>> information.
>>> 
>>> 1. An IP address that your computer can use for a time.
>>> 2. How long 

Re: SSH into my mac does not work properly.

[Tim Kilburn]

Hi Anders,

Essentially, according to your explanation, all should be one network.  
Efficiency-wise, I'm not sure why the Express is the first device in the 
network.  The processor in an Extreme is much more powerful than that in an 
Express.  If it was my network, with those specific devices, I'd have the 
Extreme wired to the cable modem and thus also have your Linux box wired to the 
Extreme.  You could then still wirelessly connect the two Expresses to the 
network as extenders or whatever other use you've determined for them.  This 
would make it so that the Extreme, with the more powerful processor was the 
head end handling the DHCP and NAT giving your network a little bit more 
efficiency.

That all being said, whatever Airport device is at the head end, should 
normally allow all traffic internally and only restrict traffic coming from the 
outside world.  That's the normal configuration anyway.

Later...


Tim Kilburn
Fort McMurray, AB Canada

On Feb 9, 2018, at 12:37, Anders Holmberg  wrote:

Hi!
Ok, i haven’t gave much of info about my connection.
THe Cable modem is in bridge mode and has an airport express connected to it 
via cable.
That airport express is in nat mode and has an airport extreme and another 
airport express connected wirelessly.
THe airport express connected to the cable modem has a wired connection to my 
linux machine.
THe macbook air is connected wirelessly to my network.
If you want more info please let me know and i dig this up.
Thanks for your help GUYS!
/A

> 8 feb. 2018 kl. 20:53 skrev Jonathan Cohn  >:
> 
> Well, you gave conflicting information from what I did.  So to be clear your 
> statement is probably right as long as there is exactly one device providing 
> all network connectivity. 
> 
> But perhaps we will learn more soon about the number of access points and 
> routers that he has. 
> 
>> On Feb 8, 2018, at 2:47 PM, Tim Kilburn > > wrote:
>> 
>> Hi,
>> 
>> That shouldn't make any difference.  If they are both connected through the 
>> same router, and if you haven't configured private networks within the WiFi 
>> configurations, then you should be able to talk between devices.
>> 
>> • determine the IP addresses of each.
>> • from the Mac, see if you can ping the Windows box.  To accomplish this in 
>> Terminal, type "ping -c 5 IP_Address_of_Windows_Box".  If it answers, then 
>> they're seeing each other and there's something else going on.
>> 
>> Later...
>> 
>> Tim Kilburn
>> Fort McMurray, AB Canada
>> 
>> On Feb 8, 2018, at 12:19, Anders Holmberg > > wrote:
>> 
>> Hi!
>> Well the machines are on the same network but i have the machine i ssh from 
>> connected via cable.
>> THe mac is wirelessly connected.
>> Does it matter if i have both a 2.5 gz and 5Gz network.
>> /A
>> 
>>> 8 feb. 2018 kl. 16:15 skrev Jonathan Cohn >> >:
>>> 
>>> Hello,
>>> 
>>> This message means that the computer you are ssh from does not know the 
>>> correct path to the  10.0.0.0/24 network. So I expect your machines are on 
>>> separate networks or perhaps you are not connected to a network at all for 
>>> the source machine.
>>> 
>>> Generally, for IPv4 what happens when they connect to a network is that the 
>>> machine will do a DHCP query to the all broadcast address 255.255.255.255 
>>> and the DHCP server (usually your router) will respond with a few pieces of 
>>> information.
>>> 
>>> 1. An IP address that your computer can use for a time.
>>> 2. How long until that IP address is available for reassignment.
>>> 3. The address of the default router.
>>> 4. The Netmask of the current network.
>>> 5. The DNS servers to use to translate from names to IP addresses.
>>> 
>>> That default route listed above means that any information not on the local 
>>> network will be sent to the default router to forward onto a different 
>>> network. The default router can do four things with your traffic being 
>>> requested to be sent:
>>> 1. It can forward it to the destination / next router in the path to the 
>>> destination.
>>> 2. It can send back a network unreachable message.
>>> 3. It can send back a host unreachable message.
>>> 4. It can just drop the packet and say nothing back to your computer.
>>> 
>>> If you are getting the network unreachable it means either your system 
>>> doesn’t have a location on your network to send the information addressed  
>>> to the 10.x.x.x network or it forwarded it to a router that gave back a 
>>> message indicating that it could not forward to the 10 network.
>>> 
>>> Now the 10 network is very special. It was the original Arpanet network and 
>>> once Arpanet was disbanded it was not allowed to be routed over the 
>>> Internet, so it is exclusively used as a private network.  
>>> 
>>> I think that is enough of an 

Re: SSH into my mac does not work properly.

[Tim Kilburn]

Hi,

OK, then we don't have a network/subnet problem.  It's either a blocked 
connection, or the simple problem is the username/password authentication 
issue.  When attempting to connect via ssh, in the username@IP_Address syntax, 
the username is what MacOS knows as the Short name.  That is, the account name. 
 The account name or short name are different than what a user sees at the 
Login screen etc.  This name is usually the name of your Home folder and can 
also be confirmed in Users & Groups. In Users & Groups in System Prefs, unlock 
the lock, interact with the Users, Groups & Login Options list and VO-shift-m 
on your account.  Select Advanced from the contextual menu and the account name 
is available in this Advanced dialog.  Make sure not to change anything in this 
dialog as you can mess up things royally.  I'd just hit the Cancel button after 
confirming the account name.

So, now that you know the account name, that is the one you use before the @ 
sign in the username@IP_Address syntax.  It should then ask for your password.  
If this doesn't allow connection, you can check in System Prefs, in the Sharing 
pane under Remote Login, and make sure that your user is permitted to use the 
Remote Login service.

Later...


Tim Kilburn
Fort McMurray, AB Canada

On Feb 9, 2018, at 12:33, Anders Holmberg  wrote:

Hi!
Ok, i can ping from my mac to my Linux machine and no packets get lost.
The other way it works too.
/A

> 8 feb. 2018 kl. 20:47 skrev Tim Kilburn  >:
> 
> Hi,
> 
> That shouldn't make any difference.  If they are both connected through the 
> same router, and if you haven't configured private networks within the WiFi 
> configurations, then you should be able to talk between devices.
> 
> • determine the IP addresses of each.
> • from the Mac, see if you can ping the Windows box.  To accomplish this in 
> Terminal, type "ping -c 5 IP_Address_of_Windows_Box".  If it answers, then 
> they're seeing each other and there's something else going on.
> 
> Later...
> 
> Tim Kilburn
> Fort McMurray, AB Canada
> 
> On Feb 8, 2018, at 12:19, Anders Holmberg  > wrote:
> 
> Hi!
> Well the machines are on the same network but i have the machine i ssh from 
> connected via cable.
> THe mac is wirelessly connected.
> Does it matter if i have both a 2.5 gz and 5Gz network.
> /A
> 
>> 8 feb. 2018 kl. 16:15 skrev Jonathan Cohn > >:
>> 
>> Hello,
>> 
>> This message means that the computer you are ssh from does not know the 
>> correct path to the  10.0.0.0/24 network. So I expect your machines are on 
>> separate networks or perhaps you are not connected to a network at all for 
>> the source machine.
>> 
>> Generally, for IPv4 what happens when they connect to a network is that the 
>> machine will do a DHCP query to the all broadcast address 255.255.255.255 
>> and the DHCP server (usually your router) will respond with a few pieces of 
>> information.
>> 
>> 1. An IP address that your computer can use for a time.
>> 2. How long until that IP address is available for reassignment.
>> 3. The address of the default router.
>> 4. The Netmask of the current network.
>> 5. The DNS servers to use to translate from names to IP addresses.
>> 
>> That default route listed above means that any information not on the local 
>> network will be sent to the default router to forward onto a different 
>> network. The default router can do four things with your traffic being 
>> requested to be sent:
>> 1. It can forward it to the destination / next router in the path to the 
>> destination.
>> 2. It can send back a network unreachable message.
>> 3. It can send back a host unreachable message.
>> 4. It can just drop the packet and say nothing back to your computer.
>> 
>> If you are getting the network unreachable it means either your system 
>> doesn’t have a location on your network to send the information addressed  
>> to the 10.x.x.x network or it forwarded it to a router that gave back a 
>> message indicating that it could not forward to the 10 network.
>> 
>> Now the 10 network is very special. It was the original Arpanet network and 
>> once Arpanet was disbanded it was not allowed to be routed over the 
>> Internet, so it is exclusively used as a private network.  
>> 
>> I think that is enough of an Internet lesson today.
>> 
>> Best wishes,
>> 
>> Jonathan Cohn  
>>> On Feb 8, 2018, at 9:42 AM, Anders Holmberg >> > wrote:
>>> 
>>> Hi!
>>> Ok, more on this thread.
>>> I typed wrong the first time i did it and that’s why i get the not routed 
>>> to host message.
>>> Now when i type ssh andersholmberg@10.0.1.8 
>>>  i get the network is not reacchable.
>>> Even though the remote login is turned on so i am a bit confused.
>>> /A
>>> 
 7 feb. 2018 

Re: SSH into my mac does not work properly.

[Anders Holmberg]

Hi!
Ok, i haven’t gave much of info about my connection.
THe Cable modem is in bridge mode and has an airport express connected to it 
via cable.
That airport express is in nat mode and has an airport extreme and another 
airport express connected wirelessly.
THe airport express connected to the cable modem has a wired connection to my 
linux machine.
THe macbook air is connected wirelessly to my network.
If you want more info please let me know and i dig this up.
Thanks for your help GUYS!
/A

> 8 feb. 2018 kl. 20:53 skrev Jonathan Cohn :
> 
> Well, you gave conflicting information from what I did.  So to be clear your 
> statement is probably right as long as there is exactly one device providing 
> all network connectivity. 
> 
> But perhaps we will learn more soon about the number of access points and 
> routers that he has. 
> 
>> On Feb 8, 2018, at 2:47 PM, Tim Kilburn > > wrote:
>> 
>> Hi,
>> 
>> That shouldn't make any difference.  If they are both connected through the 
>> same router, and if you haven't configured private networks within the WiFi 
>> configurations, then you should be able to talk between devices.
>> 
>> • determine the IP addresses of each.
>> • from the Mac, see if you can ping the Windows box.  To accomplish this in 
>> Terminal, type "ping -c 5 IP_Address_of_Windows_Box".  If it answers, then 
>> they're seeing each other and there's something else going on.
>> 
>> Later...
>> 
>> Tim Kilburn
>> Fort McMurray, AB Canada
>> 
>> On Feb 8, 2018, at 12:19, Anders Holmberg > > wrote:
>> 
>> Hi!
>> Well the machines are on the same network but i have the machine i ssh from 
>> connected via cable.
>> THe mac is wirelessly connected.
>> Does it matter if i have both a 2.5 gz and 5Gz network.
>> /A
>> 
>>> 8 feb. 2018 kl. 16:15 skrev Jonathan Cohn >> >:
>>> 
>>> Hello,
>>> 
>>> This message means that the computer you are ssh from does not know the 
>>> correct path to the  10.0.0.0/24 network. So I expect your machines are on 
>>> separate networks or perhaps you are not connected to a network at all for 
>>> the source machine.
>>> 
>>> Generally, for IPv4 what happens when they connect to a network is that the 
>>> machine will do a DHCP query to the all broadcast address 255.255.255.255 
>>> and the DHCP server (usually your router) will respond with a few pieces of 
>>> information.
>>> 
>>> 1. An IP address that your computer can use for a time.
>>> 2. How long until that IP address is available for reassignment.
>>> 3. The address of the default router.
>>> 4. The Netmask of the current network.
>>> 5. The DNS servers to use to translate from names to IP addresses.
>>> 
>>> That default route listed above means that any information not on the local 
>>> network will be sent to the default router to forward onto a different 
>>> network. The default router can do four things with your traffic being 
>>> requested to be sent:
>>> 1. It can forward it to the destination / next router in the path to the 
>>> destination.
>>> 2. It can send back a network unreachable message.
>>> 3. It can send back a host unreachable message.
>>> 4. It can just drop the packet and say nothing back to your computer.
>>> 
>>> If you are getting the network unreachable it means either your system 
>>> doesn’t have a location on your network to send the information addressed  
>>> to the 10.x.x.x network or it forwarded it to a router that gave back a 
>>> message indicating that it could not forward to the 10 network.
>>> 
>>> Now the 10 network is very special. It was the original Arpanet network and 
>>> once Arpanet was disbanded it was not allowed to be routed over the 
>>> Internet, so it is exclusively used as a private network.  
>>> 
>>> I think that is enough of an Internet lesson today.
>>> 
>>> Best wishes,
>>> 
>>> Jonathan Cohn  
 On Feb 8, 2018, at 9:42 AM, Anders Holmberg > wrote:
 
 Hi!
 Ok, more on this thread.
 I typed wrong the first time i did it and that’s why i get the not routed 
 to host message.
 Now when i type ssh andersholmberg@10.0.1.8 
  i get the network is not reacchable.
 Even though the remote login is turned on so i am a bit confused.
 /A
 
> 7 feb. 2018 kl. 21:21 skrev Chris Moore  >:
> 
> Did you allow your mac to accept remote logins?  This is done in system 
> preferences, sharing.  It also shows the format of the ssh command.  This 
> command looks like”:
> ssh user@computer-name
> When prompted for the password you would enter the password for your mac 
> user.
> 
> HTH 
> Chris
> 
>> On Feb 7, 2018, at 2:59 PM, Bill Gallik 

Re: SSH into my mac does not work properly.

[Anders Holmberg]

Hi!
Ok, i can ping from my mac to my Linux machine and no packets get lost.
The other way it works too.
/A

> 8 feb. 2018 kl. 20:47 skrev Tim Kilburn :
> 
> Hi,
> 
> That shouldn't make any difference.  If they are both connected through the 
> same router, and if you haven't configured private networks within the WiFi 
> configurations, then you should be able to talk between devices.
> 
> • determine the IP addresses of each.
> • from the Mac, see if you can ping the Windows box.  To accomplish this in 
> Terminal, type "ping -c 5 IP_Address_of_Windows_Box".  If it answers, then 
> they're seeing each other and there's something else going on.
> 
> Later...
> 
> Tim Kilburn
> Fort McMurray, AB Canada
> 
> On Feb 8, 2018, at 12:19, Anders Holmberg  > wrote:
> 
> Hi!
> Well the machines are on the same network but i have the machine i ssh from 
> connected via cable.
> THe mac is wirelessly connected.
> Does it matter if i have both a 2.5 gz and 5Gz network.
> /A
> 
>> 8 feb. 2018 kl. 16:15 skrev Jonathan Cohn > >:
>> 
>> Hello,
>> 
>> This message means that the computer you are ssh from does not know the 
>> correct path to the  10.0.0.0/24 network. So I expect your machines are on 
>> separate networks or perhaps you are not connected to a network at all for 
>> the source machine.
>> 
>> Generally, for IPv4 what happens when they connect to a network is that the 
>> machine will do a DHCP query to the all broadcast address 255.255.255.255 
>> and the DHCP server (usually your router) will respond with a few pieces of 
>> information.
>> 
>> 1. An IP address that your computer can use for a time.
>> 2. How long until that IP address is available for reassignment.
>> 3. The address of the default router.
>> 4. The Netmask of the current network.
>> 5. The DNS servers to use to translate from names to IP addresses.
>> 
>> That default route listed above means that any information not on the local 
>> network will be sent to the default router to forward onto a different 
>> network. The default router can do four things with your traffic being 
>> requested to be sent:
>> 1. It can forward it to the destination / next router in the path to the 
>> destination.
>> 2. It can send back a network unreachable message.
>> 3. It can send back a host unreachable message.
>> 4. It can just drop the packet and say nothing back to your computer.
>> 
>> If you are getting the network unreachable it means either your system 
>> doesn’t have a location on your network to send the information addressed  
>> to the 10.x.x.x network or it forwarded it to a router that gave back a 
>> message indicating that it could not forward to the 10 network.
>> 
>> Now the 10 network is very special. It was the original Arpanet network and 
>> once Arpanet was disbanded it was not allowed to be routed over the 
>> Internet, so it is exclusively used as a private network.  
>> 
>> I think that is enough of an Internet lesson today.
>> 
>> Best wishes,
>> 
>> Jonathan Cohn  
>>> On Feb 8, 2018, at 9:42 AM, Anders Holmberg >> > wrote:
>>> 
>>> Hi!
>>> Ok, more on this thread.
>>> I typed wrong the first time i did it and that’s why i get the not routed 
>>> to host message.
>>> Now when i type ssh andersholmberg@10.0.1.8 
>>>  i get the network is not reacchable.
>>> Even though the remote login is turned on so i am a bit confused.
>>> /A
>>> 
 7 feb. 2018 kl. 21:21 skrev Chris Moore >:
 
 Did you allow your mac to accept remote logins?  This is done in system 
 preferences, sharing.  It also shows the format of the ssh command.  This 
 command looks like”:
 ssh user@computer-name
 When prompted for the password you would enter the password for your mac 
 user.
 
 HTH 
 Chris
 
> On Feb 7, 2018, at 2:59 PM, Bill Gallik  > wrote:
> 
> I wonder, are you using the  key after typing in your password?
> 
> My thought is that you may need to terminate the password string with a 
> line feed rather than a carriage return (M rather than 
> J).
> 
> It’s been a lot of years since I worked on a UNIX system, but if memory 
> serves me correctly the carriage return and the line feed are treated as 
> different animals.
> 
> I think you may be able to use the line feed by entering M.
> 
> I’d be curious if this helps, please let me know?
> 
> HTH
> 
> 
> - Bill from Ino, Wisconsin
> - "Always acknowledge a fault. This will throw those in authority off 
> their guard and give you an opportunity to commit more."
> - US Humorist, Mark Twain (1835 - 1910)
> 
> On Feb 7, 

Re: SSH into my mac does not work properly.

[Tim Kilburn]

Hi,

First, do you just have one router in your house?  If so, then the quickest way 
to confirm would be to check your IP addresses.  With each device connected to 
the same SSID, check the IP's of each device.  If they all fit in the same 
range of 10.0.1.* for example, then they're all connected to the same subnet.  
Generally, this should work, although there are situations where this method 
won't give you the correct answer, but you'd need multiple AP's or a pretty 
advanced network configuration.

Later...


Tim Kilburn
Fort McMurray, AB Canada

On Feb 9, 2018, at 09:17, Anders Holmberg  wrote:

Hi!
Can i check this somewhere?
I mean the addresses for the 5K and 2.4 GZ networks?
/A

> 8 feb. 2018 kl. 20:45 skrev Jonathan Cohn  >:
> 
> OK, so both your systems are using a 10.0.X.XX network address? Logically 
> your 5K, 2K and wired networks are all separate networks according to IP 
> protocols. It is quite possible that the router you have can “bridge” the 
> networks together to make one logical network The other possibility is to 
> subnet your 10.0. network assuming it is actually your network and not 
> Verizon / Apple / Cox / Infinity network. 
> 
> Then you would route the subnets together at a router. 
> 
> So, you might have 10.0.1 as your 5K network.
> 10.0.2 as your 2K network 
> 10.0.3 as your wired network
> 
> Each of these would have a subnet mask of 255.255.255.0  and then your router 
> would correctly route between them. It all depends on how many devices you 
> have and on what your ISP is doing to you its side of the network. 
> before hand.
> 
> 
>> On Feb 8, 2018, at 2:19 PM, Anders Holmberg > > wrote:
>> 
>> Hi!
>> Well the machines are on the same network but i have the machine i ssh from 
>> connected via cable.
>> THe mac is wirelessly connected.
>> Does it matter if i have both a 2.5 gz and 5Gz network.
>> /A
>> 
>>> 8 feb. 2018 kl. 16:15 skrev Jonathan Cohn >> >:
>>> 
>>> Hello,
>>> 
>>> This message means that the computer you are ssh from does not know the 
>>> correct path to the  10.0.0.0/24 network. So I expect your machines are on 
>>> separate networks or perhaps you are not connected to a network at all for 
>>> the source machine.
>>> 
>>> Generally, for IPv4 what happens when they connect to a network is that the 
>>> machine will do a DHCP query to the all broadcast address 255.255.255.255 
>>> and the DHCP server (usually your router) will respond with a few pieces of 
>>> information.
>>> 
>>> 1. An IP address that your computer can use for a time.
>>> 2. How long until that IP address is available for reassignment.
>>> 3. The address of the default router.
>>> 4. The Netmask of the current network.
>>> 5. The DNS servers to use to translate from names to IP addresses.
>>> 
>>> That default route listed above means that any information not on the local 
>>> network will be sent to the default router to forward onto a different 
>>> network. The default router can do four things with your traffic being 
>>> requested to be sent:
>>> 1. It can forward it to the destination / next router in the path to the 
>>> destination.
>>> 2. It can send back a network unreachable message.
>>> 3. It can send back a host unreachable message.
>>> 4. It can just drop the packet and say nothing back to your computer.
>>> 
>>> If you are getting the network unreachable it means either your system 
>>> doesn’t have a location on your network to send the information addressed  
>>> to the 10.x.x.x network or it forwarded it to a router that gave back a 
>>> message indicating that it could not forward to the 10 network.
>>> 
>>> Now the 10 network is very special. It was the original Arpanet network and 
>>> once Arpanet was disbanded it was not allowed to be routed over the 
>>> Internet, so it is exclusively used as a private network.  
>>> 
>>> I think that is enough of an Internet lesson today.
>>> 
>>> Best wishes,
>>> 
>>> Jonathan Cohn  
 On Feb 8, 2018, at 9:42 AM, Anders Holmberg > wrote:
 
 Hi!
 Ok, more on this thread.
 I typed wrong the first time i did it and that’s why i get the not routed 
 to host message.
 Now when i type ssh andersholmberg@10.0.1.8 
  i get the network is not reacchable.
 Even though the remote login is turned on so i am a bit confused.
 /A
 
> 7 feb. 2018 kl. 21:21 skrev Chris Moore  >:
> 
> Did you allow your mac to accept remote logins?  This is done in system 
> preferences, sharing.  It also shows the format of the ssh command.  This 
> command looks like”:
> ssh user@computer-name
> When prompted for the password you would enter the password 

Re: SSH into my mac does not work properly.

[Anders Holmberg]

Hi!
Can i check this somewhere?
I mean the addresses for the 5K and 2.4 GZ networks?
/A

> 8 feb. 2018 kl. 20:45 skrev Jonathan Cohn :
> 
> OK, so both your systems are using a 10.0.X.XX network address? Logically 
> your 5K, 2K and wired networks are all separate networks according to IP 
> protocols. It is quite possible that the router you have can “bridge” the 
> networks together to make one logical network The other possibility is to 
> subnet your 10.0. network assuming it is actually your network and not 
> Verizon / Apple / Cox / Infinity network. 
> 
> Then you would route the subnets together at a router. 
> 
> So, you might have 10.0.1 as your 5K network.
> 10.0.2 as your 2K network 
> 10.0.3 as your wired network
> 
> Each of these would have a subnet mask of 255.255.255.0  and then your router 
> would correctly route between them. It all depends on how many devices you 
> have and on what your ISP is doing to you its side of the network. 
> before hand.
> 
> 
>> On Feb 8, 2018, at 2:19 PM, Anders Holmberg > > wrote:
>> 
>> Hi!
>> Well the machines are on the same network but i have the machine i ssh from 
>> connected via cable.
>> THe mac is wirelessly connected.
>> Does it matter if i have both a 2.5 gz and 5Gz network.
>> /A
>> 
>>> 8 feb. 2018 kl. 16:15 skrev Jonathan Cohn >> >:
>>> 
>>> Hello,
>>> 
>>> This message means that the computer you are ssh from does not know the 
>>> correct path to the  10.0.0.0/24 network. So I expect your machines are on 
>>> separate networks or perhaps you are not connected to a network at all for 
>>> the source machine.
>>> 
>>> Generally, for IPv4 what happens when they connect to a network is that the 
>>> machine will do a DHCP query to the all broadcast address 255.255.255.255 
>>> and the DHCP server (usually your router) will respond with a few pieces of 
>>> information.
>>> 
>>> 1. An IP address that your computer can use for a time.
>>> 2. How long until that IP address is available for reassignment.
>>> 3. The address of the default router.
>>> 4. The Netmask of the current network.
>>> 5. The DNS servers to use to translate from names to IP addresses.
>>> 
>>> That default route listed above means that any information not on the local 
>>> network will be sent to the default router to forward onto a different 
>>> network. The default router can do four things with your traffic being 
>>> requested to be sent:
>>> 1. It can forward it to the destination / next router in the path to the 
>>> destination.
>>> 2. It can send back a network unreachable message.
>>> 3. It can send back a host unreachable message.
>>> 4. It can just drop the packet and say nothing back to your computer.
>>> 
>>> If you are getting the network unreachable it means either your system 
>>> doesn’t have a location on your network to send the information addressed  
>>> to the 10.x.x.x network or it forwarded it to a router that gave back a 
>>> message indicating that it could not forward to the 10 network.
>>> 
>>> Now the 10 network is very special. It was the original Arpanet network and 
>>> once Arpanet was disbanded it was not allowed to be routed over the 
>>> Internet, so it is exclusively used as a private network.  
>>> 
>>> I think that is enough of an Internet lesson today.
>>> 
>>> Best wishes,
>>> 
>>> Jonathan Cohn  
 On Feb 8, 2018, at 9:42 AM, Anders Holmberg > wrote:
 
 Hi!
 Ok, more on this thread.
 I typed wrong the first time i did it and that’s why i get the not routed 
 to host message.
 Now when i type ssh andersholmberg@10.0.1.8 
  i get the network is not reacchable.
 Even though the remote login is turned on so i am a bit confused.
 /A
 
> 7 feb. 2018 kl. 21:21 skrev Chris Moore  >:
> 
> Did you allow your mac to accept remote logins?  This is done in system 
> preferences, sharing.  It also shows the format of the ssh command.  This 
> command looks like”:
> ssh user@computer-name
> When prompted for the password you would enter the password for your mac 
> user.
> 
> HTH 
> Chris
> 
>> On Feb 7, 2018, at 2:59 PM, Bill Gallik > > wrote:
>> 
>> I wonder, are you using the  key after typing in your password?
>> 
>> My thought is that you may need to terminate the password string with a 
>> line feed rather than a carriage return (M rather than 
>> J).
>> 
>> It’s been a lot of years since I worked on a UNIX system, but if memory 
>> serves me correctly the carriage return and the line feed are treated as 
>> different animals.
>> 
>> I think you may be able to use the line 

Re: SSH into my mac does not work properly.

[Tim Kilburn]

Yes, and that's what was suggested in an earlier post.

Later...

Tim Kilburn
Fort McMurray, AB Canada

On Feb 8, 2018, at 14:49, 'Jason White' via MacVisionaries 
 wrote:

Tim Kilburn  wrote:

> Conflicting but not.  As you've mentioned, if there's multiple routers, then 
> it's possible that alternative networks are being created so that 
> connectivity is complicated.  Although, in a perfect world, if everything is 
> going through one Access Point using a basic, default style of configuration, 
> whether devices are connected wirelessly or via ethernet, and whether 2.4 G 
> or 5 G, DHCP services should be handing out through a single subnet, so 
> connections between devices should be possible.


So the question is, can you ping one host from the other?

-- 
The following information is important for all members of the Mac Visionaries 
list.

If you have any questions or concerns about the running of this list, or if you 
feel that a member's post is inappropriate, please contact the owners or 
moderators directly rather than posting on the list itself.

Your Mac Visionaries list moderator is Mark Taylor.  You can reach mark at:  
mk...@ucla.edu and your owner is Cara Quinn - you can reach Cara at 
caraqu...@caraquinn.com

The archives for this list can be searched at:
http://www.mail-archive.com/macvisionaries@googlegroups.com/
--- 
You received this message because you are subscribed to the Google Groups 
"MacVisionaries" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to macvisionaries+unsubscr...@googlegroups.com.
To post to this group, send email to macvisionaries@googlegroups.com.
Visit this group at https://groups.google.com/group/macvisionaries.
For more options, visit https://groups.google.com/d/optout.

-- 
The following information is important for all members of the Mac Visionaries 
list.

If you have any questions or concerns about the running of this list, or if you 
feel that a member's post is inappropriate, please contact the owners or 
moderators directly rather than posting on the list itself.

Your Mac Visionaries list moderator is Mark Taylor.  You can reach mark at:  
mk...@ucla.edu and your owner is Cara Quinn - you can reach Cara at 
caraqu...@caraquinn.com

The archives for this list can be searched at:
http://www.mail-archive.com/macvisionaries@googlegroups.com/
--- 
You received this message because you are subscribed to the Google Groups 
"MacVisionaries" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to macvisionaries+unsubscr...@googlegroups.com.
To post to this group, send email to macvisionaries@googlegroups.com.
Visit this group at https://groups.google.com/group/macvisionaries.
For more options, visit https://groups.google.com/d/optout.

Re: SSH into my mac does not work properly.

['Jason White' via MacVisionaries]

Tim Kilburn  wrote:
 
> Conflicting but not.  As you've mentioned, if there's multiple routers, then 
> it's possible that alternative networks are being created so that 
> connectivity is complicated.  Although, in a perfect world, if everything is 
> going through one Access Point using a basic, default style of configuration, 
> whether devices are connected wirelessly or via ethernet, and whether 2.4 G 
> or 5 G, DHCP services should be handing out through a single subnet, so 
> connections between devices should be possible.


So the question is, can you ping one host from the other?

-- 
The following information is important for all members of the Mac Visionaries 
list.

If you have any questions or concerns about the running of this list, or if you 
feel that a member's post is inappropriate, please contact the owners or 
moderators directly rather than posting on the list itself.

Your Mac Visionaries list moderator is Mark Taylor.  You can reach mark at:  
mk...@ucla.edu and your owner is Cara Quinn - you can reach Cara at 
caraqu...@caraquinn.com

The archives for this list can be searched at:
http://www.mail-archive.com/macvisionaries@googlegroups.com/
--- 
You received this message because you are subscribed to the Google Groups 
"MacVisionaries" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to macvisionaries+unsubscr...@googlegroups.com.
To post to this group, send email to macvisionaries@googlegroups.com.
Visit this group at https://groups.google.com/group/macvisionaries.
For more options, visit https://groups.google.com/d/optout.

Re: SSH into my mac does not work properly.

[Tim Kilburn]

Hi,

Conflicting but not.  As you've mentioned, if there's multiple routers, then 
it's possible that alternative networks are being created so that connectivity 
is complicated.  Although, in a perfect world, if everything is going through 
one Access Point using a basic, default style of configuration, whether devices 
are connected wirelessly or via ethernet, and whether 2.4 G or 5 G, DHCP 
services should be handing out through a single subnet, so connections between 
devices should be possible.

Later...

Tim Kilburn
Fort McMurray, AB Canada

On Feb 8, 2018, at 12:53, Jonathan Cohn  wrote:

Well, you gave conflicting information from what I did.  So to be clear your 
statement is probably right as long as there is exactly one device providing 
all network connectivity. 

But perhaps we will learn more soon about the number of access points and 
routers that he has. 

> On Feb 8, 2018, at 2:47 PM, Tim Kilburn  > wrote:
> 
> Hi,
> 
> That shouldn't make any difference.  If they are both connected through the 
> same router, and if you haven't configured private networks within the WiFi 
> configurations, then you should be able to talk between devices.
> 
> • determine the IP addresses of each.
> • from the Mac, see if you can ping the Windows box.  To accomplish this in 
> Terminal, type "ping -c 5 IP_Address_of_Windows_Box".  If it answers, then 
> they're seeing each other and there's something else going on.
> 
> Later...
> 
> Tim Kilburn
> Fort McMurray, AB Canada
> 
> On Feb 8, 2018, at 12:19, Anders Holmberg  > wrote:
> 
> Hi!
> Well the machines are on the same network but i have the machine i ssh from 
> connected via cable.
> THe mac is wirelessly connected.
> Does it matter if i have both a 2.5 gz and 5Gz network.
> /A
> 
>> 8 feb. 2018 kl. 16:15 skrev Jonathan Cohn > >:
>> 
>> Hello,
>> 
>> This message means that the computer you are ssh from does not know the 
>> correct path to the  10.0.0.0/24 network. So I expect your machines are on 
>> separate networks or perhaps you are not connected to a network at all for 
>> the source machine.
>> 
>> Generally, for IPv4 what happens when they connect to a network is that the 
>> machine will do a DHCP query to the all broadcast address 255.255.255.255 
>> and the DHCP server (usually your router) will respond with a few pieces of 
>> information.
>> 
>> 1. An IP address that your computer can use for a time.
>> 2. How long until that IP address is available for reassignment.
>> 3. The address of the default router.
>> 4. The Netmask of the current network.
>> 5. The DNS servers to use to translate from names to IP addresses.
>> 
>> That default route listed above means that any information not on the local 
>> network will be sent to the default router to forward onto a different 
>> network. The default router can do four things with your traffic being 
>> requested to be sent:
>> 1. It can forward it to the destination / next router in the path to the 
>> destination.
>> 2. It can send back a network unreachable message.
>> 3. It can send back a host unreachable message.
>> 4. It can just drop the packet and say nothing back to your computer.
>> 
>> If you are getting the network unreachable it means either your system 
>> doesn’t have a location on your network to send the information addressed  
>> to the 10.x.x.x network or it forwarded it to a router that gave back a 
>> message indicating that it could not forward to the 10 network.
>> 
>> Now the 10 network is very special. It was the original Arpanet network and 
>> once Arpanet was disbanded it was not allowed to be routed over the 
>> Internet, so it is exclusively used as a private network.  
>> 
>> I think that is enough of an Internet lesson today.
>> 
>> Best wishes,
>> 
>> Jonathan Cohn  
>>> On Feb 8, 2018, at 9:42 AM, Anders Holmberg >> > wrote:
>>> 
>>> Hi!
>>> Ok, more on this thread.
>>> I typed wrong the first time i did it and that’s why i get the not routed 
>>> to host message.
>>> Now when i type ssh andersholmberg@10.0.1.8 
>>>  i get the network is not reacchable.
>>> Even though the remote login is turned on so i am a bit confused.
>>> /A
>>> 
 7 feb. 2018 kl. 21:21 skrev Chris Moore >:
 
 Did you allow your mac to accept remote logins?  This is done in system 
 preferences, sharing.  It also shows the format of the ssh command.  This 
 command looks like”:
 ssh user@computer-name
 When prompted for the password you would enter the password for your mac 
 user.
 
 HTH 
 Chris
 
> On Feb 7, 2018, at 2:59 PM, Bill Gallik  > wrote:
> 
> I 

Re: SSH into my mac does not work properly.

[Jonathan Cohn]

Well, you gave conflicting information from what I did.  So to be clear your 
statement is probably right as long as there is exactly one device providing 
all network connectivity. 

But perhaps we will learn more soon about the number of access points and 
routers that he has. 

> On Feb 8, 2018, at 2:47 PM, Tim Kilburn  wrote:
> 
> Hi,
> 
> That shouldn't make any difference.  If they are both connected through the 
> same router, and if you haven't configured private networks within the WiFi 
> configurations, then you should be able to talk between devices.
> 
> • determine the IP addresses of each.
> • from the Mac, see if you can ping the Windows box.  To accomplish this in 
> Terminal, type "ping -c 5 IP_Address_of_Windows_Box".  If it answers, then 
> they're seeing each other and there's something else going on.
> 
> Later...
> 
> Tim Kilburn
> Fort McMurray, AB Canada
> 
> On Feb 8, 2018, at 12:19, Anders Holmberg  > wrote:
> 
> Hi!
> Well the machines are on the same network but i have the machine i ssh from 
> connected via cable.
> THe mac is wirelessly connected.
> Does it matter if i have both a 2.5 gz and 5Gz network.
> /A
> 
>> 8 feb. 2018 kl. 16:15 skrev Jonathan Cohn > >:
>> 
>> Hello,
>> 
>> This message means that the computer you are ssh from does not know the 
>> correct path to the  10.0.0.0/24 network. So I expect your machines are on 
>> separate networks or perhaps you are not connected to a network at all for 
>> the source machine.
>> 
>> Generally, for IPv4 what happens when they connect to a network is that the 
>> machine will do a DHCP query to the all broadcast address 255.255.255.255 
>> and the DHCP server (usually your router) will respond with a few pieces of 
>> information.
>> 
>> 1. An IP address that your computer can use for a time.
>> 2. How long until that IP address is available for reassignment.
>> 3. The address of the default router.
>> 4. The Netmask of the current network.
>> 5. The DNS servers to use to translate from names to IP addresses.
>> 
>> That default route listed above means that any information not on the local 
>> network will be sent to the default router to forward onto a different 
>> network. The default router can do four things with your traffic being 
>> requested to be sent:
>> 1. It can forward it to the destination / next router in the path to the 
>> destination.
>> 2. It can send back a network unreachable message.
>> 3. It can send back a host unreachable message.
>> 4. It can just drop the packet and say nothing back to your computer.
>> 
>> If you are getting the network unreachable it means either your system 
>> doesn’t have a location on your network to send the information addressed  
>> to the 10.x.x.x network or it forwarded it to a router that gave back a 
>> message indicating that it could not forward to the 10 network.
>> 
>> Now the 10 network is very special. It was the original Arpanet network and 
>> once Arpanet was disbanded it was not allowed to be routed over the 
>> Internet, so it is exclusively used as a private network.  
>> 
>> I think that is enough of an Internet lesson today.
>> 
>> Best wishes,
>> 
>> Jonathan Cohn  
>>> On Feb 8, 2018, at 9:42 AM, Anders Holmberg >> > wrote:
>>> 
>>> Hi!
>>> Ok, more on this thread.
>>> I typed wrong the first time i did it and that’s why i get the not routed 
>>> to host message.
>>> Now when i type ssh andersholmberg@10.0.1.8 
>>>  i get the network is not reacchable.
>>> Even though the remote login is turned on so i am a bit confused.
>>> /A
>>> 
 7 feb. 2018 kl. 21:21 skrev Chris Moore >:
 
 Did you allow your mac to accept remote logins?  This is done in system 
 preferences, sharing.  It also shows the format of the ssh command.  This 
 command looks like”:
 ssh user@computer-name
 When prompted for the password you would enter the password for your mac 
 user.
 
 HTH 
 Chris
 
> On Feb 7, 2018, at 2:59 PM, Bill Gallik  > wrote:
> 
> I wonder, are you using the  key after typing in your password?
> 
> My thought is that you may need to terminate the password string with a 
> line feed rather than a carriage return (M rather than 
> J).
> 
> It’s been a lot of years since I worked on a UNIX system, but if memory 
> serves me correctly the carriage return and the line feed are treated as 
> different animals.
> 
> I think you may be able to use the line feed by entering M.
> 
> I’d be curious if this helps, please let me know?
> 
> HTH
> 
> 
> - Bill from Ino, Wisconsin
> - "Always acknowledge a 

Re: SSH into my mac does not work properly.

[Tim Kilburn]

Hi,

That shouldn't make any difference.  If they are both connected through the 
same router, and if you haven't configured private networks within the WiFi 
configurations, then you should be able to talk between devices.

• determine the IP addresses of each.
• from the Mac, see if you can ping the Windows box.  To accomplish this in 
Terminal, type "ping -c 5 IP_Address_of_Windows_Box".  If it answers, then 
they're seeing each other and there's something else going on.

Later...

Tim Kilburn
Fort McMurray, AB Canada

On Feb 8, 2018, at 12:19, Anders Holmberg  wrote:

Hi!
Well the machines are on the same network but i have the machine i ssh from 
connected via cable.
THe mac is wirelessly connected.
Does it matter if i have both a 2.5 gz and 5Gz network.
/A

> 8 feb. 2018 kl. 16:15 skrev Jonathan Cohn  >:
> 
> Hello,
> 
> This message means that the computer you are ssh from does not know the 
> correct path to the  10.0.0.0/24 network. So I expect your machines are on 
> separate networks or perhaps you are not connected to a network at all for 
> the source machine.
> 
> Generally, for IPv4 what happens when they connect to a network is that the 
> machine will do a DHCP query to the all broadcast address 255.255.255.255 and 
> the DHCP server (usually your router) will respond with a few pieces of 
> information.
> 
> 1. An IP address that your computer can use for a time.
> 2. How long until that IP address is available for reassignment.
> 3. The address of the default router.
> 4. The Netmask of the current network.
> 5. The DNS servers to use to translate from names to IP addresses.
> 
> That default route listed above means that any information not on the local 
> network will be sent to the default router to forward onto a different 
> network. The default router can do four things with your traffic being 
> requested to be sent:
> 1. It can forward it to the destination / next router in the path to the 
> destination.
> 2. It can send back a network unreachable message.
> 3. It can send back a host unreachable message.
> 4. It can just drop the packet and say nothing back to your computer.
> 
> If you are getting the network unreachable it means either your system 
> doesn’t have a location on your network to send the information addressed  to 
> the 10.x.x.x network or it forwarded it to a router that gave back a message 
> indicating that it could not forward to the 10 network.
> 
> Now the 10 network is very special. It was the original Arpanet network and 
> once Arpanet was disbanded it was not allowed to be routed over the Internet, 
> so it is exclusively used as a private network.  
> 
> I think that is enough of an Internet lesson today.
> 
> Best wishes,
> 
> Jonathan Cohn  
>> On Feb 8, 2018, at 9:42 AM, Anders Holmberg > > wrote:
>> 
>> Hi!
>> Ok, more on this thread.
>> I typed wrong the first time i did it and that’s why i get the not routed to 
>> host message.
>> Now when i type ssh andersholmberg@10.0.1.8  
>> i get the network is not reacchable.
>> Even though the remote login is turned on so i am a bit confused.
>> /A
>> 
>>> 7 feb. 2018 kl. 21:21 skrev Chris Moore >> >:
>>> 
>>> Did you allow your mac to accept remote logins?  This is done in system 
>>> preferences, sharing.  It also shows the format of the ssh command.  This 
>>> command looks like”:
>>> ssh user@computer-name
>>> When prompted for the password you would enter the password for your mac 
>>> user.
>>> 
>>> HTH 
>>> Chris
>>> 
 On Feb 7, 2018, at 2:59 PM, Bill Gallik > wrote:
 
 I wonder, are you using the  key after typing in your password?
 
 My thought is that you may need to terminate the password string with a 
 line feed rather than a carriage return (M rather than 
 J).
 
 It’s been a lot of years since I worked on a UNIX system, but if memory 
 serves me correctly the carriage return and the line feed are treated as 
 different animals.
 
 I think you may be able to use the line feed by entering M.
 
 I’d be curious if this helps, please let me know?
 
 HTH
 
 
 - Bill from Ino, Wisconsin
 - "Always acknowledge a fault. This will throw those in authority off 
 their guard and give you an opportunity to commit more."
 - US Humorist, Mark Twain (1835 - 1910)
 
 On Feb 7, 2018, at 1:37 PM, Anders Holmberg > wrote:
 
 Hi!
 I have a Linux machine with braille and i want to perform tasks on my 
 macbook air using ssh from that linux machine since terminal and voiceover 
 isn’t the best combination.
 I have not compiled brltty yet onto the mac 

Re: SSH into my mac does not work properly.

[Jonathan Cohn]

OK, so both your systems are using a 10.0.X.XX network address? Logically your 
5K, 2K and wired networks are all separate networks according to IP protocols. 
It is quite possible that the router you have can “bridge” the networks 
together to make one logical network The other possibility is to subnet your 
10.0. network assuming it is actually your network and not Verizon / Apple / 
Cox / Infinity network. 

Then you would route the subnets together at a router. 

So, you might have 10.0.1 as your 5K network.
10.0.2 as your 2K network 
10.0.3 as your wired network

Each of these would have a subnet mask of 255.255.255.0  and then your router 
would correctly route between them. It all depends on how many devices you have 
and on what your ISP is doing to you its side of the network. 
before hand.


> On Feb 8, 2018, at 2:19 PM, Anders Holmberg  wrote:
> 
> Hi!
> Well the machines are on the same network but i have the machine i ssh from 
> connected via cable.
> THe mac is wirelessly connected.
> Does it matter if i have both a 2.5 gz and 5Gz network.
> /A
> 
>> 8 feb. 2018 kl. 16:15 skrev Jonathan Cohn > >:
>> 
>> Hello,
>> 
>> This message means that the computer you are ssh from does not know the 
>> correct path to the  10.0.0.0/24 network. So I expect your machines are on 
>> separate networks or perhaps you are not connected to a network at all for 
>> the source machine.
>> 
>> Generally, for IPv4 what happens when they connect to a network is that the 
>> machine will do a DHCP query to the all broadcast address 255.255.255.255 
>> and the DHCP server (usually your router) will respond with a few pieces of 
>> information.
>> 
>> 1. An IP address that your computer can use for a time.
>> 2. How long until that IP address is available for reassignment.
>> 3. The address of the default router.
>> 4. The Netmask of the current network.
>> 5. The DNS servers to use to translate from names to IP addresses.
>> 
>> That default route listed above means that any information not on the local 
>> network will be sent to the default router to forward onto a different 
>> network. The default router can do four things with your traffic being 
>> requested to be sent:
>> 1. It can forward it to the destination / next router in the path to the 
>> destination.
>> 2. It can send back a network unreachable message.
>> 3. It can send back a host unreachable message.
>> 4. It can just drop the packet and say nothing back to your computer.
>> 
>> If you are getting the network unreachable it means either your system 
>> doesn’t have a location on your network to send the information addressed  
>> to the 10.x.x.x network or it forwarded it to a router that gave back a 
>> message indicating that it could not forward to the 10 network.
>> 
>> Now the 10 network is very special. It was the original Arpanet network and 
>> once Arpanet was disbanded it was not allowed to be routed over the 
>> Internet, so it is exclusively used as a private network.  
>> 
>> I think that is enough of an Internet lesson today.
>> 
>> Best wishes,
>> 
>> Jonathan Cohn  
>>> On Feb 8, 2018, at 9:42 AM, Anders Holmberg >> > wrote:
>>> 
>>> Hi!
>>> Ok, more on this thread.
>>> I typed wrong the first time i did it and that’s why i get the not routed 
>>> to host message.
>>> Now when i type ssh andersholmberg@10.0.1.8 
>>>  i get the network is not reacchable.
>>> Even though the remote login is turned on so i am a bit confused.
>>> /A
>>> 
 7 feb. 2018 kl. 21:21 skrev Chris Moore >:
 
 Did you allow your mac to accept remote logins?  This is done in system 
 preferences, sharing.  It also shows the format of the ssh command.  This 
 command looks like”:
 ssh user@computer-name
 When prompted for the password you would enter the password for your mac 
 user.
 
 HTH 
 Chris
 
> On Feb 7, 2018, at 2:59 PM, Bill Gallik  > wrote:
> 
> I wonder, are you using the  key after typing in your password?
> 
> My thought is that you may need to terminate the password string with a 
> line feed rather than a carriage return (M rather than 
> J).
> 
> It’s been a lot of years since I worked on a UNIX system, but if memory 
> serves me correctly the carriage return and the line feed are treated as 
> different animals.
> 
> I think you may be able to use the line feed by entering M.
> 
> I’d be curious if this helps, please let me know?
> 
> HTH
> 
> 
> - Bill from Ino, Wisconsin
> - "Always acknowledge a fault. This will throw those in authority off 
> their guard and give you an opportunity to commit more."
> - US Humorist, 

Re: SSH into my mac does not work properly.

[Anders Holmberg]

Hi!
Well the machines are on the same network but i have the machine i ssh from 
connected via cable.
THe mac is wirelessly connected.
Does it matter if i have both a 2.5 gz and 5Gz network.
/A

> 8 feb. 2018 kl. 16:15 skrev Jonathan Cohn :
> 
> Hello,
> 
> This message means that the computer you are ssh from does not know the 
> correct path to the  10.0.0.0/24 network. So I expect your machines are on 
> separate networks or perhaps you are not connected to a network at all for 
> the source machine.
> 
> Generally, for IPv4 what happens when they connect to a network is that the 
> machine will do a DHCP query to the all broadcast address 255.255.255.255 and 
> the DHCP server (usually your router) will respond with a few pieces of 
> information.
> 
> 1. An IP address that your computer can use for a time.
> 2. How long until that IP address is available for reassignment.
> 3. The address of the default router.
> 4. The Netmask of the current network.
> 5. The DNS servers to use to translate from names to IP addresses.
> 
> That default route listed above means that any information not on the local 
> network will be sent to the default router to forward onto a different 
> network. The default router can do four things with your traffic being 
> requested to be sent:
> 1. It can forward it to the destination / next router in the path to the 
> destination.
> 2. It can send back a network unreachable message.
> 3. It can send back a host unreachable message.
> 4. It can just drop the packet and say nothing back to your computer.
> 
> If you are getting the network unreachable it means either your system 
> doesn’t have a location on your network to send the information addressed  to 
> the 10.x.x.x network or it forwarded it to a router that gave back a message 
> indicating that it could not forward to the 10 network.
> 
> Now the 10 network is very special. It was the original Arpanet network and 
> once Arpanet was disbanded it was not allowed to be routed over the Internet, 
> so it is exclusively used as a private network.  
> 
> I think that is enough of an Internet lesson today.
> 
> Best wishes,
> 
> Jonathan Cohn  
>> On Feb 8, 2018, at 9:42 AM, Anders Holmberg > > wrote:
>> 
>> Hi!
>> Ok, more on this thread.
>> I typed wrong the first time i did it and that’s why i get the not routed to 
>> host message.
>> Now when i type ssh andersholmberg@10.0.1.8  
>> i get the network is not reacchable.
>> Even though the remote login is turned on so i am a bit confused.
>> /A
>> 
>>> 7 feb. 2018 kl. 21:21 skrev Chris Moore >> >:
>>> 
>>> Did you allow your mac to accept remote logins?  This is done in system 
>>> preferences, sharing.  It also shows the format of the ssh command.  This 
>>> command looks like”:
>>> ssh user@computer-name
>>> When prompted for the password you would enter the password for your mac 
>>> user.
>>> 
>>> HTH 
>>> Chris
>>> 
 On Feb 7, 2018, at 2:59 PM, Bill Gallik > wrote:
 
 I wonder, are you using the  key after typing in your password?
 
 My thought is that you may need to terminate the password string with a 
 line feed rather than a carriage return (M rather than 
 J).
 
 It’s been a lot of years since I worked on a UNIX system, but if memory 
 serves me correctly the carriage return and the line feed are treated as 
 different animals.
 
 I think you may be able to use the line feed by entering M.
 
 I’d be curious if this helps, please let me know?
 
 HTH
 
 
 - Bill from Ino, Wisconsin
 - "Always acknowledge a fault. This will throw those in authority off 
 their guard and give you an opportunity to commit more."
 - US Humorist, Mark Twain (1835 - 1910)
 
 On Feb 7, 2018, at 1:37 PM, Anders Holmberg > wrote:
 
 Hi!
 I have a Linux machine with braille and i want to perform tasks on my 
 macbook air using ssh from that linux machine since terminal and voiceover 
 isn’t the best combination.
 I have not compiled brltty yet onto the mac so i have to ssh into it.
 However when i type ssh and then the ip addres i am asked for the password.
 I enter the password and press enter.
 Then i am asked for the password again and i enter it again and so on.
 I know there’s something wrong i do but i can not figure out what.
 SSH is not blocked on my network so it should work.
 I am not really familiar with setting up public keys even though this 
 might be the best.
 Can anyone please help me out?
 Thanks in advance.
 /A
 
 -- 
 The following information is important for all members of the Mac 
 Visionaries list.

Re: SSH into my mac does not work properly.

[Jonathan Cohn]

Hello,

This message means that the computer you are ssh from does not know the correct 
path to the  10.0.0.0/24 network. So I expect your machines are on separate 
networks or perhaps you are not connected to a network at all for the source 
machine.

Generally, for IPv4 what happens when they connect to a network is that the 
machine will do a DHCP query to the all broadcast address 255.255.255.255 and 
the DHCP server (usually your router) will respond with a few pieces of 
information.

1. An IP address that your computer can use for a time.
2. How long until that IP address is available for reassignment.
3. The address of the default router.
4. The Netmask of the current network.
5. The DNS servers to use to translate from names to IP addresses.

That default route listed above means that any information not on the local 
network will be sent to the default router to forward onto a different network. 
The default router can do four things with your traffic being requested to be 
sent:
1. It can forward it to the destination / next router in the path to the 
destination.
2. It can send back a network unreachable message.
3. It can send back a host unreachable message.
4. It can just drop the packet and say nothing back to your computer.

If you are getting the network unreachable it means either your system doesn’t 
have a location on your network to send the information addressed  to the 
10.x.x.x network or it forwarded it to a router that gave back a message 
indicating that it could not forward to the 10 network.

Now the 10 network is very special. It was the original Arpanet network and 
once Arpanet was disbanded it was not allowed to be routed over the Internet, 
so it is exclusively used as a private network.  

I think that is enough of an Internet lesson today.

Best wishes,

Jonathan Cohn  
> On Feb 8, 2018, at 9:42 AM, Anders Holmberg  wrote:
> 
> Hi!
> Ok, more on this thread.
> I typed wrong the first time i did it and that’s why i get the not routed to 
> host message.
> Now when i type ssh andersholmberg@10.0.1.8  
> i get the network is not reacchable.
> Even though the remote login is turned on so i am a bit confused.
> /A
> 
>> 7 feb. 2018 kl. 21:21 skrev Chris Moore > >:
>> 
>> Did you allow your mac to accept remote logins?  This is done in system 
>> preferences, sharing.  It also shows the format of the ssh command.  This 
>> command looks like”:
>> ssh user@computer-name
>> When prompted for the password you would enter the password for your mac 
>> user.
>> 
>> HTH 
>> Chris
>> 
>>> On Feb 7, 2018, at 2:59 PM, Bill Gallik >> > wrote:
>>> 
>>> I wonder, are you using the  key after typing in your password?
>>> 
>>> My thought is that you may need to terminate the password string with a 
>>> line feed rather than a carriage return (M rather than J).
>>> 
>>> It’s been a lot of years since I worked on a UNIX system, but if memory 
>>> serves me correctly the carriage return and the line feed are treated as 
>>> different animals.
>>> 
>>> I think you may be able to use the line feed by entering M.
>>> 
>>> I’d be curious if this helps, please let me know?
>>> 
>>> HTH
>>> 
>>> 
>>> - Bill from Ino, Wisconsin
>>> - "Always acknowledge a fault. This will throw those in authority off their 
>>> guard and give you an opportunity to commit more."
>>> - US Humorist, Mark Twain (1835 - 1910)
>>> 
>>> On Feb 7, 2018, at 1:37 PM, Anders Holmberg >> > wrote:
>>> 
>>> Hi!
>>> I have a Linux machine with braille and i want to perform tasks on my 
>>> macbook air using ssh from that linux machine since terminal and voiceover 
>>> isn’t the best combination.
>>> I have not compiled brltty yet onto the mac so i have to ssh into it.
>>> However when i type ssh and then the ip addres i am asked for the password.
>>> I enter the password and press enter.
>>> Then i am asked for the password again and i enter it again and so on.
>>> I know there’s something wrong i do but i can not figure out what.
>>> SSH is not blocked on my network so it should work.
>>> I am not really familiar with setting up public keys even though this might 
>>> be the best.
>>> Can anyone please help me out?
>>> Thanks in advance.
>>> /A
>>> 
>>> -- 
>>> The following information is important for all members of the Mac 
>>> Visionaries list.
>>> 
>>> If you have any questions or concerns about the running of this list, or if 
>>> you feel that a member's post is inappropriate, please contact the owners 
>>> or moderators directly rather than posting on the list itself.
>>> 
>>> Your Mac Visionaries list moderator is Mark Taylor.  You can reach mark at: 
>>>  macvisionaries+modera...@googlegroups.com 
>>>  and your owner is Cara 
>>> Quinn - you 

Re: SSH into my mac does not work properly.

[Anders Holmberg]

Hi!
Ok, more on this thread.
I typed wrong the first time i did it and that’s why i get the not routed to 
host message.
Now when i type ssh andersholmberg@10.0.1.8  i 
get the network is not reacchable.
Even though the remote login is turned on so i am a bit confused.
/A

> 7 feb. 2018 kl. 21:21 skrev Chris Moore :
> 
> Did you allow your mac to accept remote logins?  This is done in system 
> preferences, sharing.  It also shows the format of the ssh command.  This 
> command looks like”:
> ssh user@computer-name
> When prompted for the password you would enter the password for your mac user.
> 
> HTH 
> Chris
> 
>> On Feb 7, 2018, at 2:59 PM, Bill Gallik > > wrote:
>> 
>> I wonder, are you using the  key after typing in your password?
>> 
>> My thought is that you may need to terminate the password string with a line 
>> feed rather than a carriage return (M rather than J).
>> 
>> It’s been a lot of years since I worked on a UNIX system, but if memory 
>> serves me correctly the carriage return and the line feed are treated as 
>> different animals.
>> 
>> I think you may be able to use the line feed by entering M.
>> 
>> I’d be curious if this helps, please let me know?
>> 
>> HTH
>> 
>> 
>> - Bill from Ino, Wisconsin
>> - "Always acknowledge a fault. This will throw those in authority off their 
>> guard and give you an opportunity to commit more."
>> - US Humorist, Mark Twain (1835 - 1910)
>> 
>> On Feb 7, 2018, at 1:37 PM, Anders Holmberg > > wrote:
>> 
>> Hi!
>> I have a Linux machine with braille and i want to perform tasks on my 
>> macbook air using ssh from that linux machine since terminal and voiceover 
>> isn’t the best combination.
>> I have not compiled brltty yet onto the mac so i have to ssh into it.
>> However when i type ssh and then the ip addres i am asked for the password.
>> I enter the password and press enter.
>> Then i am asked for the password again and i enter it again and so on.
>> I know there’s something wrong i do but i can not figure out what.
>> SSH is not blocked on my network so it should work.
>> I am not really familiar with setting up public keys even though this might 
>> be the best.
>> Can anyone please help me out?
>> Thanks in advance.
>> /A
>> 
>> -- 
>> The following information is important for all members of the Mac 
>> Visionaries list.
>> 
>> If you have any questions or concerns about the running of this list, or if 
>> you feel that a member's post is inappropriate, please contact the owners or 
>> moderators directly rather than posting on the list itself.
>> 
>> Your Mac Visionaries list moderator is Mark Taylor.  You can reach mark at:  
>> macvisionaries+modera...@googlegroups.com 
>>  and your owner is Cara 
>> Quinn - you can reach Cara at caraqu...@caraquinn.com 
>> 
>> 
>> The archives for this list can be searched at:
>> http://www.mail-archive.com/macvisionaries@googlegroups.com/ 
>> 
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "MacVisionaries" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to macvisionaries+unsubscr...@googlegroups.com 
>> .
>> To post to this group, send email to macvisionaries@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/macvisionaries 
>> .
>> For more options, visit https://groups.google.com/d/optout 
>> .
>> 
>> 
>> -- 
>> The following information is important for all members of the Mac 
>> Visionaries list.
>>  
>> If you have any questions or concerns about the running of this list, or if 
>> you feel that a member's post is inappropriate, please contact the owners or 
>> moderators directly rather than posting on the list itself.
>>  
>> Your Mac Visionaries list moderator is Mark Taylor. You can reach mark 
>> at:macvisionaries+modera...@googlegroups.com 
>>  and your owner is Cara 
>> Quinn - you can reach Cara at caraqu...@caraquinn.com 
>> 
>>  
>> The archives for this list can be searched at:
>> http://www.mail-archive.com/macvisionaries@googlegroups.com/ 
>> 
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "MacVisionaries" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to macvisionaries+unsubscr...@googlegroups.com 
>> .

Re: SSH into my mac does not work properly.

[Anders Holmberg]

Hi!
No i found out that you have to type:
ssh and...@xx.xx.x.xx  where x is the ip number.
But if i do this now i get a message saying that the ip number is not routed to 
hos.
Very strange.
/A

> 7 feb. 2018 kl. 20:59 skrev Bill Gallik :
> 
> I wonder, are you using the  key after typing in your password?
> 
> My thought is that you may need to terminate the password string with a line 
> feed rather than a carriage return (M rather than J).
> 
> It’s been a lot of years since I worked on a UNIX system, but if memory 
> serves me correctly the carriage return and the line feed are treated as 
> different animals.
> 
> I think you may be able to use the line feed by entering M.
> 
> I’d be curious if this helps, please let me know?
> 
> HTH
> 
> 
> - Bill from Ino, Wisconsin
> - "Always acknowledge a fault. This will throw those in authority off their 
> guard and give you an opportunity to commit more."
> - US Humorist, Mark Twain (1835 - 1910)
> 
> On Feb 7, 2018, at 1:37 PM, Anders Holmberg  > wrote:
> 
> Hi!
> I have a Linux machine with braille and i want to perform tasks on my macbook 
> air using ssh from that linux machine since terminal and voiceover isn’t the 
> best combination.
> I have not compiled brltty yet onto the mac so i have to ssh into it.
> However when i type ssh and then the ip addres i am asked for the password.
> I enter the password and press enter.
> Then i am asked for the password again and i enter it again and so on.
> I know there’s something wrong i do but i can not figure out what.
> SSH is not blocked on my network so it should work.
> I am not really familiar with setting up public keys even though this might 
> be the best.
> Can anyone please help me out?
> Thanks in advance.
> /A
> 
> -- 
> The following information is important for all members of the Mac Visionaries 
> list.
> 
> If you have any questions or concerns about the running of this list, or if 
> you feel that a member's post is inappropriate, please contact the owners or 
> moderators directly rather than posting on the list itself.
> 
> Your Mac Visionaries list moderator is Mark Taylor.  You can reach mark at:  
> macvisionaries+modera...@googlegroups.com 
>  and your owner is Cara 
> Quinn - you can reach Cara at caraqu...@caraquinn.com 
> 
> 
> The archives for this list can be searched at:
> http://www.mail-archive.com/macvisionaries@googlegroups.com/ 
> 
> --- 
> You received this message because you are subscribed to the Google Groups 
> "MacVisionaries" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to macvisionaries+unsubscr...@googlegroups.com.
> To post to this group, send email to macvisionaries@googlegroups.com.
> Visit this group at https://groups.google.com/group/macvisionaries.
> For more options, visit https://groups.google.com/d/optout.
> 
> 
> -- 
> The following information is important for all members of the Mac Visionaries 
> list.
>  
> If you have any questions or concerns about the running of this list, or if 
> you feel that a member's post is inappropriate, please contact the owners or 
> moderators directly rather than posting on the list itself.
>  
> Your Mac Visionaries list moderator is Mark Taylor. You can reach mark at: 
> macvisionaries+modera...@googlegroups.com and your owner is Cara Quinn - you 
> can reach Cara at caraqu...@caraquinn.com
>  
> The archives for this list can be searched at:
> http://www.mail-archive.com/macvisionaries@googlegroups.com/ 
> 
> --- 
> You received this message because you are subscribed to the Google Groups 
> "MacVisionaries" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to macvisionaries+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to macvisionaries@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/macvisionaries 
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
The following information is important for all members of the Mac Visionaries 
list.

If you have any questions or concerns about the running of this list, or if you 
feel that a member's post is inappropriate, please contact the owners or 
moderators directly rather than posting on the list itself.

Your Mac Visionaries list moderator is Mark Taylor.  You can reach mark at:  
macvisionaries+modera...@googlegroups.com and your owner is Cara Quinn - you 
can reach Cara at caraqu...@caraquinn.com

The archives for this list 

Re: SSH into my mac does not work properly.

[Tim Kilburn]

Hi,

It looks like you've neglected to enter a user for the ssh connection.
eg:  ssh Anders@192.168.1.101

You may then get an authenticity confirmation request if it's your first time, 
then the password request, both followed by the return key.  After that, you 
should be in.

Later...

Tim Kilburn
Fort McMurray, AB Canada

On Feb 7, 2018, at 13:21, Chris Moore  wrote:

Did you allow your mac to accept remote logins?  This is done in system 
preferences, sharing.  It also shows the format of the ssh command.  This 
command looks like”:
ssh user@computer-name
When prompted for the password you would enter the password for your mac user.

HTH 
Chris

> On Feb 7, 2018, at 2:59 PM, Bill Gallik  > wrote:
> 
> I wonder, are you using the  key after typing in your password?
> 
> My thought is that you may need to terminate the password string with a line 
> feed rather than a carriage return (M rather than J).
> 
> It’s been a lot of years since I worked on a UNIX system, but if memory 
> serves me correctly the carriage return and the line feed are treated as 
> different animals.
> 
> I think you may be able to use the line feed by entering M.
> 
> I’d be curious if this helps, please let me know?
> 
> HTH
> 
> 
> - Bill from Ino, Wisconsin
> - "Always acknowledge a fault. This will throw those in authority off their 
> guard and give you an opportunity to commit more."
> - US Humorist, Mark Twain (1835 - 1910)
> 
> On Feb 7, 2018, at 1:37 PM, Anders Holmberg  > wrote:
> 
> Hi!
> I have a Linux machine with braille and i want to perform tasks on my macbook 
> air using ssh from that linux machine since terminal and voiceover isn’t the 
> best combination.
> I have not compiled brltty yet onto the mac so i have to ssh into it.
> However when i type ssh and then the ip addres i am asked for the password.
> I enter the password and press enter.
> Then i am asked for the password again and i enter it again and so on.
> I know there’s something wrong i do but i can not figure out what.
> SSH is not blocked on my network so it should work.
> I am not really familiar with setting up public keys even though this might 
> be the best.
> Can anyone please help me out?
> Thanks in advance.
> /A
> 
> -- 
> The following information is important for all members of the Mac Visionaries 
> list.
> 
> If you have any questions or concerns about the running of this list, or if 
> you feel that a member's post is inappropriate, please contact the owners or 
> moderators directly rather than posting on the list itself.
> 
> Your Mac Visionaries list moderator is Mark Taylor.  You can reach mark at:  
> macvisionaries+modera...@googlegroups.com 
>  and your owner is Cara 
> Quinn - you can reach Cara at caraqu...@caraquinn.com 
> 
> 
> The archives for this list can be searched at:
> http://www.mail-archive.com/macvisionaries@googlegroups.com/ 
> 
> --- 
> You received this message because you are subscribed to the Google Groups 
> "MacVisionaries" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to macvisionaries+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to macvisionaries@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/macvisionaries 
> .
> For more options, visit https://groups.google.com/d/optout 
> .
> 
> 
> -- 
> The following information is important for all members of the Mac Visionaries 
> list.
>  
> If you have any questions or concerns about the running of this list, or if 
> you feel that a member's post is inappropriate, please contact the owners or 
> moderators directly rather than posting on the list itself.
>  
> Your Mac Visionaries list moderator is Mark Taylor. You can reach mark at: 
> macvisionaries+modera...@googlegroups.com 
>  and your owner is Cara 
> Quinn - you can reach Cara at caraqu...@caraquinn.com 
> 
>  
> The archives for this list can be searched at:
> http://www.mail-archive.com/macvisionaries@googlegroups.com/ 
> 
> --- 
> You received this message because you are subscribed to the Google Groups 
> "MacVisionaries" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to macvisionaries+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to macvisionaries@googlegroups.com 
> 

Re: SSH into my mac does not work properly.

[Chris Moore]

Did you allow your mac to accept remote logins?  This is done in system 
preferences, sharing.  It also shows the format of the ssh command.  This 
command looks like”:
ssh user@computer-name
When prompted for the password you would enter the password for your mac user.

HTH 
Chris

> On Feb 7, 2018, at 2:59 PM, Bill Gallik  wrote:
> 
> I wonder, are you using the  key after typing in your password?
> 
> My thought is that you may need to terminate the password string with a line 
> feed rather than a carriage return (M rather than J).
> 
> It’s been a lot of years since I worked on a UNIX system, but if memory 
> serves me correctly the carriage return and the line feed are treated as 
> different animals.
> 
> I think you may be able to use the line feed by entering M.
> 
> I’d be curious if this helps, please let me know?
> 
> HTH
> 
> 
> - Bill from Ino, Wisconsin
> - "Always acknowledge a fault. This will throw those in authority off their 
> guard and give you an opportunity to commit more."
> - US Humorist, Mark Twain (1835 - 1910)
> 
> On Feb 7, 2018, at 1:37 PM, Anders Holmberg  > wrote:
> 
> Hi!
> I have a Linux machine with braille and i want to perform tasks on my macbook 
> air using ssh from that linux machine since terminal and voiceover isn’t the 
> best combination.
> I have not compiled brltty yet onto the mac so i have to ssh into it.
> However when i type ssh and then the ip addres i am asked for the password.
> I enter the password and press enter.
> Then i am asked for the password again and i enter it again and so on.
> I know there’s something wrong i do but i can not figure out what.
> SSH is not blocked on my network so it should work.
> I am not really familiar with setting up public keys even though this might 
> be the best.
> Can anyone please help me out?
> Thanks in advance.
> /A
> 
> -- 
> The following information is important for all members of the Mac Visionaries 
> list.
> 
> If you have any questions or concerns about the running of this list, or if 
> you feel that a member's post is inappropriate, please contact the owners or 
> moderators directly rather than posting on the list itself.
> 
> Your Mac Visionaries list moderator is Mark Taylor.  You can reach mark at:  
> macvisionaries+modera...@googlegroups.com 
>  and your owner is Cara 
> Quinn - you can reach Cara at caraqu...@caraquinn.com 
> 
> 
> The archives for this list can be searched at:
> http://www.mail-archive.com/macvisionaries@googlegroups.com/ 
> 
> --- 
> You received this message because you are subscribed to the Google Groups 
> "MacVisionaries" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to macvisionaries+unsubscr...@googlegroups.com.
> To post to this group, send email to macvisionaries@googlegroups.com.
> Visit this group at https://groups.google.com/group/macvisionaries.
> For more options, visit https://groups.google.com/d/optout.
> 
> 
> -- 
> The following information is important for all members of the Mac Visionaries 
> list.
>  
> If you have any questions or concerns about the running of this list, or if 
> you feel that a member's post is inappropriate, please contact the owners or 
> moderators directly rather than posting on the list itself.
>  
> Your Mac Visionaries list moderator is Mark Taylor. You can reach mark at: 
> macvisionaries+modera...@googlegroups.com and your owner is Cara Quinn - you 
> can reach Cara at caraqu...@caraquinn.com
>  
> The archives for this list can be searched at:
> http://www.mail-archive.com/macvisionaries@googlegroups.com/ 
> 
> --- 
> You received this message because you are subscribed to the Google Groups 
> "MacVisionaries" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to macvisionaries+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to macvisionaries@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/macvisionaries 
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
The following information is important for all members of the Mac Visionaries 
list.

If you have any questions or concerns about the running of this list, or if you 
feel that a member's post is inappropriate, please contact the owners or 
moderators directly rather than posting on the list itself.

Your Mac Visionaries list moderator is Mark Taylor.  You can reach mark at:  
macvisionaries+modera...@googlegroups.com and your owner is Cara Quinn - you 

Re: SSH into my mac does not work properly.

[Bill Gallik]

I wonder, are you using the  key after typing in your password?

My thought is that you may need to terminate the password string with a line 
feed rather than a carriage return (M rather than J).

It’s been a lot of years since I worked on a UNIX system, but if memory serves 
me correctly the carriage return and the line feed are treated as different 
animals.

I think you may be able to use the line feed by entering M.

I’d be curious if this helps, please let me know?

HTH


- Bill from Ino, Wisconsin
- "Always acknowledge a fault. This will throw those in authority off their 
guard and give you an opportunity to commit more."
- US Humorist, Mark Twain (1835 - 1910)

On Feb 7, 2018, at 1:37 PM, Anders Holmberg  wrote:

Hi!
I have a Linux machine with braille and i want to perform tasks on my macbook 
air using ssh from that linux machine since terminal and voiceover isn’t the 
best combination.
I have not compiled brltty yet onto the mac so i have to ssh into it.
However when i type ssh and then the ip addres i am asked for the password.
I enter the password and press enter.
Then i am asked for the password again and i enter it again and so on.
I know there’s something wrong i do but i can not figure out what.
SSH is not blocked on my network so it should work.
I am not really familiar with setting up public keys even though this might be 
the best.
Can anyone please help me out?
Thanks in advance.
/A

-- 
The following information is important for all members of the Mac Visionaries 
list.

If you have any questions or concerns about the running of this list, or if you 
feel that a member's post is inappropriate, please contact the owners or 
moderators directly rather than posting on the list itself.

Your Mac Visionaries list moderator is Mark Taylor.  You can reach mark at:  
macvisionaries+modera...@googlegroups.com and your owner is Cara Quinn - you 
can reach Cara at caraqu...@caraquinn.com

The archives for this list can be searched at:
http://www.mail-archive.com/macvisionaries@googlegroups.com/
--- 
You received this message because you are subscribed to the Google Groups 
"MacVisionaries" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to macvisionaries+unsubscr...@googlegroups.com.
To post to this group, send email to macvisionaries@googlegroups.com.
Visit this group at https://groups.google.com/group/macvisionaries.
For more options, visit https://groups.google.com/d/optout.

-- 
The following information is important for all members of the Mac Visionaries 
list.

If you have any questions or concerns about the running of this list, or if you 
feel that a member's post is inappropriate, please contact the owners or 
moderators directly rather than posting on the list itself.

Your Mac Visionaries list moderator is Mark Taylor.  You can reach mark at:  
macvisionaries+modera...@googlegroups.com and your owner is Cara Quinn - you 
can reach Cara at caraqu...@caraquinn.com

The archives for this list can be searched at:
http://www.mail-archive.com/macvisionaries@googlegroups.com/
--- 
You received this message because you are subscribed to the Google Groups 
"MacVisionaries" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to macvisionaries+unsubscr...@googlegroups.com.
To post to this group, send email to macvisionaries@googlegroups.com.
Visit this group at https://groups.google.com/group/macvisionaries.
For more options, visit https://groups.google.com/d/optout.

SSH into my mac does not work properly.

[Anders Holmberg]

Hi!
I have a Linux machine with braille and i want to perform tasks on my macbook 
air using ssh from that linux machine since terminal and voiceover isn’t the 
best combination.
I have not compiled brltty yet onto the mac so i have to ssh into it.
However when i type ssh and then the ip addres i am asked for the password.
I enter the password and press enter.
Then i am asked for the password again and i enter it again and so on.
I know there’s something wrong i do but i can not figure out what.
SSH is not blocked on my network so it should work.
I am not really familiar with setting up public keys even though this might be 
the best.
Can anyone please help me out?
Thanks in advance.
/A

-- 
The following information is important for all members of the Mac Visionaries 
list.

If you have any questions or concerns about the running of this list, or if you 
feel that a member's post is inappropriate, please contact the owners or 
moderators directly rather than posting on the list itself.

Your Mac Visionaries list moderator is Mark Taylor.  You can reach mark at:  
macvisionaries+modera...@googlegroups.com and your owner is Cara Quinn - you 
can reach Cara at caraqu...@caraquinn.com

The archives for this list can be searched at:
http://www.mail-archive.com/macvisionaries@googlegroups.com/
--- 
You received this message because you are subscribed to the Google Groups 
"MacVisionaries" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to macvisionaries+unsubscr...@googlegroups.com.
To post to this group, send email to macvisionaries@googlegroups.com.
Visit this group at https://groups.google.com/group/macvisionaries.
For more options, visit https://groups.google.com/d/optout.