Active Topics
-
List of well performing apps on Leste (34)
to Maemo 7 / Leste by biketool - 7 hrs, 48 mins ago -
Maemo repository (5)
to Community by dredlok706 - 2 days, 2 hrs ago -
Re-commissioning N9 in 2018 (127)
to MeeGo / Harmattan by smatkovi - 2 days, 5 hrs ago -
Porting apps to Leste (41)
to Maemo 7 / Leste by Arno_11 - 2 days, 23 hrs ago -
N900 is not recognizable on any of my devices (windows 10,7, xp) What can I do? (1)
to Nokia N900 by nieldk - 4 days, 11 hrs ago - more...
|
2010-02-08
, 12:28
|
|
Posts: 236 |
Thanked: 223 times |
Joined on Oct 2009
@ NE UK
|
#12
|
It seems quite odd, because for both wlan interfaces, the subnet is correct and there is traffic both ways.
So, on the N900:
inet addr:192.168.254.219
Mask:255.255.255.0
RX bytes:510308 (498.3 KiB) TX bytes:166707 (162.7 KiB)
(though the traffic is rather low here)
and on the laptop:
inet addr:192.168.254.222
Mask:255.255.255.0
RX bytes:23174401 (23.1 MB) TX bytes:5773662 (5.7 MB)
These are definitely correctly configured at the interface level.
I've occasionally had an issue ssh-ing into the N900 where the N900's lan interface needs to be "woken up" by initiating some traffic from the device itself.
"No route to host" might be a connect timeout, if the wlan interface on the N900 has gone to sleep (the message might take a while to appear if this is the case.)
I would first make sure there's no interference from iptables on the laptop by turning iptables off temporarily, then make sure the interfaces and routing are as described previously on both machines, then try pinging the laptop IP from the N900, and if you get replies, try to ssh to the N900 from the laptop again.
If that doesn't work, might be best to post your laptop routing table, though from looking at the ifconfig output it seems it would be correct.
So, on the N900:
inet addr:192.168.254.219
Mask:255.255.255.0
RX bytes:510308 (498.3 KiB) TX bytes:166707 (162.7 KiB)
(though the traffic is rather low here)
and on the laptop:
inet addr:192.168.254.222
Mask:255.255.255.0
RX bytes:23174401 (23.1 MB) TX bytes:5773662 (5.7 MB)
These are definitely correctly configured at the interface level.
I've occasionally had an issue ssh-ing into the N900 where the N900's lan interface needs to be "woken up" by initiating some traffic from the device itself.
"No route to host" might be a connect timeout, if the wlan interface on the N900 has gone to sleep (the message might take a while to appear if this is the case.)
I would first make sure there's no interference from iptables on the laptop by turning iptables off temporarily, then make sure the interfaces and routing are as described previously on both machines, then try pinging the laptop IP from the N900, and if you get replies, try to ssh to the N900 from the laptop again.
If that doesn't work, might be best to post your laptop routing table, though from looking at the ifconfig output it seems it would be correct.
 |
