[ILUG] sshd problem

Lee Hosty hostyle at csn.ul.ie
Tue Apr 20 10:03:44 IST 2004


Gavin McCullagh wrote:

>>As it happens, it was /etc/hosts that was the problem, along with extra
>>computers on the WAN - with all except the knoppix box using DHCP.
>>
[snip]

>>Is there a standard method of dealing with this? A wildcard in
>>/etc/hosts.allow I would presume?
>>
>
>Either:
>
>1) your client thinks it has the name
>"rfc1918.space.should.not.be.used.on.publicips".  If it were given an IP
>and DNS but no hostname, it might ask the DNS for it's own name and get
>that back. 
>2) your server is doing a DNS lookup of 192.168.0.6 and getting back the
>"rfc....".
>
>I reckon it's [1].  The solution is to set the hostname on your client.
>
It _is_ set (as far as I can tell with respect to Windows - but thats a
question for google, not ILUG).

>
>If it's [2] placing a line like one of the below in /etc/hosts should sort
>it out as it'll be able to then resolve name & ip address using the hosts
>file and won't revert to DNS for the answer.
>
>192.168.0.6  [clienthostname].[yourlocaldomain] [clienthostname]
>192.168.0.6  [clienthostname]
>
Already there. The problem is that since my laptop connects to the WLAN via
DHCP it doesn't always get the same IP address. This is why it seemed to be
working when there were only 3 machines on the WLAN (my two clients always
received either 192.168.0.2 or 192.168.0.3, both of which had entries in
/etc/hosts). Now theres 5 or 6 machines on and off the WLAN and I'm not
always getting the same IP address.

What I've done for now is force the WAP to always assign the same IP to my
two clients. Seems like the best and easiest solution.

Thanks muchly.




More information about the ILUG mailing list