Cannot ssh to Freerunner

2008-10-06 Thread Nicolas Linkert
Hi, I might be a bit retarded (one never knows), but for the life of it I cannot ssh into the FR: Host IP: 192.168.0.101 DNS: 192.168.0.100 On the host I do as root: ifconfig usb0 192.168.0.200 netmask 255.255.255.0 ssh [EMAIL PROTECTED] No route to host ... ? Oh, this is the most

Re: Cannot ssh to Freerunner

2008-10-06 Thread Nicola Mfb
2008/10/6 Nicolas Linkert [EMAIL PROTECTED] Hi, I might be a bit retarded (one never knows), but for the life of it I cannot ssh into the FR: Host IP: 192.168.0.101 DNS: 192.168.0.100 On the host I do as root: ifconfig usb0 192.168.0.200 netmask 255.255.255.0 ssh [EMAIL

Re: Cannot ssh to Freerunner

2008-10-06 Thread xiangfu
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nicolas Linkert wrote: Hi, I might be a bit retarded (one never knows), but for the life of it I cannot ssh into the FR: Host IP: 192.168.0.101 DNS: 192.168.0.100 this is you eth0 ip address. On the host I do as root: ifconfig usb0

Re: Cannot ssh to Freerunner

2008-10-06 Thread Daniel Selinger
If your host is in the same subnet (and has a ethernetcard too), you should use subnetmask 255.255.255.248 for connecting to the freerunner. Otherwise the kernel tries to send out the packages for the freerunnner over your networkcard. (thats what i think, but i'm no network pro ;) - they never

Re: Cannot ssh to Freerunner

2008-10-06 Thread Nicolas Linkert
Hi, no, that does not change anything. ifconfig usb0 192.168.0.200 netmask 255.255.255.0 route add -host 192.168.0.202 gw 192.168.0.200 komakino:/home/nicolas# ping 192.168.0.202 PING 192.168.0.202 (192.168.0.202) 56(84) bytes of data. From 192.168.0.101 icmp_seq=1 Destination Host Unreachable

Re: Cannot ssh to Freerunner

2008-10-06 Thread Paul
Nick, Any other ideas? It's really strange since this worked with the Neo 1973. Not sure if this helps you, but this is what I stuck in my firewall script for the Neo: # Freerunner's USB: $iptables -A FORWARD -i usb0 -j ACCEPT $iptables -A INPUT -i usb0 -j ACCEPT $iptables -A OUTPUT -o

Re: Cannot ssh to Freerunner

2008-10-06 Thread Joel Newkirk
On Mon, 06 Oct 2008 20:42:41 +0200, Nicolas Linkert [EMAIL PROTECTED] wrote: Hi, no, that does not change anything. ifconfig usb0 192.168.0.200 netmask 255.255.255.0 route add -host 192.168.0.202 gw 192.168.0.200 Host IP: 192.168.0.101 DNS: 192.168.0.100 On the host I do

Re: Cannot ssh to Freerunner

2008-10-06 Thread Joel Newkirk
On Mon, 06 Oct 2008 20:53:16 +0200, Paul [EMAIL PROTECTED] wrote: Nick, Any other ideas? It's really strange since this worked with the Neo 1973. Not sure if this helps you, but this is what I stuck in my firewall script for the Neo: # Freerunner's USB: $iptables -A FORWARD -i usb0

Re: Cannot ssh to Freerunner

2008-10-06 Thread Nicolas Linkert
On Mon, 6 Oct 2008 14:53:32 -0400, Joel Newkirk [EMAIL PROTECTED] said: On Mon, 06 Oct 2008 20:42:41 +0200, Nicolas Linkert [EMAIL PROTECTED] wrote: Hi, no, that does not change anything. ifconfig usb0 192.168.0.200 netmask 255.255.255.0 route add -host 192.168.0.202 gw

Re: Cannot ssh to Freerunner

2008-10-06 Thread Nicolas Linkert
The following entry in /etc/network/interfaces allows me to log into the FR - but then I have no access to the internet ... # The primary network interface allow-hotplug eth0 iface eth0 inet static address 192.168.0.101 netmask 255.255.255.0 network 192.168.0.0

Re: Cannot ssh to Freerunner

2008-10-06 Thread Neil Jerram
2008/10/6 Nicolas Linkert [EMAIL PROTECTED]: # The primary network interface allow-hotplug eth0 iface eth0 inet static address 192.168.0.101 netmask 255.255.255.0 network 192.168.0.0 broadcast 192.168.0.255 gateway 192.168.0.100 dns-nameservers

Re: Cannot ssh to Freerunner

2008-10-06 Thread Joel Newkirk
Sorry, I'd expected to be in front of a computer earlier to respond... 3: usb0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether 6e:6d:ef:52:f2:5b brd ff:ff:ff:ff:ff:ff 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.101

Re: Cannot ssh to Freerunner

2008-10-06 Thread Nicolas Linkert
Great! This works for me. The only thing I had to change were the ACCEPT commands since they were not accepted. Thanks. cu, Nick On Mon, 6 Oct 2008 20:28:58 -0400, Joel Newkirk [EMAIL PROTECTED] said: Sorry, I'd expected to be in front of a computer earlier to respond... 3: usb0:

Re: Cannot ssh to Freerunner

2008-10-06 Thread Joel Newkirk
Well crap, sorry about that. It's supposed to be -j ACCEPT, not just 'ACCEPT'. -j means 'jump' and is followed by a chain name or target, in this case ACCEPT telling the firewall to permit matching traffic. I'm guessing your FORWARD chain is either empty with a policy of ACCEPT, or some form of