[arm-allstar] ssh ver 1.5 error

Doug Crompton wa3dsp at gmail.com
Mon Jan 30 13:37:31 EST 2017 

I have several V1.5 versions running here all using DHCP and I have never
seen a change of IP at reboot. I would suspect this is router specific. I
have had some crazy things happen with older routers which I ended up
replacing. I also encourage users to lock the IP address down in the router
using the mac address. You will get a different IP if you come into the
router using wired vs. wireless because the mac address is different for
each.

Not to lessen your problem but many hundreds of users have brought up V1.5
over the weekend and the issues with this seem to only effect a couple.





*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*

On Mon, Jan 30, 2017 at 12:30 PM, "John Wagner via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> First - nice work Doug, Dave, and anyone else that worked on the image! The
> only real issues I had getting it running on a couple nodes were
> self-inflicted. That speaks volumes to your attention to detail and level
> of testing. Well done guys.
>
> On the SSH/DHCP topic - I don't know if this is related or not... but I
> have noticed that the DHCP client on the 1.5 image behaves differently than
> on the 1.02 version. I also thought SSH wasn't working on my Pi initially,
> but it turns out the Pi was getting a different IP address from my DHCP
> server every time the Pi rebooted. So I'd have to go find the Pi on the
> network after every reboot. Once I figured out what was going on and found
> the new Pi address, SSH to port 222 worked fine.
>
> I haven't grabbed pcaps or dug into logs much yet to see what is going on,
> but I will tonight.
>
> I had my Pi reserved in the DHCP server by it's MAC. The Pi would boot, the
> DHCP server would show an active lease for the Pi on it's reserved address,
> and then another active dynamic lease on a different address for the same
> MAC farther up the scope.
>
> I have 19 other DHCP clients on my network that don't do this, some
> reserved and some totally dynamic, with a mix of Windows, Linux, MacOS,
> iPhones, etc. And the same RasPi2 hardware with the 1.02 image running on
> it did not behave this way either. I figured it was just something peculiar
> on my setup and just setting a static on the Pi until I had time to figure
> it out. FWIW, my DHCP server is on a Juniper SRX210H router/firewall.
>
>  - John, N8CD
>
> On Mon, Jan 30, 2017 at 11:48 AM, <arm-allstar-request at hamvoip.org> wrote:
>
> > Date: Mon, 30 Jan 2017 16:12:30 +0000 (UTC)
> > From: Joe Borovetz <j.borovetz at sbcglobal.net>
> > To: ARM Allstar <arm-allstar at hamvoip.org>
> > Cc: Doug Crompton <wa3dsp at gmail.com>
> > Subject: Re: [arm-allstar] ssh ver 1.5 error
> > Message-ID: <1776946242.3446886.1485792750765 at mail.yahoo.com>
> > Content-Type: text/plain; charset=UTF-8
> >
> > I am using the same address for 1.5 as I did with the previous release.
> > In my system, no ip addresses are handed out via DHCP unless the mac
> > address of the device is in the dhcp table and it is set to supply the
> same
> > address every time.
> > Joe
> >
> >
> >     On Sunday, January 29, 2017 9:49 PM, Doug Crompton via arm-allstar <
> > arm-allstar at hamvoip.org> wrote:
> >
> >
> >  This is often caused by two conflicting IP addresses on the same LAN.
> Try
> >
> > pacman-S arp-scan
> >
> > to install arp-scan
> >
> > Here is an example of a dup IP address -
> > arp-scan -I eth0 -l | grep 192.168.1.42
> >
> > 192.168.1.42 d4:eb:9a:f2:11:a1 (Unknown)
> > 192.168.1.42 f4:23:a4:38:b5:76 (Unknown) (DUP: 2)
> >
> > Substitute your Allstar servers IP address in the arp-scan statement.
> > Make sure the mac address matches the Pi Allstar server you want to
> connect
> > to. Pi's would look similar to this b8:27:eb vendor ID -
> >
> > [root at Pi3-1 ~]# arp-scan -I eth0 -l | grep 192.168.0.152
> > 192.168.0.152? ? b8:27:eb:b2:c2:c3? ? Raspberry Pi Foundation
> >
> >
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >
> > On Sun, Jan 29, 2017 at 7:35 PM, "Joe S. Borovetz via arm-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> > > I too am having problems with the ssh connection. I get connection
> > refused.
> > >
> > > The web server is working on my system too. I even changed the ssh port
> > as
> > > a test.
> > >
> > > ssh worked fine on the previous version and also on a BBB that is being
> > > used for testing another node.
> > >
> > > Joe WA5VMS
> > >
> > >
> > > W2YMM 631-960-1051 <%28631%29%20960-1051> http://www.w2ymm.com On Sun,
> > > Jan 29, 2017 at 8:37 AM, David McGough <kb4fxc at inttek.net> wrote:
> > >
> > >> Hi Bob,
> > >>>
> > >>> It acts like putty is trying to connect to the wrong RPi3
> port...Verify
> > >>> that putty is connecting using port 222.
> > >>>
> > >>> To confirm that you've got the correct IP address, try pointing a web
> > >>> browser to the RPi3--like: http://192.168.1.11  ...You should see a
> > web
> > >>> page like:
> > >>>
> > >>>? THIS IS A TEST !
> > >>>
> > >>> If you see this the web server is working.
> > >>>
> > >>>
> > >>> Thanks David, I am seeing that message when I enter the ip address
> into
> > >>> my
> > >>> web browser.
> > >>>
> > >>> THIS IS A TEST !
> > >>? ? ? ? ? ? ? ? If you see this the web server is working.
> > >> Bob W2YMM
> > >> _______________________________________________
> > >>
> > >> arm-allstar mailing list
> > >> arm-allstar at hamvoip.org
> > >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > >>
> > >> Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > >>
> > >>
> > > _______________________________________________
> > >
> > > arm-allstar mailing list
> > > arm-allstar at hamvoip.org
> > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > >
> > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > >
> > >
> > _______________________________________________
> >
> > arm-allstar mailing list
> > arm-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> >
> >
> >
> >
> > ------------------------------
> >
> > Message: 4
> > Date: Mon, 30 Jan 2017 11:35:29 -0500
> > From: Sam Nabkey <sam.nabkey at gmail.com>
> > To: BeagleBone Black ARM Allstar <arm-allstar at hamvoip.org>
> > Cc: Joe Borovetz <j.borovetz at sbcglobal.net>, Doug Crompton
> >         <wa3dsp at gmail.com>
> > Subject: Re: [arm-allstar] ssh ver 1.5 error
> > Message-ID:
> >         <CAO8AawpHu2yK_gDoDKuNz=N0zvaWWctcWobDFqcjrsjE9xjChg at mail.
> > gmail.com>
> > Content-Type: text/plain; charset=UTF-8
> >
> > I've had similar issues when adding the static ip in the /etc/networks
> file
> > over modifying the dhcpcd configuration file.
> >
> >
> > On Jan 30, 2017 11:13, Joe Borovetz via arm-allstar <
> > arm-allstar at hamvoip.org>
> > wrote:
> >
> > > I am using the same address for 1.5 as I did with the previous release.
> > > In my system, no ip addresses are handed out via DHCP unless the mac
> > > address of the device is in the dhcp table and it is set to supply the
> > same
> > > address every time.
> > > Joe
> > >
> > >
> > >     On Sunday, January 29, 2017 9:49 PM, Doug Crompton via arm-allstar
> <
> > > arm-allstar at hamvoip.org> wrote:
> > >
> > >
> > >  This is often caused by two conflicting IP addresses on the same LAN.
> > Try
> > >
> > > pacman-S arp-scan
> > >
> > > to install arp-scan
> > >
> > > Here is an example of a dup IP address -
> > > arp-scan -I eth0 -l | grep 192.168.1.42
> > >
> > > 192.168.1.42 d4:eb:9a:f2:11:a1 (Unknown)
> > > 192.168.1.42 f4:23:a4:38:b5:76 (Unknown) (DUP: 2)
> > >
> > > Substitute your Allstar servers IP address in the arp-scan statement.
> > > Make sure the mac address matches the Pi Allstar server you want to
> > connect
> > > to. Pi's would look similar to this b8:27:eb vendor ID -
> > >
> > > [root at Pi3-1 ~]# arp-scan -I eth0 -l | grep 192.168.0.152
> > > 192.168.0.152    b8:27:eb:b2:c2:c3    Raspberry Pi Foundation
> > >
> > >
> > >
> > >
> > > *73 Doug*
> > >
> > > *WA3DSP*
> > >
> > > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> > >
> > > On Sun, Jan 29, 2017 at 7:35 PM, "Joe S. Borovetz via arm-allstar" <
> > > arm-allstar at hamvoip.org> wrote:
> > >
> > > > I too am having problems with the ssh connection. I get connection
> > > refused.
> > > >
> > > > The web server is working on my system too. I even changed the ssh
> port
> > > as
> > > > a test.
> > > >
> > > > ssh worked fine on the previous version and also on a BBB that is
> being
> > > > used for testing another node.
> > > >
> > > > Joe WA5VMS
> > > >
> > > >
> > > > W2YMM 631-960-1051 <%28631%29%20960-1051> http://www.w2ymm.com On
> Sun,
> > > > Jan 29, 2017 at 8:37 AM, David McGough <kb4fxc at inttek.net> wrote:
> > > >
> > > >> Hi Bob,
> > > >>>
> > > >>> It acts like putty is trying to connect to the wrong RPi3
> > port...Verify
> > > >>> that putty is connecting using port 222.
> > > >>>
> > > >>> To confirm that you've got the correct IP address, try pointing a
> web
> > > >>> browser to the RPi3--like: http://192.168.1.11  ...You should see
> a
> > > web
> > > >>> page like:
> > > >>>
> > > >>>  THIS IS A TEST !
> > > >>>
> > > >>> If you see this the web server is working.
> > > >>>
> > > >>>
> > > >>> Thanks David, I am seeing that message when I enter the ip address
> > into
> > > >>> my
> > > >>> web browser.
> > > >>>
> > > >>> THIS IS A TEST !
> > > >>                If you see this the web server is working.
> > > >> Bob W2YMM
> > > >> _______________________________________________
> > > >>
> > > >> arm-allstar mailing list
> > > >> arm-allstar at hamvoip.org
> > > >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > > >>
> > > >> Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > > >>
> > > >>
> > > > _______________________________________________
> > > >
> > > > arm-allstar mailing list
> > > > arm-allstar at hamvoip.org
> > > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > > >
> > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > > >
> > > >
> > > _______________________________________________
> > >
> > > arm-allstar mailing list
> > > arm-allstar at hamvoip.org
> > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > >
> > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > >
> > >
> > >
> > > _______________________________________________
> > >
> > > arm-allstar mailing list
> > > arm-allstar at hamvoip.org
> > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > >
> > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> >
> >
> > ------------------------------
> >
> > Message: 5
> > Date: Mon, 30 Jan 2017 11:48:16 -0500 (EST)
> > From: David McGough <kb4fxc at inttek.net>
> > To: "\"Sam Nabkey via arm-allstar\"" <arm-allstar at hamvoip.org>
> > Subject: Re: [arm-allstar] ssh ver 1.5 error
> > Message-ID:
> >         <Pine.LNX.4.44.1701301139490.32477-100000 at goliath.inttek.net>
> > Content-Type: TEXT/PLAIN; charset=US-ASCII
> >
> >
> > Hi Everyone,
> >
> > If you need to hand-modify the IP address configuration, the files are:
> >
> > /etc/systemd/network/eth0.network
> > /etc/systemd/network/wlan0.network
> >
> > This webpage gives many hints about config syntax, etc.:
> >
> > https://wiki.archlinux.org/index.php/systemd-networkd
> >
> > It's worth noting that these files and configuration methods are the
> "new"
> > systemd way of doing things, this isn't archlinux specific....As
> > systemd becomes more prolific, many linux distros are adopting a very
> > similar method of configuration (for better or worse!).
> >
> >
> > 73, David KB4FXC
> >
> >
> > On Mon, 30 Jan 2017, "Sam Nabkey via arm-allstar" wrote:
> >
> > > I've had similar issues when adding the static ip in the /etc/networks
> > file
> > > over modifying the dhcpcd configuration file.
> > >
> > >
> > > On Jan 30, 2017 11:13, Joe Borovetz via arm-allstar <
> > arm-allstar at hamvoip.org>
> > > wrote:
> > >
> > > > I am using the same address for 1.5 as I did with the previous
> release.
> > > > In my system, no ip addresses are handed out via DHCP unless the mac
> > > > address of the device is in the dhcp table and it is set to supply
> the
> > same
> > > > address every time.
> > > > Joe
> > > >
> > > >
> > > >     On Sunday, January 29, 2017 9:49 PM, Doug Crompton via
> arm-allstar
> > <
> > > > arm-allstar at hamvoip.org> wrote:
> > > >
> > > >
> > > >  This is often caused by two conflicting IP addresses on the same
> LAN.
> > Try
> > > >
> > > > pacman-S arp-scan
> > > >
> > > > to install arp-scan
> > > >
> > > > Here is an example of a dup IP address -
> > > > arp-scan -I eth0 -l | grep 192.168.1.42
> > > >
> > > > 192.168.1.42 d4:eb:9a:f2:11:a1 (Unknown)
> > > > 192.168.1.42 f4:23:a4:38:b5:76 (Unknown) (DUP: 2)
> > > >
> > > > Substitute your Allstar servers IP address in the arp-scan statement.
> > > > Make sure the mac address matches the Pi Allstar server you want to
> > connect
> > > > to. Pi's would look similar to this b8:27:eb vendor ID -
> > > >
> > > > [root at Pi3-1 ~]# arp-scan -I eth0 -l | grep 192.168.0.152
> > > > 192.168.0.152    b8:27:eb:b2:c2:c3    Raspberry Pi Foundation
> > > >
> > > >
> > > >
> > > >
> > > > *73 Doug*
> > > >
> > > > *WA3DSP*
> > > >
> > > > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio
> >*
> > > >
> > > > On Sun, Jan 29, 2017 at 7:35 PM, "Joe S. Borovetz via arm-allstar" <
> > > > arm-allstar at hamvoip.org> wrote:
> > > >
> > > > > I too am having problems with the ssh connection. I get connection
> > > > refused.
> > > > >
> > > > > The web server is working on my system too. I even changed the ssh
> > port
> > > > as
> > > > > a test.
> > > > >
> > > > > ssh worked fine on the previous version and also on a BBB that is
> > being
> > > > > used for testing another node.
> > > > >
> > > > > Joe WA5VMS
> > > > >
> > > > >
> > > > > W2YMM 631-960-1051 <%28631%29%20960-1051> http://www.w2ymm.com On
> > Sun,
> > > > > Jan 29, 2017 at 8:37 AM, David McGough <kb4fxc at inttek.net> wrote:
> > > > >
> > > > >> Hi Bob,
> > > > >>>
> > > > >>> It acts like putty is trying to connect to the wrong RPi3
> > port...Verify
> > > > >>> that putty is connecting using port 222.
> > > > >>>
> > > > >>> To confirm that you've got the correct IP address, try pointing a
> > web
> > > > >>> browser to the RPi3--like: http://192.168.1.11  ...You should
> see
> > a
> > > > web
> > > > >>> page like:
> > > > >>>
> > > > >>>  THIS IS A TEST !
> > > > >>>
> > > > >>> If you see this the web server is working.
> > > > >>>
> > > > >>>
> > > > >>> Thanks David, I am seeing that message when I enter the ip
> address
> > into
> > > > >>> my
> > > > >>> web browser.
> > > > >>>
> > > > >>> THIS IS A TEST !
> > > > >>                If you see this the web server is working.
> > > > >> Bob W2YMM
> > > > >> _______________________________________________
> > > > >>
> > > > >> arm-allstar mailing list
> > > > >> arm-allstar at hamvoip.org
> > > > >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > > > >>
> > > > >> Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > > > >>
> > > > >>
> > > > > _______________________________________________
> > > > >
> > > > > arm-allstar mailing list
> > > > > arm-allstar at hamvoip.org
> > > > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > > > >
> > > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > > > >
> > > > >
> > > > _______________________________________________
> > > >
> > > > arm-allstar mailing list
> > > > arm-allstar at hamvoip.org
> > > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > > >
> > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > >
> > > > arm-allstar mailing list
> > > > arm-allstar at hamvoip.org
> > > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > > >
> > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > > _______________________________________________
> > >
> > > arm-allstar mailing list
> > > arm-allstar at hamvoip.org
> > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > >
> > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > >
> >
> >
> >
> > ------------------------------
> >
> > Subject: Digest Footer
> >
> > _______________________________________________
> > arm-allstar mailing list
> > arm-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> >
> > ------------------------------
> >
> > End of arm-allstar Digest, Vol 32, Issue 41
> > *******************************************
> >
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
>

More information about the arm-allstar mailing list