|
2010-02-08
, 12:33
|
|
Posts: 1,111 |
Thanked: 1,985 times |
Joined on Aug 2009
@ Ċbo, Finland
|
#13
|
Wow, all sorts of complicated stuff in this thread. Pinging the computer from the N900 works for me when I get that. I think it has to do with power saving
__________________
Class .. : Meddler, Thread watcher, Developer, Helper
Humor .. : [********--] Alignment: Pacifist
Patience : [*****-----] Weapon(s): N900, N950, Metal music
Agro ... : [----------] Relic(s) : N95, NGage, Tamyia Wild One
Try Tweed Suit for your hardcore twittering needs
http://twitter.com/mece66
I like my coffee black, like my metal.
Class .. : Meddler, Thread watcher, Developer, Helper
Humor .. : [********--] Alignment: Pacifist
Patience : [*****-----] Weapon(s): N900, N950, Metal music
Agro ... : [----------] Relic(s) : N95, NGage, Tamyia Wild One
Try Tweed Suit for your hardcore twittering needs
http://twitter.com/mece66
I like my coffee black, like my metal.
|
|
2010-02-08
, 12:53
|
|
Posts: 9 |
Thanked: 4 times |
Joined on Feb 2010
|
#14
|
Originally Posted by joschum
Have a look at the routing table of your laptop, I still think it is a routing problem.
Yes, usb0 seems to be disconnected but ssh to the N900 via wireless by
ssh root@192.168.254.219
should work since both the laptop and the N900 are in the same subnet. I also moved the N900 close to the access point but it doesn`t work. ssh from the N900 to another computer works.
Any ideas?
Are you able to ping the n990 from laptop?
Are you able to ping laptop from n900?
Are you able to ssh from n900 to laptop?
What does telnet 192.168.254.219 22 give you?
Last edited by flya320; 2010-02-08 at 12:58.
|
|
2010-02-08
, 12:59
|
|
Posts: 39 |
Thanked: 0 times |
Joined on Feb 2010
@ Zürich, Switzerland
|
#15
|
Originally Posted by Rob1n
This is the routing table of my laptop, is this OK?
Is the routing table on your laptop correct?
Code:
root@epithalamus:~# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 172.16.23.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet8 192.168.177.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet1 192.168.254.0 0.0.0.0 255.255.255.0 U 2 0 0 wlan0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 wlan0 0.0.0.0 192.168.254.1 0.0.0.0 UG 0 0 0 wlan0
Last edited by joschum; 2010-02-08 at 13:09.
 |
|
2010-02-08
, 13:04
|
|
Posts: 850 |
Thanked: 626 times |
Joined on Sep 2009
@ Vienna, Austria
|
#16
|
Originally Posted by joschum
hm, that's strange. your default route points to "tun0", yet your previous ifconfig output doesn't list tun0 as interface.
This is the routing table of my laptop, is this OK?
do you use OpenVPN on your laptop? maybe your setup scripts for the encrypted tunnel didn't restore the original settings properly after disconnecting?
__________________
"What we perceive is not nature itself, but nature exposed to our method of questioning."
-- Werner Karl Heisenberg
"What we perceive is not nature itself, but nature exposed to our method of questioning."
-- Werner Karl Heisenberg
 |
|
2010-02-08
, 13:10
|
|
Posts: 3,404 |
Thanked: 4,474 times |
Joined on Oct 2005
@ Germany
|
#17
|
It could be a powersaving issue (I have this with my router in all N900 firmwares since 38.x except for 42-11). Ping the router from your N900 or do some other network traffic to make the router see the N900 again, so that you can ssh into it.
Setting down powersaving by one level helps, too (at the expense of battery life).
Setting down powersaving by one level helps, too (at the expense of battery life).
__________________
Tidings - RSS and Podcast aggregator for Jolla - https://github.com/pycage/tidings
Cargo Dock - file/cloud manager for Jolla - https://github.com/pycage/cargodock
Tidings - RSS and Podcast aggregator for Jolla - https://github.com/pycage/tidings
Cargo Dock - file/cloud manager for Jolla - https://github.com/pycage/cargodock
| The Following User Says Thank You to pycage For This Useful Post: | ||
|
|
2010-02-08
, 13:10
|
|
Posts: 39 |
Thanked: 0 times |
Joined on Feb 2010
@ Zürich, Switzerland
|
#18
|
Originally Posted by SubCore
Oh, I pasted an output of route -n that was generated during a VPN session. Now the output above is corrected, it does not contain tun0 anymore...
hm, that's strange. your default route points to "tun0", yet your previous ifconfig output doesn't list tun0 as interface.
do you use OpenVPN on your laptop? maybe your setup scripts for the encrypted tunnel didn't restore the original settings properly after disconnecting?
|
|
2010-02-08
, 13:21
|
|
Posts: 850 |
Thanked: 626 times |
Joined on Sep 2009
@ Vienna, Austria
|
#19
|
Originally Posted by joschum
hm looks good now... it should work :/
Now the output above is corrected, it does not contain tun0 anymore...
the only thing i can think of now is that maybe the vmware network module messes up the other interfaces. i've seen that happen sometimes...
__________________
"What we perceive is not nature itself, but nature exposed to our method of questioning."
-- Werner Karl Heisenberg
"What we perceive is not nature itself, but nature exposed to our method of questioning."
-- Werner Karl Heisenberg
|
|
2010-02-09
, 07:02
|
|
Posts: 39 |
Thanked: 0 times |
Joined on Feb 2010
@ Zürich, Switzerland
|
#20
|
I followed the steps that are described in the link below, now USB networking works fine for me. That is, ssh from my laptop running Ubuntu 9.10 to the N900 works :-)
http://wiki.maemo.org/N900_USB_Networking
http://wiki.maemo.org/N900_USB_Networking
The first couple of times I try to ssh over wireless I get the same message as joschum. However, I try to connect several times. After about 5 times it connects and works flawlessly.
nissepetter@jabber.org