DHCP vs Static IP - SUSE 10.0 REVISITED
I'm the guy who got frustrated trying to set up a laptop on my LAN after installing SUSE 10.0 and decided to go back to SuSE 9.3. It turned out that I couldn't get 9.3 to reinstall properly either. After several days of trying this and that, I finally determined that I had an intermittent problem with my laptop's optical drive. Short version: I bought a new laptop and installed SUSE 10.0 on it without any apparent problems. However... I am still misundertanding something about configuring the NICs. Everyone was a big help the last time we hashed this out. If you all would continue to help me figure this out, I'd really appreciate it. Here's my setup. It's changed a bit as the result of our previous session. My local network is Ethernet and is implemented with a Linksys router switch. The router switch connects to the cable via a cable modem. I've loaded SUSE 10.0 on the brand new laptop. The laptop connects to my lan via an internal 10/100 Ethernet card. At this point, everything is hard wired. The host names are: linux.site (file server and primary workstation) - SuSE 9.3 camino.site (secondary workstation) - SuSE 9.3 hplaptop.site (mobile workstation) - SUSE 10.0 There are three linux machines, but only one running 10.0, on my lan. The two 9.3 machine's NICs are configured to use DHCP. They can access the Internet and can ping in either direction to/from each other. When hplaptop is configured to use DHCP, hplaptop can access the Internet and can ping either of the other machines but the other two machines cannot ping hplaptop. If I change hplaptop to use fixed IP addresses, all three machines can ping everything on the local network but hplaptop cannot access the Internet. Here's a ping from linux.site to hplaptop.site, everything using DHCP. ===== dhenson@linux:~> ping hplaptop.site PING hplaptop.site (192.168.1.63) 56(84) bytes of data.
From 192.168.1.2: icmp_seq=2 Destination Host Unreachable From 192.168.1.2 icmp_seq=2 Destination Host Unreachable From 192.168.1.2 icmp_seq=3 Destination Host Unreachable From 192.168.1.2 icmp_seq=4 Destination Host Unreachable
--- hplaptop.site ping statistics --- 6 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4999ms , pipe 3 dhenson@linux:~> ===== I'm not sure where ping is getting the hplaptop IP address but it is the one listed in the /etc/hosts file. Here's a listing of that: ===== # # hosts This file describes a number of hostname-to-address # mappings for the TCP/IP subsystem. It is mostly # used at boot time, when no name servers are running. # On small systems, this file can be used instead of a # "named" name server. # Syntax: # # IP-Address Full-Qualified-Hostname Short-Hostname # 127.0.0.1 localhost # special IPv6 addresses ::1 localhost ipv6-localhost ipv6-loopback fe00::0 ipv6-localnet ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 192.168.1.60 linux.site linux 192.168.1.61 toshiba.site toshiba 192.168.1.62 camino.site camino 192.168.1.63 hplaptop.site hplaptop ===== My router-switch's IP address is: 192.168.1.1 My router-switch's subnet mask is: 255.255.255.0 As far as I can tell, the hosts all have the same subnet mask. The router-switch's DHCP is set to start issuing at 192.168.1.2 and to issue up to 48 addresses. I'm so confused at this point that I'm not sure if I'm giving you the info you need. If you need anything, just ask. -- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
On Friday 04 November 2005 05:35 pm, Donald D Henson wrote:
I'm the guy who got frustrated trying to set up a laptop on my LAN after installing SUSE 10.0 and decided to go back to SuSE 9.3. It turned out that I couldn't get 9.3 to reinstall properly either. After several days of trying this and that, I finally determined that I had an intermittent problem with my laptop's optical drive. Short version: I bought a new laptop and installed SUSE 10.0 on it without any apparent problems. However...
I am still misundertanding something about configuring the NICs. Everyone was a big help the last time we hashed this out. If you all would continue to help me figure this out, I'd really appreciate it. Here's my setup. It's changed a bit as the result of our previous session.
My local network is Ethernet and is implemented with a Linksys router switch. The router switch connects to the cable via a cable modem. I've loaded SUSE 10.0 on the brand new laptop. The laptop connects to my lan via an internal 10/100 Ethernet card. At this point, everything is hard wired. The host names are:
linux.site (file server and primary workstation) - SuSE 9.3 camino.site (secondary workstation) - SuSE 9.3 hplaptop.site (mobile workstation) - SUSE 10.0
There are three linux machines, but only one running 10.0, on my lan. The two 9.3 machine's NICs are configured to use DHCP. They can access the Internet and can ping in either direction to/from each other. When hplaptop is configured to use DHCP, hplaptop can access the Internet and can ping either of the other machines but the other two machines cannot ping hplaptop. If I change hplaptop to use fixed IP addresses, all three machines can ping everything on the local network but hplaptop cannot access the Internet.
Here's a ping from linux.site to hplaptop.site, everything using DHCP.
=====
dhenson@linux:~> ping hplaptop.site PING hplaptop.site (192.168.1.63) 56(84) bytes of data.
From 192.168.1.2: icmp_seq=2 Destination Host Unreachable From 192.168.1.2 icmp_seq=2 Destination Host Unreachable From 192.168.1.2 icmp_seq=3 Destination Host Unreachable From 192.168.1.2 icmp_seq=4 Destination Host Unreachable
It would help if you gave the IP addresses each machine has at the time of everything working and when it doesn't work. Also the output of route -n on the laptop when it does and doesn't work. Also check whether the firewall is running on any or all of the machines. If just changing to a static IP makes it work, then a firewall is probably not the problem.
--- hplaptop.site ping statistics --- 6 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4999ms , pipe 3 dhenson@linux:~>
=====
I'm not sure where ping is getting the hplaptop IP address but it is the one listed in the /etc/hosts file. Here's a listing of that:
=====
# # hosts This file describes a number of hostname-to-address # mappings for the TCP/IP subsystem. It is mostly # used at boot time, when no name servers are running. # On small systems, this file can be used instead of a # "named" name server. # Syntax: # # IP-Address Full-Qualified-Hostname Short-Hostname #
127.0.0.1 localhost
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 192.168.1.60 linux.site linux 192.168.1.61 toshiba.site toshiba 192.168.1.62 camino.site camino 192.168.1.63 hplaptop.site hplaptop
=====
My router-switch's IP address is: 192.168.1.1 My router-switch's subnet mask is: 255.255.255.0 As far as I can tell, the hosts all have the same subnet mask. The router-switch's DHCP is set to start issuing at 192.168.1.2 and to issue up to 48 addresses.
I'm so confused at this point that I'm not sure if I'm giving you the info you need. If you need anything, just ask.
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
Bruce Marshall wrote:
On Friday 04 November 2005 05:35 pm, Donald D Henson wrote:
I'm the guy who got frustrated trying to set up a laptop on my LAN after installing SUSE 10.0 and decided to go back to SuSE 9.3. It turned out that I couldn't get 9.3 to reinstall properly either. After several days of trying this and that, I finally determined that I had an intermittent problem with my laptop's optical drive. Short version: I bought a new laptop and installed SUSE 10.0 on it without any apparent problems. However...
I am still misundertanding something about configuring the NICs. Everyone was a big help the last time we hashed this out. If you all would continue to help me figure this out, I'd really appreciate it. Here's my setup. It's changed a bit as the result of our previous session.
My local network is Ethernet and is implemented with a Linksys router switch. The router switch connects to the cable via a cable modem. I've loaded SUSE 10.0 on the brand new laptop. The laptop connects to my lan via an internal 10/100 Ethernet card. At this point, everything is hard wired. The host names are:
linux.site (file server and primary workstation) - SuSE 9.3 camino.site (secondary workstation) - SuSE 9.3 hplaptop.site (mobile workstation) - SUSE 10.0
There are three linux machines, but only one running 10.0, on my lan. The two 9.3 machine's NICs are configured to use DHCP. They can access the Internet and can ping in either direction to/from each other. When hplaptop is configured to use DHCP, hplaptop can access the Internet and can ping either of the other machines but the other two machines cannot ping hplaptop. If I change hplaptop to use fixed IP addresses, all three machines can ping everything on the local network but hplaptop cannot access the Internet.
Here's a ping from linux.site to hplaptop.site, everything using DHCP.
=====
dhenson@linux:~> ping hplaptop.site PING hplaptop.site (192.168.1.63) 56(84) bytes of data.
From 192.168.1.2: icmp_seq=2 Destination Host Unreachable From 192.168.1.2 icmp_seq=2 Destination Host Unreachable From 192.168.1.2 icmp_seq=3 Destination Host Unreachable From 192.168.1.2 icmp_seq=4 Destination Host Unreachable
It would help if you gave the IP addresses each machine has at the time of everything working and when it doesn't work.
There is no time when everything is working, otherwise we wouldn't be having this conversation. :-) Assuming you mean when each machine can/cannot ping the other machines on the LAN... When things are not working (on the LAN), all machines are configured to use DHCP. Is there a way to tell what IP addresses have been assigned? When things are working (on the LAN), hplaptop is configured to use a static IP address of 192.168.1.63. The other two machines are configured to use DHCP. Same question as before.
Also the output of route -n on the laptop when it does and doesn't work.
When not working (all machines using DHCP): hplaptop:/home/dhenson # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 hplaptop:/home/dhenson # When working (hplaptop using 192.168.1.63): hplaptop:/home/dhenson # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo hplaptop:/home/dhenson #
Also check whether the firewall is running on any or all of the machines. If just changing to a static IP makes it work, then a firewall is probably not the problem.
All Linux firewalls are disabled. I use the firewall in the router switch.
--- hplaptop.site ping statistics --- 6 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4999ms , pipe 3 dhenson@linux:~>
=====
I'm not sure where ping is getting the hplaptop IP address but it is the one listed in the /etc/hosts file. Here's a listing of that:
=====
# # hosts This file describes a number of hostname-to-address # mappings for the TCP/IP subsystem. It is mostly # used at boot time, when no name servers are running. # On small systems, this file can be used instead of a # "named" name server. # Syntax: # # IP-Address Full-Qualified-Hostname Short-Hostname #
127.0.0.1 localhost
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 192.168.1.60 linux.site linux 192.168.1.61 toshiba.site toshiba 192.168.1.62 camino.site camino 192.168.1.63 hplaptop.site hplaptop
=====
My router-switch's IP address is: 192.168.1.1 My router-switch's subnet mask is: 255.255.255.0 As far as I can tell, the hosts all have the same subnet mask. The router-switch's DHCP is set to start issuing at 192.168.1.2 and to issue up to 48 addresses.
I'm so confused at this point that I'm not sure if I'm giving you the info you need. If you need anything, just ask.
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
On Sat, 2005-11-05 at 10:38 -0700, Donald D Henson wrote:
Bruce Marshall wrote:
There is no time when everything is working, otherwise we wouldn't be having this conversation. :-) Assuming you mean when each machine can/cannot ping the other machines on the LAN...
When things are not working (on the LAN), all machines are configured to use DHCP. Is there a way to tell what IP addresses have been assigned?
When things are working (on the LAN), hplaptop is configured to use a static IP address of 192.168.1.63. The other two machines are configured to use DHCP. Same question as before.
Also the output of route -n on the laptop when it does and doesn't work.
When not working (all machines using DHCP):
hplaptop:/home/dhenson # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 hplaptop:/home/dhenson #
When working (hplaptop using 192.168.1.63):
hplaptop:/home/dhenson # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo hplaptop:/home/dhenson #
Seems that the opposite would be true as the second example has -no- default route but the first example does. Perhaps the default route is not set correctly in the first example. What is the address of your router? -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On Saturday 05 November 2005 12:45 pm, Ken Schneider wrote:
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo hplaptop:/home/dhenson #
Seems that the opposite would be true as the second example has -no- default route but the first example does. Perhaps the default route is not set correctly in the first example. What is the address of your router?
But as long as all of his computers are on the same subnet 192.168.1.xx then he shouldn't need a default route... No? (but no default indicates something might be wrong)
On Sat, 2005-11-05 at 12:55 -0500, Bruce Marshall wrote:
On Saturday 05 November 2005 12:45 pm, Ken Schneider wrote:
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo hplaptop:/home/dhenson #
Seems that the opposite would be true as the second example has -no- default route but the first example does. Perhaps the default route is not set correctly in the first example. What is the address of your router?
But as long as all of his computers are on the same subnet 192.168.1.xx then he shouldn't need a default route... No? (but no default indicates something might be wrong)
Well yes as long as he doesn't expect to connect to -any- other computers i.e. the internet. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
Bruce Marshall wrote:
On Saturday 05 November 2005 12:45 pm, Ken Schneider wrote:
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo hplaptop:/home/dhenson # Seems that the opposite would be true as the second example has -no- default route but the first example does. Perhaps the default route is not set correctly in the first example. What is the address of your router?
But as long as all of his computers are on the same subnet 192.168.1.xx then he shouldn't need a default route... No? (but no default indicates something might be wrong)
It appears that the missing gateway line was a copying error. I could have sworn that the line was missing before but it is there now. -- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
Ken Schneider wrote:
On Sat, 2005-11-05 at 10:38 -0700, Donald D Henson wrote:
Bruce Marshall wrote:
There is no time when everything is working, otherwise we wouldn't be having this conversation. :-) Assuming you mean when each machine can/cannot ping the other machines on the LAN...
When things are not working (on the LAN), all machines are configured to use DHCP. Is there a way to tell what IP addresses have been assigned?
When things are working (on the LAN), hplaptop is configured to use a static IP address of 192.168.1.63. The other two machines are configured to use DHCP. Same question as before.
Also the output of route -n on the laptop when it does and doesn't work. When not working (all machines using DHCP):
hplaptop:/home/dhenson # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 hplaptop:/home/dhenson #
When working (hplaptop using 192.168.1.63):
hplaptop:/home/dhenson # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo hplaptop:/home/dhenson #
Seems that the opposite would be true as the second example has -no- default route but the first example does. Perhaps the default route is not set correctly in the first example. What is the address of your router?
192.168.1.1 -- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
On Sat, 2005-11-05 at 11:03 -0700, Donald D Henson wrote:
Ken Schneider wrote:
On Sat, 2005-11-05 at 10:38 -0700, Donald D Henson wrote:
Bruce Marshall wrote:
There is no time when everything is working, otherwise we wouldn't be having this conversation. :-) Assuming you mean when each machine can/cannot ping the other machines on the LAN...
When things are not working (on the LAN), all machines are configured to use DHCP. Is there a way to tell what IP addresses have been assigned?
When things are working (on the LAN), hplaptop is configured to use a static IP address of 192.168.1.63. The other two machines are configured to use DHCP. Same question as before.
Also the output of route -n on the laptop when it does and doesn't work. When not working (all machines using DHCP):
hplaptop:/home/dhenson # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 hplaptop:/home/dhenson #
When working (hplaptop using 192.168.1.63):
hplaptop:/home/dhenson # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo hplaptop:/home/dhenson #
Seems that the opposite would be true as the second example has -no- default route but the first example does. Perhaps the default route is not set correctly in the first example. What is the address of your router?
192.168.1.1
Then it seems that you are actually having a problem with your router if you can't set the default route to it. What brand of router is it? -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
Ken Schneider wrote:
On Sat, 2005-11-05 at 11:03 -0700, Donald D Henson wrote:
Ken Schneider wrote:
On Sat, 2005-11-05 at 10:38 -0700, Donald D Henson wrote:
Bruce Marshall wrote:
There is no time when everything is working, otherwise we wouldn't be having this conversation. :-) Assuming you mean when each machine can/cannot ping the other machines on the LAN...
When things are not working (on the LAN), all machines are configured to use DHCP. Is there a way to tell what IP addresses have been assigned?
When things are working (on the LAN), hplaptop is configured to use a static IP address of 192.168.1.63. The other two machines are configured to use DHCP. Same question as before.
Also the output of route -n on the laptop when it does and doesn't work. When not working (all machines using DHCP):
hplaptop:/home/dhenson # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 hplaptop:/home/dhenson #
When working (hplaptop using 192.168.1.63):
hplaptop:/home/dhenson # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo hplaptop:/home/dhenson #
Seems that the opposite would be true as the second example has -no- default route but the first example does. Perhaps the default route is not set correctly in the first example. What is the address of your router? 192.168.1.1
Then it seems that you are actually having a problem with your router if you can't set the default route to it. What brand of router is it?
Linnksys but I think the missing gateway line was a copying error. I looked a few minutes ago and it was there. -- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
On Sat, 2005-11-05 at 11:51 -0700, Donald D Henson wrote:
Ken Schneider wrote:
On Sat, 2005-11-05 at 11:03 -0700, Donald D Henson wrote:
Seems that the opposite would be true as the second example has -no- default route but the first example does. Perhaps the default route is not set correctly in the first example. What is the address of your router? 192.168.1.1
Then it seems that you are actually having a problem with your router if you can't set the default route to it. What brand of router is it?
Linnksys but I think the missing gateway line was a copying error. I looked a few minutes ago and it was there.
What is the routing protocol that you are using? Also do you have any DNS server running? What do you have for the domain in the Yast network config as well as the host name for each PC? It appears that the names setup in a DNS server or the entries setup in /etc/hosts are messed up. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
Ken Schneider wrote:
On Sat, 2005-11-05 at 11:51 -0700, Donald D Henson wrote:
Ken Schneider wrote:
On Sat, 2005-11-05 at 11:03 -0700, Donald D Henson wrote:
Seems that the opposite would be true as the second example has -no- default route but the first example does. Perhaps the default route is not set correctly in the first example. What is the address of your router? 192.168.1.1
Then it seems that you are actually having a problem with your router if you can't set the default route to it. What brand of router is it?
Linnksys but I think the missing gateway line was a copying error. I looked a few minutes ago and it was there.
What is the routing protocol that you are using? Also do you have any DNS server running? What do you have for the domain in the Yast network config as well as the host name for each PC? It appears that the names setup in a DNS server or the entries setup in /etc/hosts are messed up.
Close. It was the NIC configuration that was messed up. I failed to assign a gateway address. Once I did that, everything started working. I appreciate your assistance. -- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
On Saturday 05 November 2005 12:38 pm, Donald D Henson wrote:
Bruce Marshall wrote:
On Friday 04 November 2005 05:35 pm, Donald D Henson wrote:
I'm the guy who got frustrated trying to set up a laptop on my LAN after installing SUSE 10.0 and decided to go back to SuSE 9.3. It turned out that I couldn't get 9.3 to reinstall properly either. After several days of trying this and that, I finally determined that I had an intermittent problem with my laptop's optical drive. Short version: I bought a new laptop and installed SUSE 10.0 on it without any apparent problems. However...
I am still misundertanding something about configuring the NICs. Everyone was a big help the last time we hashed this out. If you all would continue to help me figure this out, I'd really appreciate it. Here's my setup. It's changed a bit as the result of our previous session.
My local network is Ethernet and is implemented with a Linksys router switch. The router switch connects to the cable via a cable modem. I've loaded SUSE 10.0 on the brand new laptop. The laptop connects to my lan via an internal 10/100 Ethernet card. At this point, everything is hard wired. The host names are:
linux.site (file server and primary workstation) - SuSE 9.3 camino.site (secondary workstation) - SuSE 9.3 hplaptop.site (mobile workstation) - SUSE 10.0
There are three linux machines, but only one running 10.0, on my lan. The two 9.3 machine's NICs are configured to use DHCP. They can access the Internet and can ping in either direction to/from each other. When hplaptop is configured to use DHCP, hplaptop can access the Internet and can ping either of the other machines but the other two machines cannot ping hplaptop. If I change hplaptop to use fixed IP addresses, all three machines can ping everything on the local network but hplaptop cannot access the Internet.
Here's a ping from linux.site to hplaptop.site, everything using DHCP.
=====
dhenson@linux:~> ping hplaptop.site PING hplaptop.site (192.168.1.63) 56(84) bytes of data.
From 192.168.1.2: icmp_seq=2 Destination Host Unreachable
From 192.168.1.2 icmp_seq=2 Destination Host Unreachable From 192.168.1.2 icmp_seq=3 Destination Host Unreachable From 192.168.1.2 icmp_seq=4 Destination Host Unreachable
It would help if you gave the IP addresses each machine has at the time of everything working and when it doesn't work.
There is no time when everything is working, otherwise we wouldn't be having this conversation. :-) Assuming you mean when each machine can/cannot ping the other machines on the LAN...
When things are not working (on the LAN), all machines are configured to use DHCP. Is there a way to tell what IP addresses have been assigned?
The two commands we would like to see are: ifconfig route -n on two of the machines when things aren't working. ifconfig will tell you what address got assigned to the machine you issue it from.
When things are working (on the LAN), hplaptop is configured to use a static IP address of 192.168.1.63. The other two machines are configured to use DHCP. Same question as before.
Also the output of route -n on the laptop when it does and doesn't work.
When not working (all machines using DHCP):
hplaptop:/home/dhenson # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 hplaptop:/home/dhenson #
When working (hplaptop using 192.168.1.63):
hplaptop:/home/dhenson # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo hplaptop:/home/dhenson #
Also check whether the firewall is running on any or all of the machines. If just changing to a static IP makes it work, then a firewall is probably not the problem.
All Linux firewalls are disabled. I use the firewall in the router switch.
--- hplaptop.site ping statistics --- 6 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4999ms , pipe 3 dhenson@linux:~>
=====
I'm not sure where ping is getting the hplaptop IP address but it is the one listed in the /etc/hosts file. Here's a listing of that:
=====
# # hosts This file describes a number of hostname-to-address # mappings for the TCP/IP subsystem. It is mostly # used at boot time, when no name servers are running. # On small systems, this file can be used instead of a # "named" name server. # Syntax: # # IP-Address Full-Qualified-Hostname Short-Hostname #
127.0.0.1 localhost
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 192.168.1.60 linux.site linux 192.168.1.61 toshiba.site toshiba 192.168.1.62 camino.site camino 192.168.1.63 hplaptop.site hplaptop
=====
My router-switch's IP address is: 192.168.1.1 My router-switch's subnet mask is: 255.255.255.0 As far as I can tell, the hosts all have the same subnet mask. The router-switch's DHCP is set to start issuing at 192.168.1.2 and to issue up to 48 addresses.
I'm so confused at this point that I'm not sure if I'm giving you the info you need. If you need anything, just ask.
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
Bruce Marshall wrote:
On Saturday 05 November 2005 12:38 pm, Donald D Henson wrote:
Bruce Marshall wrote:
On Friday 04 November 2005 05:35 pm, Donald D Henson wrote:
I'm the guy who got frustrated trying to set up a laptop on my LAN after installing SUSE 10.0 and decided to go back to SuSE 9.3. It turned out that I couldn't get 9.3 to reinstall properly either. After several days of trying this and that, I finally determined that I had an intermittent problem with my laptop's optical drive. Short version: I bought a new laptop and installed SUSE 10.0 on it without any apparent problems. However...
I am still misundertanding something about configuring the NICs. Everyone was a big help the last time we hashed this out. If you all would continue to help me figure this out, I'd really appreciate it. Here's my setup. It's changed a bit as the result of our previous session.
My local network is Ethernet and is implemented with a Linksys router switch. The router switch connects to the cable via a cable modem. I've loaded SUSE 10.0 on the brand new laptop. The laptop connects to my lan via an internal 10/100 Ethernet card. At this point, everything is hard wired. The host names are:
linux.site (file server and primary workstation) - SuSE 9.3 camino.site (secondary workstation) - SuSE 9.3 hplaptop.site (mobile workstation) - SUSE 10.0
There are three linux machines, but only one running 10.0, on my lan. The two 9.3 machine's NICs are configured to use DHCP. They can access the Internet and can ping in either direction to/from each other. When hplaptop is configured to use DHCP, hplaptop can access the Internet and can ping either of the other machines but the other two machines cannot ping hplaptop. If I change hplaptop to use fixed IP addresses, all three machines can ping everything on the local network but hplaptop cannot access the Internet.
Here's a ping from linux.site to hplaptop.site, everything using DHCP.
=====
dhenson@linux:~> ping hplaptop.site PING hplaptop.site (192.168.1.63) 56(84) bytes of data.
From 192.168.1.2: icmp_seq=2 Destination Host Unreachable
From 192.168.1.2 icmp_seq=2 Destination Host Unreachable From 192.168.1.2 icmp_seq=3 Destination Host Unreachable From 192.168.1.2 icmp_seq=4 Destination Host Unreachable It would help if you gave the IP addresses each machine has at the time of everything working and when it doesn't work. There is no time when everything is working, otherwise we wouldn't be having this conversation. :-) Assuming you mean when each machine can/cannot ping the other machines on the LAN...
When things are not working (on the LAN), all machines are configured to use DHCP. Is there a way to tell what IP addresses have been assigned?
The two commands we would like to see are:
ifconfig route -n
on two of the machines when things aren't working.
From Linux.site:
linux:/home/dhenson # ifconfig eth0 Link encap:Ethernet HWaddr 00:07:E9:9C:26:0B inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::207:e9ff:fe9c:260b/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:170742 errors:0 dropped:0 overruns:0 frame:0 TX packets:149293 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:149850521 (142.9 Mb) TX bytes:31689785 (30.2 Mb) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:5053 errors:0 dropped:0 overruns:0 frame:0 TX packets:5053 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1560914 (1.4 Mb) TX bytes:1560914 (1.4 Mb) linux:/home/dhenson # linux:/home/dhenson # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 linux:/home/dhenson #
From hplaptop.site:
hplaptop:/home/dhenson # ifconfig eth0 Link encap:Ethernet HWaddr 00:C0:9F:DF:D1:C8 inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::2c0:9fff:fedf:d168/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:513 errors:0 dropped:0 overruns:0 frame:0 TX packets:558 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:239331 (233.7 kb) TX bytes:172288 (163.2 kb) Interrupt: 255 Base address: 0x2400 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:43 errors:0 dropped:0 overruns:0 frame:0 TX packets:43 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2856 (2.7 kb) TX bytes:2856 (2.7 kb) hplaptop:/home/dhenson # hplaptop:/home/dhenson # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 hplaptop:/home/dhenson #
ifconfig will tell you what address got assigned to the machine you issue it from.
When things are working (on the LAN), hplaptop is configured to use a static IP address of 192.168.1.63. The other two machines are configured to use DHCP. Same question as before.
Also the output of route -n on the laptop when it does and doesn't work. When not working (all machines using DHCP):
hplaptop:/home/dhenson # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 hplaptop:/home/dhenson #
When working (hplaptop using 192.168.1.63):
hplaptop:/home/dhenson # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo hplaptop:/home/dhenson #
Also check whether the firewall is running on any or all of the machines. If just changing to a static IP makes it work, then a firewall is probably not the problem. All Linux firewalls are disabled. I use the firewall in the router switch.
--- hplaptop.site ping statistics --- 6 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4999ms , pipe 3 dhenson@linux:~>
=====
I'm not sure where ping is getting the hplaptop IP address but it is the one listed in the /etc/hosts file. Here's a listing of that:
=====
# # hosts This file describes a number of hostname-to-address # mappings for the TCP/IP subsystem. It is mostly # used at boot time, when no name servers are running. # On small systems, this file can be used instead of a # "named" name server. # Syntax: # # IP-Address Full-Qualified-Hostname Short-Hostname #
127.0.0.1 localhost
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 192.168.1.60 linux.site linux 192.168.1.61 toshiba.site toshiba 192.168.1.62 camino.site camino 192.168.1.63 hplaptop.site hplaptop
=====
My router-switch's IP address is: 192.168.1.1 My router-switch's subnet mask is: 255.255.255.0 As far as I can tell, the hosts all have the same subnet mask. The router-switch's DHCP is set to start issuing at 192.168.1.2 and to issue up to 48 addresses.
I'm so confused at this point that I'm not sure if I'm giving you the info you need. If you need anything, just ask.
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules -- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
On Saturday 05 November 2005 01:34 pm, Donald D Henson wrote:
192.168.1.60 linux.site linux 192.168.1.61 toshiba.site toshiba 192.168.1.62 camino.site camino 192.168.1.63 hplaptop.site hplaptop
Why do you have addresses like the above??? There's a big part of your problem....
Donald D Henson wrote: I just figured out how to tell what current DHCP addresses have been assigned. See added info below.
Bruce Marshall wrote:
It would help if you gave the IP addresses each machine has at the time of everything working and when it doesn't work.
There is no time when everything is working, otherwise we wouldn't be having this conversation. :-) Assuming you mean when each machine can/cannot ping the other machines on the LAN...
When things are not working (on the LAN), all machines are configured to use DHCP. Is there a way to tell what IP addresses have been assigned?
camino 192.168.1.3 linux 192.168.1.2 hplaptop 192.168.1.4
When things are working (on the LAN), hplaptop is configured to use a static IP address of 192.168.1.63. The other two machines are configured to use DHCP. Same question as before.
camino 192.168.1.3 linux 192.168.1.2 hplaptop 192.168.1.4
Also the output of route -n on the laptop when it does and doesn't work.
When not working (all machines using DHCP):
hplaptop:/home/dhenson # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 hplaptop:/home/dhenson #
When working (hplaptop using 192.168.1.63):
hplaptop:/home/dhenson # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo hplaptop:/home/dhenson #
Also check whether the firewall is running on any or all of the machines. If just changing to a static IP makes it work, then a firewall is probably not the problem.
All Linux firewalls are disabled. I use the firewall in the router switch.
--- hplaptop.site ping statistics --- 6 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4999ms , pipe 3 dhenson@linux:~>
=====
I'm not sure where ping is getting the hplaptop IP address but it is the one listed in the /etc/hosts file. Here's a listing of that:
=====
# # hosts This file describes a number of hostname-to-address # mappings for the TCP/IP subsystem. It is mostly # used at boot time, when no name servers are running. # On small systems, this file can be used instead of a # "named" name server. # Syntax: # # IP-Address Full-Qualified-Hostname Short-Hostname #
127.0.0.1 localhost
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 192.168.1.60 linux.site linux 192.168.1.61 toshiba.site toshiba 192.168.1.62 camino.site camino 192.168.1.63 hplaptop.site hplaptop
=====
My router-switch's IP address is: 192.168.1.1 My router-switch's subnet mask is: 255.255.255.0 As far as I can tell, the hosts all have the same subnet mask. The router-switch's DHCP is set to start issuing at 192.168.1.2 and to issue up to 48 addresses.
I'm so confused at this point that I'm not sure if I'm giving you the info you need. If you need anything, just ask.
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
On Saturday 05 November 2005 01:00 pm, Donald D Henson wrote:
--- hplaptop.site ping statistics --- 6 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4999ms , pipe 3 dhenson@linux:~>
Wny don't you try pinging using the ip addresses instead of whatever you have set up for 'names'. This would eliminate a lookup problem vs. a network problem.
Bruce Marshall wrote:
On Saturday 05 November 2005 01:00 pm, Donald D Henson wrote:
--- hplaptop.site ping statistics --- 6 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4999ms , pipe 3 dhenson@linux:~>
Wny don't you try pinging using the ip addresses instead of whatever you have set up for 'names'. This would eliminate a lookup problem vs. a network problem.
Ah. Progress. Pinging 192.168.1.4, the address assigned by the router DHCP, works. When I ping hplaptop: linux:/home/dhenson # ping hplaptop PING hplaptop.site (192.168.1.63) 56(84) bytes of data.
From 192.168.1.2: icmp_seq=2 Destination Host Unreachable From 192.168.1.2 icmp_seq=2 Destination Host Unreachable From 192.168.1.2 icmp_seq=3 Destination Host Unreachable From 192.168.1.2 icmp_seq=4 Destination Host Unreachable
--- hplaptop.site ping statistics --- 4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 2998ms , pipe 3 linux:/home/dhenson # Note that the address of hplaptop this time is 192.168.1.63. What controls the selection of the IP addresses? -- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
On Saturday 05 November 2005 01:49 pm, Donald D Henson wrote:
Ah. Progress. Pinging 192.168.1.4, the address assigned by the router DHCP, works. When I ping hplaptop:
linux:/home/dhenson # ping hplaptop PING hplaptop.site (192.168.1.63) 56(84) bytes of data.
From 192.168.1.2: icmp_seq=2 Destination Host Unreachable From 192.168.1.2 icmp_seq=2 Destination Host Unreachable From 192.168.1.2 icmp_seq=3 Destination Host Unreachable From 192.168.1.2 icmp_seq=4 Destination Host Unreachable
--- hplaptop.site ping statistics --- 4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 2998ms , pipe 3 linux:/home/dhenson #
Ok, more progress. Look at the address you are trying to ping in the example above!! So where does the PING hplaptop.site (192.168.1.63) address come from? '63'??
On Saturday 05 November 2005 01:00 pm, Donald D Henson wrote:
camino 192.168.1.3 linux 192.168.1.2 hplaptop 192.168.1.4
When things are working (on the LAN), hplaptop is configured to use a static IP address of 192.168.1.63. The other two machines are configured to use DHCP. Same question as before.
camino 192.168.1.3 linux 192.168.1.2 hplaptop 192.168.1.4
Here's another pointer.... You are never going to be able to guar-an-tee that any of your machines are going to get the same address from a DHCP setup... so there's almost no point in trying to set up /etc/hosts to give each one a name. You have two choices: 1) Set up your router to hand out specific addresses using a MAC address matchup.. 2) Just give each machine a static IP address (outside your routers DHCP range) and set /etc/hosts to match. Point the DNS for each machine to 192.168.1.1 and the same address for the gateway. And be done with it. I think DHCP in this instance just complicates matters for no gain.
Bruce Marshall wrote:
On Saturday 05 November 2005 01:00 pm, Donald D Henson wrote:
camino 192.168.1.3 linux 192.168.1.2 hplaptop 192.168.1.4
When things are working (on the LAN), hplaptop is configured to use a static IP address of 192.168.1.63. The other two machines are configured to use DHCP. Same question as before. camino 192.168.1.3 linux 192.168.1.2 hplaptop 192.168.1.4
Here's another pointer....
You are never going to be able to guar-an-tee that any of your machines are going to get the same address from a DHCP setup... so there's almost no point in trying to set up /etc/hosts to give each one a name.
You have two choices:
1) Set up your router to hand out specific addresses using a MAC address matchup..
2) Just give each machine a static IP address (outside your routers DHCP range) and set /etc/hosts to match. Point the DNS for each machine to 192.168.1.1 and the same address for the gateway. And be done with it.
Got it. My problem all along has been my failure to assign a gateway address in the NIC configuration. Once I did that, everything started magically working like it should. Thanks for hanging in there with me until the penny dropped. I really appreciate it. And I didn't get mad at you this time. :-)
I think DHCP in this instance just complicates matters for no gain.
Concur. -- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
Hi, On Fri, 04 Nov 2005 15:35:47 -0700 Donald D Henson <wepin@wepin.com> wrote:
My local network is Ethernet and is implemented with a Linksys router switch. The router switch connects to the cable via a cable modem. I've loaded SUSE 10.0 on the brand new laptop. The laptop connects to my lan via an internal 10/100 Ethernet card. At this point, everything is hard wired. The host names are:
linux.site (file server and primary workstation) - SuSE 9.3 camino.site (secondary workstation) - SuSE 9.3 hplaptop.site (mobile workstation) - SUSE 10.0
[...]
192.168.1.60 linux.site linux 192.168.1.61 toshiba.site toshiba 192.168.1.62 camino.site camino 192.168.1.63 hplaptop.site hplaptop [...] My router-switch's IP address is: 192.168.1.1 My router-switch's subnet mask is: 255.255.255.0 As far as I can tell, the hosts all have the same subnet mask. The router-switch's DHCP is set to start issuing at 192.168.1.2 and to issue up to 48 addresses.
To pin it down: Either use static IPs on all computers that should be reached via a name given in /etc/hosts or set up a name server on the router as only the router can tell which IPs it issued when using DHCP. Longer version: I wonder why it works at all in most cases now. When name resolving is to be done, according to the above mentioned entries in /etc/hosts, the names should be resolved to an IP from a range that could not have been issued to that machine. Of course, setting up a DNS server on the router depends on such a service in its software. Maybe another option would be to - set fixed MAC->IP-combinations in the DHCP config and continue using /etc/hosts, or - experiment with mDNS (multicast DNS), which I think the SuSE glibc supports at least at client side. Never tried it myself, though... -hwh
participants (4)
-
Bruce Marshall -
Donald D Henson -
Hans-Werner Hilse -
Ken Schneider