[Server-devel] ssh connect to xs server (150) / more setup problems...

[John Watlington]

On Feb 22, 2008, at 12:53 AM, Stefan Reitz wrote:

> Hello Everybody,
>
>
> I've been trying to find some information on how to putty (my  
> favorite windows ssh client) into my xs server (build 150).
>
> Putty's response: 'No supported authentication methods available',  
> which is also what I find in /var/log/secure
>
> I created a 1024 bit rsa key pair with puttygen and coppied the  
> public part to ~/.ssh/rsa_id.pub.
> I restarted sshd but it didn't help.

You will need to put the public part in .ssh/authorized_keys
You can concatenate the public keys from a number of machines  
together into that file.
You will also need to make sure that .ssh and authorized keys are  
owned by you, and that group and
other write priviledges are disabled.   You do not have to restart sshd.

Alternatively, you can edit /etc/ssh/sshd_config, find the line  
"PasswordAuthentication no" and change
it to yes.    You will have to restart sshd for this to take effect.

> Having never seen a well set-up xs server, I don't quite know what  
> to expect...
> - I know Apache is running because I get the 'Fedora Test Page'  
> presented. Shouldn't there be something else?

That would be the responsibility of the content group.   They are  
working on it.

> - I have a dhcp enabled access point connected to eth1, but I can't  
> log on to it with my XO. ifconfig shows:
>  eth1 (inet addr:172.18.0.1 Bcast:172.18.1.255 Mask:255.254.0) UP  
> BROADCAST MULTICAST with 0 RX and TX packets
>  eth1:1 (inet addr:172.18.1.1 Bcast:172.18.1.255 Mask:255.254.0) UP  
> BROADCAST MULTICAST with no information on RX and TX packets - The  
> HWaddr for both is identical.

You do NOT want to enable DHCP on that access point.  Make sure that  
the access point is NOT running in
"gateway" mode.   You can assign it a fixed address in the range  
172.18.1.32 - 172.18.1.254
(gateway 172.18.0.1, netmask 255.255.254.0), which is reserved for  
that purpose.

> eth0 provided internet connectivity right out of the box and says   
> UP BROADCAST RUNNING MULTICAST. I feel clue less.

The XS is set to DHCP automatically.   You can easily change that to  
a static network address.
http://wiki.laptop.org/go/ 
XS_Configuration_Management#Internet_Connection

>  The access point works fine - as soon as I connect it directly to  
> my switch the XO can connect to it.
>
> ejabberd: I followed the steps on http://wiki.laptop.org/go/ 
> XS_Configuration_Management , but once I go to the web interface, I  
> can't log on. None of the created user name - password combinations  
> ever works

Are you sure that you are trying username@<ejabberddomainname> ?
This stymied me for a while.   In the config file, you specify  
something like:
{acl, admin, {user, "admin", "schoolserver.random.xs.laptop.org"}}.

At the login prompt, the correct username is   
admin at schoolserver.random.xs.laptop.org
and the password would be whatever you specified on the ejabberdctl  
command line.

> I guess I am spoiled from my CentOS SME server. Nice integrated web  
> interface. Lots of functionality out of the box. I really need to  
> get this box running. Everything above was originally meant to be  
> 'just a basic condition' - the important thing - with respect to an  
> upcomming demonstration - is presenting dansguardian...

You could install Webmin if you really feel the need.   Something  
more focused
than Webmin will eventually be provided.

> Thank you all for your patience with my venting

Please continue to vent on this mailing list.    Hopefully all of these
issues will either be fixed or well documented in the future.

Cheers,
wad