Ok, let me get the setup info out of the way to start. I have 3 computers all on the same Linksys wireless router. 2 are wired and 1 is wireless.
Vista desktop wired at 192.168.1.102
openSUSE 11.1 laptop wireless at 192.168.1.103
Headless Ubuntu server 8.10 wired at 192.168.1.105
So the problem is that 1 and 3 are connected and visible (pingable) within the local network. I just converted my laptop to openSUSE and am connected to the internet but local host addresses are unreachable.
Hopefully this is a simple problem, as I’m fairly new to linux. Not clueless, just not experienced. I’ve been at it all day to get the network up on this laptop and I’m going crazy!!! Durring the bcm4328 wifi installation I was almost suicidal!!!
If you can do this also from your Ubuntu box that could be useful (I
think the ‘ip’ commands work on Ubuntu… haven’t verified). The
corresponding data from windows is also useful and can probably be
retrieved via ipconfig /all for the most part.
Good luck.
linoobius wrote:
> Ok, let me get the setup info out of the way to start. I have 3
> computers all on the same Linksys wireless router. 2 are wired and 1 is
> wireless.
>
> 1) Vista desktop wired at 192.168.1.102
> 2) openSUSE 11.1 laptop wireless at 192.168.1.103
> 3) Headless Ubuntu server 8.10 wired at 192.168.1.105
>
> So the problem is that 1 and 3 are connected and visible (pingable)
> within the local network. I just converted my laptop to openSUSE and am
> connected to the internet but local host addresses are unreachable.
>
> Hopefully this is a simple problem, as I’m fairly new to linux. Not
> clueless, just not experienced. I’ve been at it all day to get the
> network up on this laptop and I’m going crazy!!! Durring the bcm4328
> wifi installation I was almost suicidal!!!
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
Here are the results from the commands on the openSUSE machine. Everything worked fine when I had Ubuntu Hardy on theis machine. The problem only came up after I switched over to SUSE. The problems have to be unique to this machine…
michael@michael-laptop:~> ip addr sh
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
inet 127.0.0.2/8 brd 127.255.255.255 scope host secondary lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:1a:73:6e:0e:60 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.103/24 brd 192.168.1.255 scope global wlan0
inet6 fe80::21a:73ff:fe6e:e60/64 scope link
valid_lft forever preferred_lft forever
3: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether 00:1a:4b:70:e2:c9 brd ff:ff:ff:ff:ff:ff
michael@michael-laptop:~> ip route sh
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.103 metric 2
127.0.0.0/8 dev lo scope link
default via 192.168.1.1 dev wlan0 proto static
michael@michael-laptop:~> cat /etc/resolv.conf
### /etc/resolv.conf file autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
# NETCONFIG_DNS_STATIC_SEARCHLIST
# NETCONFIG_DNS_STATIC_SERVERS
# NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
# NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
# Note: Manual change of this file disables netconfig too, but
# may get lost when this file contains comments or empty lines
# only, the netconfig settings are same with settings in this
# file and in case of a "netconfig update -f" call.
#
### Please remove (at least) this line when you modify the file!
search cmts.mlf.ptd.net
nameserver 216.144.187.37
nameserver 207.44.96.129
nameserver 204.186.0.201
michael@michael-laptop:~> ping 192.168.1.105
PING 192.168.1.105 (192.168.1.105) 56(84) bytes of data.
From 192.168.1.103 icmp_seq=3 Destination Host Unreachable
From 192.168.1.103 icmp_seq=6 Destination Host Unreachable
From 192.168.1.103 icmp_seq=7 Destination Host Unreachable
michael@michael-laptop:~> ssh 192.168.1.105
ssh: connect to host 192.168.1.105 port 22: No route to host
Doh… I didn’t even notice that this was wireless and the others
wired… yet you mentioned this worked with Hardy… was that also via
wireless? If so I’m not sure, but otherwise I wonder a little bit about
the wired/wireless interaction. If that’s different I would bet your
router is doing some kind of internal network (wired) protection from
your wireless stuff, but that’s a guess and doesn’t seem right given
your description assuming Hardy was wireless as well. Do your other
boxes show 192.168.1.1 as their default gateways, with 255.255.255.0 as
their subnet masks? If you use the wired connection on this box does it
help? Worst case scenario get a LAN trace from both the box sending
pings and the one that should be receiving and see if it’s even making
it that far. Also try pinging your gateway in any case to see if those
packets make it there and back to rule out a connection problem to the
router. Maybe this is something really funny like your wireless
connecting to a different wireless network (not yours) than you think it
is, but one that has similar IP addressing.
Good luck.
linoobius wrote:
> Here are the results from the commands on the openSUSE machine.
> Everything worked fine when I had Ubuntu Hardy on theis machine. The
> problem only came up after I switched over to SUSE. The problems have to
> be unique to this machine…
>
> michael@michael-laptop:~> ip addr sh
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
> inet 127.0.0.2/8 brd 127.255.255.255 scope host secondary lo
> inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> 2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> state UP qlen 1000
> link/ether 00:1a:73:6e:0e:60 brd ff:ff:ff:ff:ff:ff
> inet 192.168.1.103/24 brd 192.168.1.255 scope global wlan0
> inet6 fe80::21a:73ff:fe6e:e60/64 scope link
> valid_lft forever preferred_lft forever
> 3: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
> state DOWN qlen 1000
> link/ether 00:1a:4b:70:e2:c9 brd ff:ff:ff:ff:ff:ff
>
> michael@michael-laptop:~> ip route sh
> 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.103
> metric 2
> 127.0.0.0/8 dev lo scope link
> default via 192.168.1.1 dev wlan0 proto static
>
> michael@michael-laptop:~> cat /etc/resolv.conf
> ### /etc/resolv.conf file autogenerated by netconfig!
> #
> # Before you change this file manually, consider to define the
> # static DNS configuration using the following variables in the
> # /etc/sysconfig/network/config file:
> # NETCONFIG_DNS_STATIC_SEARCHLIST
> # NETCONFIG_DNS_STATIC_SERVERS
> # NETCONFIG_DNS_FORWARDER
> # or disable DNS configuration updates via netconfig by setting:
> # NETCONFIG_DNS_POLICY=’’
> #
> # See also the netconfig(8) manual page and other documentation.
> #
> # Note: Manual change of this file disables netconfig too, but
> # may get lost when this file contains comments or empty lines
> # only, the netconfig settings are same with settings in this
> # file and in case of a “netconfig update -f” call.
> #
> ### Please remove (at least) this line when you modify the file!
> search cmts.mlf.ptd.net
> nameserver 216.144.187.37
> nameserver 207.44.96.129
> nameserver 204.186.0.201
>
> michael@michael-laptop:~> ping 192.168.1.105
> PING 192.168.1.105 (192.168.1.105) 56(84) bytes of data.
> From 192.168.1.103 icmp_seq=3 Destination Host Unreachable
> From 192.168.1.103 icmp_seq=6 Destination Host Unreachable
> From 192.168.1.103 icmp_seq=7 Destination Host Unreachable
>
> michael@michael-laptop:~> ssh 192.168.1.105
> ssh: connect to host 192.168.1.105 port 22: No route to host
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
Thanks for your quick help!!! I have found the culprit to be… me! lolz It was just as simple as I had it still set for ifup instead of NetworkManager. I messed around for HOURS trying to figure this out!!! Talk about Doh!!! :’( :shame:
Well it’s good that you found it. Thank-you for posting back the
results. The best thing about these types of hangups is that you’ll
never do them again.
Good luck.
linoobius wrote:
> Thanks for your quick help!!! I have found the culprit to be… me!
> lolz It was just as simple as I had it still set for ifup instead of
> NetworkManager. I messed around for HOURS trying to figure this out!!!
> Talk about Doh!!! :’( :shame:
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
:shame: