public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: After updating 'arping' to 2.15: can't login with SSH
Date: Fri, 11 Dec 2015 18:53:21 +0000	[thread overview]
Message-ID: <1449860001.31655.122.camel@ipfire.org> (raw)
In-Reply-To: <56671940.4040108@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 6096 bytes --]

Hello guys,

I am sorry, but I do not follow. Do I need to do anything? Is this a
bug?

-Michael

On Tue, 2015-12-08 at 18:54 +0100, Matthias Fischer wrote:
> Hi Erik,
> 
> I can't explain, but your changes made it! After using your lfs-file
> for 
> 'arping 2.15', the first tests are all ok. SSH is working as expected
> and I can login through PuTTY.
> 
> Thanks again! ;-)
> 
> Best,
> Matthias
> 
> 
> On 07.12.2015 18:48, Matthias Fischer wrote:
> > On 07.12.2015 15:05, ue wrote:
> > > Hi Matthias,
> > > have build also arping-2.15 (should be the same since i have here
> > > an
> > > appropriate md5sum) but i have only copied it like /libnet
> > > /usr/lib/libnet.so usr/lib/libnet.so.1 /usr/lib/libnet.so.1.7.0
> > > also
> > > from my building environment to the productive one (no fresh .iso
> > > Install) and have had here no problem with SSH but also arping
> > > works
> > > as expected:
> > 
> > Hm... ;-)
> > 
> > > -> arping -h
> > > ARPing 2.15, by Thomas Habets <thomas(a)habets.se>
> > > usage: arping [ -0aAbdDeFpPqrRuUv ] [ -w <us> ] [ -W <sec> ] [ -S
> > > <host/ip> ]
> > >                [ -T <host/ip ] [ -s <MAC> ] [ -t <MAC> ] [ -c
> > > <count> ]
> > >                [ -C <count> ] [ -i <interface> ] [ -m <type> ]
> > > <host/ip/MAC | -B>
> > > For complete usage info, use --help or check the manage.
> > 
> > I had exactly the same output, so I thought that everything could
> > be
> > fine. It wasn't...
> > 
> > > As a beneath info my arping LFS differs a little to yours in
> > > Installation Details" section:
> > 
> > I'll try again with your settings. Devel is running.
> > 
> > > #################################################################
> > > ##############
> > > 
> > > # Installation Details
> > > #################################################################
> > > ##############
> > > 
> > > 
> > > $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
> > >     @$(PREBUILD)
> > >     @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf
> > > $(DIR_DL)/$(DL_FILE)
> > >     cd $(DIR_APP) && ./bootstrap.sh
> > >     cd $(DIR_APP) && ./configure --prefix=/usr
> > > 
> > >     cd $(DIR_APP) && make $(MAKETUNING)
> > >     cd $(DIR_APP) && make install
> > > 
> > >     @rm -rf $(DIR_APP)
> > >     @$(POSTBUILD)
> > > 
> > > 
> > > but i think this aren´t a explanation causing your SSH problem
> > > which i
> > > currently can not´t reproduce here.
> > 
> > Thanks a lot - we'll see...
> > 
> > Best,
> > Matthias
> > 
> > > Greetings,
> > > 
> > > Erik
> > > 
> > > 
> > > 
> > > Am 06.12.2015 um 14:49 schrieb Matthias Fischer:
> > > 
> > > > Hi,
> > > > 
> > > > it came to my view
> > > > (https://forum.ipfire.org/viewtopic.php?f=27&t=15377&sid=a93f68
> > > > dc580a6301bb3afe3a85d0c44d#p92425)
> > > > that there is an update for 'arping'. New version is 2.15
> > > > (IPFire:
> > > > 2.05). Having the time, I tried.
> > > > 
> > > > First results:
> > > > 
> > > > - After some lfs-changes building seems ok, Diffs are as
> > > > follows:
> > > > 
> > > > ***SNIP***
> > > > diff --git a/lfs/arping b/lfs/arping
> > > > index 13eb05e..7680fdb 100644
> > > > --- a/lfs/arping
> > > > +++ b/lfs/arping
> > > > @@ -1,7 +1,7 @@
> > > > ###############################################################
> > > > ################
> > > > 
> > > > #         #
> > > > # IPFire.org - A linux based firewall         #
> > > > -# Copyright (C) 2007  Michael Tremer & Christian Schmidt      
> > > >   #
> > > > +# Copyright (C) 2015  Michael Tremer & Christian Schmidt      
> > > >   #
> > > > #         #
> > > > # This program is free software: you can redistribute it and/or
> > > > modify        #
> > > > # it under the terms of the GNU General Public License as
> > > > published
> > > > by        #
> > > > @@ -24,7 +24,7 @@
> > > > 
> > > > include Config
> > > > 
> > > > -VER        = 2.05
> > > > +VER        = 2.15
> > > > 
> > > > THISAPP    = arping-$(VER)
> > > > DL_FILE    = $(THISAPP).tar.gz
> > > > @@ -40,7 +40,7 @@ objects = $(DL_FILE)
> > > > 
> > > > $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
> > > > 
> > > > -$(DL_FILE)_MD5 = 96e7c2ce8ae09046e264a314eeaac4dd
> > > > +$(DL_FILE)_MD5 = 676584f6eb4ccc8c70fc6b2c702df75d
> > > > 
> > > > install : $(TARGET)
> > > > 
> > > > @@ -70,7 +70,8 @@ $(subst %,%_MD5,$(objects)) :
> > > > $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
> > > >     @$(PREBUILD)
> > > >     @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf
> > > > $(DIR_DL)/$(DL_FILE)
> > > > +    cd $(DIR_APP) && ./configure --prefix=/usr
> > > >     cd $(DIR_APP) && make $(MAKETUNING)
> > > > -    cd $(DIR_APP) && install -m 0755 arping /usr/sbin
> > > > +    cd $(DIR_APP) && make install-exec
> > > >     @rm -rf $(DIR_APP)
> > > >     @$(POSTBUILD)
> > > > ***SNAP***
> > > > 
> > > > Resulting binary is a bit small. Smaller than expected. Ok,
> > > > nevertheless - ("...this will NOT work...!") -  copied it to
> > > > '/usr/sbin' (after making a backup... ;-) ).
> > > > 
> > > > Rebooting the machine showed no visible problems. At first. But
> > > > after
> > > > starting SSH, I couldn't no longer login with PuTTY. Exactly
> > > > NOTHING
> > > > happens.
> > > > 
> > > > SSH-Log shows:
> > > > 
> > > > ...
> > > > 11:18:02    sshd[2852]:     Server listening on 0.0.0.0 port
> > > > 222.
> > > > 11:18:02    sshd[2852]:     Server listening on :: port 222.
> > > > 11:18:02    sshd[2859]:     error: Bind to port 222 on 0.0.0.0
> > > > failed: Address already in use.
> > > > 11:18:02    sshd[2859]:     error: Bind to port 222 on ::
> > > > failed:
> > > > Address already in use.
> > > > 11:18:02    sshd[2859]:     fatal: Cannot bind any address.
> > > > ...
> > > > 
> > > > Copied the old 'arping 2.05' back to '/usr/sbin', rebooted,
> > > > PuTTY works.
> > > > 
> > > > Ok, so there is something missing (in lfs!?), probably
> > > > configure-options, which is beyond my small programming skills.
> > > > If
> > > > anyone is interested in the new 'arping'-version and capable of
> > > > this:
> > > > any hints are welcome. ;-)
> > > > 
> > > > Best,
> > > > Matthias
> > > 
> > > 
> > 
> > 
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-12-11 18:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-06 13:49 Matthias Fischer
2015-12-07 14:05 ` ue
2015-12-07 17:48   ` Matthias Fischer
2015-12-08 17:54     ` Matthias Fischer
2015-12-11 18:53       ` Michael Tremer [this message]
2015-12-11 20:58         ` Matthias Fischer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1449860001.31655.122.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox