DHCP issue with SUSE 11.4

Hello everyone,

after upgrading from openSUSE 11.2 to 11.4 my computer finds himself unable to establish a network connection or to even get an IP adress. I’m especially confused, as until now it used to work out-of-the-box.
when plugging in my WinXP notebook on the same switch or the same cable even, everything works fine…?!?
I already tried some suggestions I found on the net, so I guess my configuration is totally f*cked-up by now:shame:

any help to get me up and running again would be appreciated.

thanx,
robert

symptoms:

ARGOS:/home/rmpp # ping google.de
ping: unknown host google.de

this is the DSL-modem:

ARGOS:/home/rmpp # ping 192.168.2.1
connect: Network is unreachable

this is the router/firewall:

ARGOS:/home/rmpp # ping 192.168.10.1
connect: Network is unreachable

additional info:

ARGOS:/home/rmpp # ifconfig
eth0      Link encap:Ethernet  Hardware Adresse 00:19:99:13:67:DD  
          inet6 Adresse: fe80::219:99ff:fe13:67dd/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6028 errors:0 dropped:0 overruns:0 frame:0
          TX packets:346 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 Sendewarteschlangenlänge:1000 
          RX bytes:361680 (353.2 Kb)  TX bytes:103836 (101.4 Kb)
          Interrupt:18 Basisadresse:0x6000 

lo        Link encap:Lokale Schleife  
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:106 errors:0 dropped:0 overruns:0 frame:0
          TX packets:106 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 Sendewarteschlangenlänge:0 
          RX bytes:8607 (8.4 Kb)  TX bytes:8607 (8.4 Kb)
ARGOS:/home/rmpp # /sbin/lspci | grep thernet
00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)
ARGOS:/home/rmpp # 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!
ARGOS:/home/rmpp # route
Kernel IP Routentabelle
Ziel            Router          Genmask         Flags Metric Ref    Use Iface
loopback        *               255.0.0.0       U     0      0        0 lo

The last time I saw something like that, was in 2007. The kernel thought that it recognized the ethernet card, but it didn’t work. As it happened, I had installed 64 bit. I redid the install, but at 32 bit, and it then worked.

I’m not sure what is happening in your case. But I suspect that it is a problem with the driver for your card, rather than with DHCP.

I suggest, as a test, manually assigning a suitable IP address (one appropriate for your router). I would use Yast for that. See if you can at least get it talking to the router.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Try this:

sudo /usr/sbin/dhcpcd-test eth0

Post the output and let’s see what happens when you try to get an IP
address via DHCP. I assume you setup NetworkManager to manage your
network (vs. the Traditional (ifup) method) but confirming that would be
useful (sudo /sbin/yast lan). It’s interesting that your NIC shows
packets received so I don’t think it’s broken… just misconfigured which
the steps above will hopefully verify.

Good luck.


Want to yell at me in person?
Come to BrainShare 2011 in October: http://tinyurl.com/brainshare2011
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJOQoFyAAoJEF+XTK08PnB5XhcQAJEl5/FwiRqw73UbqbJJBrcV
r6qSVU3exm+HQX4TK3a7IdZNw62rKUvFFMPHlP+6JNlGR9pwDXsmd4x8QVxKamCy
lP7keD8lOHwTiLzPu3MY9DvX5Cs1Mi6MLMiHHhfwVB4xhNQ0i47Nc3hiQMHInO3L
xIGwtdHdXkqnlqujpWzPJ0/kxMwTyd4s7EtCirUljGih5iNLql2Aksn0i1cT7t5p
pkBIee7H4bsSRVFtyvqjq6rmmAqf2KmItC87PA9aMeUPxM6hGLsNMwIz//IigkwP
HKkAWfJBII9gG7tAyQCBNX7DhjjdCWpAkIgjtDR5kvaL+5eM5m/ZYvHpHiwtXoMn
qPShnY1dO4PXsHmBfsfIV55kLEIqq0fv1ZZWsDq/zQl6ot1lJEA5eiN7GWcfczcj
jUwmHqLnd9k8hobf8vLaX02Qs2oAPTNgzkrcbwM4rZ9+6BVAPjiVpM5fHiSax8dB
gJLLWisv0IcR3gg89D7ueD+9W3qHGKOUBpvUbWpHSRtA90b9edVh+5/rulkJsGID
MZx1lw2xMJLonYjVhZHA3w4KmEPY9Bq44s1R+qODYfj2yUWuJinX1S7j3DWyyQDr
PwswQzy1TLh96mZf6EY0nMxJ2x3C5jllY+qNiYHeZ/lMlO3OIiGLcCg8GL2RRX67
xTuIE775qVYezq7ME2f+
=mZUr
-----END PGP SIGNATURE-----

Did anyone note that according to his ifconfig output he has an IPv6 address on *eth0, *but no IPv4 address? I do not know what conclusion to draw from this, but to me it looks if tthe DHCP server at least gave the IPv6 address.

okay here we go…
let’s see what the commands give us as output:


ARGOS:/home/rmpp # /usr/sbin/dhcpcd-test eth0
info, eth0: hardware address = 00:19:99:13:67:dd
info, eth0: broadcasting for a lease
debug, eth0: sending DHCP_DISCOVER with xid 0x45a6c392
debug, eth0: waiting for 10 seconds
debug, eth0: sending DHCP_DISCOVER with xid 0x45a6c392
debug, eth0: sending DHCP_DISCOVER with xid 0x45a6c392
err, eth0: timed out
info, eth0: exiting
ARGOS:/home/rmpp # 

I got no clue what this is trying to tell me, to be honest…
and here comes the big one:

 YaST2 - lan @ ARGOS                                                                                                                              
                                                                                                                                                  
  Netzwerkeinstellungen                                                                                                                          
  ┌Globale Optionen──Übersicht──Hostname/DNS──Routing──────────────────────────────────────────────────────────────────────────────────────────┐ 
  │┌──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐│ 
  ││Name                     │IP-Adresse                                                                                                      ││ 
  ││MCP51 Ethernet Controller│DHCP                                                                                                            ││ 
  ││                                                                                                                                          ││ 
  ││                                                                                                                                          ││ 
  ││                                                                                                                                          ││ 
  ││                                                                                                                                          ││ 
  ││                                                                                                                                          ││ 
  ││                                                                                                                                          ││ 
  ││                                                                                                                                          ││ 
  ││                                                                                                                                          ││ 
  ││                                                                                                                                          ││ 
  ││                                                                                                                                          ││ 
  ││                                                                                                                                          ││ 
  ││                                                                                                                                          ││ 
  ││                                                                                                                                          ││ 
  ││                                                                                                                                          ││ 
  ││                                                                                                                                          ││ 
  ││                                                                                                                                          ││ 
  ││                                                                                                                                          ││ 
  ││                                                                                                                                          ││ 
  │└──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘│ 
  │┌──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐│ 
  ││MCP51 Ethernet Controller                                                                                                                 ││ 
  ││MAC : 00:19:99:13:67:dd                                                                                                                   ││ 
  ││BusID : 0000:00:14.0                                                                                                                      ││ 
  ││ *  Gerätename: eth0                                                                                                                      ││ 
  ││ *  Beim Booten automatisch gestartet                                                                                                     ││ 
  ││ *  IP-Adresse zugewiesen mittels DHCP                                                                                                    ││ 
  ││                                                                                                                                          ││ 
  ││                                                                                                                                          ││ 
  ││                                                                                                                                          ││ 
  │└──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘│ 
  │[Hinzufügen][Bearbeiten][Löschen]                                                                                                           │ 
  └────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘ 
 [Hilfe]                                                                                 [Abbrechen]                                      OK  ]  
                                                                                                                                                  
 F1 Hilfe  F3 Hinzufügen  F4 Bearbeiten  F5 Löschen  F9 Abbrechen  F10 OK                                                              


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

It means your DHCP server is not providing you with an IP address for
whatever reason. Why is that? You said this works with the same wire on
another box so that would make me think that the DHCP service actually
works, but then why doesn’t this box see the response? Maybe a firewall
issue? Perhaps try shutting that down in case it was munged and then try
the test again.

sudo /sbin/rcSuSEfirewall2 stop

If that helps then we can focus on firewall rules. If not, perhaps we
should look at a LAN trace while running the dhcpcd-test command from before:

sudo /usr/sbin/tcpdump -n -s 0 -i eth1 -v port 67 or port 68

Good luck.


Want to yell at me in person?
Come to BrainShare 2011 in October: http://tinyurl.com/brainshare2011
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJOQp1yAAoJEF+XTK08PnB53HUQAIXN4AahIp0YOiaFZQOoUwPz
xzg0Mrkis92p5hP+upNU6CN05ERk5AfiRK0hH9Xe4BTGd4kCikn+4OiKVq0RaGxY
SgL+9p/ublRQ9RnKcMQXIpICuZnX7dLGAnBhNomWHcPivYI32nZ++U2BXV7JvcIe
90iRLWrkofHQnyLxQyAfBnIvxdASVvt0pUCvJVgcHAVKrY+0caP63OXf6C+brSvk
PCwwMjKGOa9B8cG+WoS42/W56yK7cCnF6U46n38fhe4D6vgGpNmae4E6EZBrH/C8
Zb4/Pa3jm0jGSCDBQdkOricdYA9sDUzU1tDQysbVkFefpVJAtDfgdVdlsRUZZQo6
m9sjzNXw6FI2zctBFeb16CIl+zv0xqB2F1rTrLq2EXoW5B4dx33JJXVG7mvssCpL
THQoQo5t5+8OWEA8nLpuAuyZorK311c1wipcnp98dwOkTqoZyPqyCfQ41+8COCTw
rMJmq2Xplc+IzntzQauF0+zsJfq0nOu8tlnCoxuzhrDhzb7w5Db9J2lWRLvnX5R9
vowLalOvY0+8BJZnMQOGdVr8S3qZFdOA4VGtALvOR5QtIsS4Ff0HeOMmoil42LWs
qCPzRGsQSqkDcwysp2DCl+RVENHckpx0H0HMBUj5UfeOZ8O3MPpZA/0x009sEBCk
nm0QykitrfNh5ZlRsbUJ
=+I3m
-----END PGP SIGNATURE-----

okay, I stopped the firewall and did another lookup

ARGOS:/home/rmpp # /sbin/rcSuSEfirewall2 stop
Unloading firewall rules                                                                                                               done
ARGOS:/home/rmpp # /usr/sbin/dhcpcd-test eth0
info, eth0: hardware address = 00:19:99:13:67:dd
info, eth0: broadcasting for a lease
debug, eth0: sending DHCP_DISCOVER with xid 0x2ee3bdb5
debug, eth0: waiting for 10 seconds
debug, eth0: sending DHCP_DISCOVER with xid 0x2ee3bdb5
debug, eth0: sending DHCP_DISCOVER with xid 0x2ee3bdb5
err, eth0: timed out
info, eth0: exiting
ARGOS:/home/rmpp # 

while running the trace:

ARGOS:/home/rmpp # /usr/sbin/tcpdump -n -s 0 -i eth0 -v port 67
tcpdump: WARNING: eth0: no IPv4 address assigned
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
17:13:59.835152 IP (tos 0x10, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 328)
    0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:19:99:13:67:dd, length 300, xid 0x9b3c3d09, secs 3, Flags [none]
          Client-Ethernet-Address 00:19:99:13:67:dd
          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message Option 53, length 1: Discover
            Client-ID Option 61, length 7: ether 00:19:99:13:67:dd
            Vendor-Class Option 60, length 12: "dhcpcd 3.2.3"
            Hostname Option 12, length 5: "ARGOS"
            Parameter-Request Option 55, length 1: 
              Domain-Name-Server
17:14:01.657136 IP (tos 0x10, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 328)
    0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:19:99:13:67:dd, length 300, xid 0x7727ab66, Flags [none]
          Client-Ethernet-Address 00:19:99:13:67:dd
          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message Option 53, length 1: Discover
            Client-ID Option 61, length 7: ether 00:19:99:13:67:dd
            Vendor-Class Option 60, length 12: "dhcpcd 3.2.3"
            Hostname Option 12, length 5: "ARGOS"
            Parameter-Request Option 55, length 22: 
              RN, RB, Subnet-Mask, BR
              Classless-Static-Route, Static-Route, Default-Gateway, Hostname
              Option 119, Domain-Name, Domain-Name-Server, YD
              YS, NTP, MTU, RP
              Option 120, LPR-Server, LOG, Netbios-Name-Server
              WDD, Netbios-Scope
17:14:04.658425 IP (tos 0x10, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 328)
    0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:19:99:13:67:dd, length 300, xid 0x7727ab66, secs 3, Flags [none]
          Client-Ethernet-Address 00:19:99:13:67:dd
          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message Option 53, length 1: Discover                                                                                            
            Client-ID Option 61, length 7: ether 00:19:99:13:67:dd                                                                                
            Vendor-Class Option 60, length 12: "dhcpcd 3.2.3"
            Hostname Option 12, length 5: "ARGOS"
            Parameter-Request Option 55, length 22: 
              RN, RB, Subnet-Mask, BR
              Classless-Static-Route, Static-Route, Default-Gateway, Hostname
              Option 119, Domain-Name, Domain-Name-Server, YD
              YS, NTP, MTU, RP
              Option 120, LPR-Server, LOG, Netbios-Name-Server
              WDD, Netbios-Scope
17:14:05.841312 IP (tos 0x10, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 328)
    0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:19:99:13:67:dd, length 300, xid 0x9b3c3d09, secs 9, Flags [none]
          Client-Ethernet-Address 00:19:99:13:67:dd
          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message Option 53, length 1: Discover
            Client-ID Option 61, length 7: ether 00:19:99:13:67:dd
            Vendor-Class Option 60, length 12: "dhcpcd 3.2.3"
            Hostname Option 12, length 5: "ARGOS"
            Parameter-Request Option 55, length 1: 
              Domain-Name-Server
17:14:10.664695 IP (tos 0x10, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 328)
    0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:19:99:13:67:dd, length 300, xid 0x7727ab66, secs 9, Flags [none]
          Client-Ethernet-Address 00:19:99:13:67:dd
          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message Option 53, length 1: Discover
            Client-ID Option 61, length 7: ether 00:19:99:13:67:dd
            Vendor-Class Option 60, length 12: "dhcpcd 3.2.3"
            Hostname Option 12, length 5: "ARGOS"
            Parameter-Request Option 55, length 22: 
              RN, RB, Subnet-Mask, BR
              Classless-Static-Route, Static-Route, Default-Gateway, Hostname
              Option 119, Domain-Name, Domain-Name-Server, YD
              YS, NTP, MTU, RP
              Option 120, LPR-Server, LOG, Netbios-Name-Server
              WDD, Netbios-Scope
^C
5 packets captured
5 packets received by filter
0 packets dropped by kernel
ARGOS:/home/rmpp # 

On 08/10/2011 10:02 AM, ab wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> It means your DHCP server is not providing you with an IP address for
> whatever reason. Why is that? You said this works with the same wire on
> another box so that would make me think that the DHCP service actually
> works, but then why doesn’t this box see the response? Maybe a firewall
> issue? Perhaps try shutting that down in case it was munged and then try
> the test again.
>
> sudo /sbin/rcSuSEfirewall2 stop
>
> If that helps then we can focus on firewall rules. If not, perhaps we
> should look at a LAN trace while running the dhcpcd-test command from before:
>
> sudo /usr/sbin/tcpdump -n -s 0 -i eth1 -v port 67 or port 68

Would all you people that are advising him on complicated issues/solutions like
tcpdump and all kinds of DNS tests, please go back to the original post and take
a good look at the output of “route”. With that routing table, how can he ever
get to anyplace but localhost?

Sometimes network issues are very complicated, but when you cannot ping the
router, it is either no NIC driver, or faulty routing. As ifconfig shows his
NIC, bingo.

@rmpp: Enter the following command:


sudo /sbin/route add default gw 192.168.10.1

Usually, doing this once fixes it for good, but not always. If you find that you
need to reenter the command after every boot, add it to /etc/init.d/after.local.

@rmpp: Enter the following command:

sudo /sbin/route add default gw 192.168.10.1

Usually, doing this once fixes it for good, but not always. If you find that you
need to reenter the command after every boot, add it to /etc/init.d/after.local.

I’ll go and try it immediately

sorry, that opens up an other issue:

ARGOS:/home/rmpp # /sbin/route add default gw 192.168.10.1
SIOCADDRT: Kein passender Prozess gefunden
ARGOS:/home/rmpp # 

“no process matches” or something like that…
the mystery deepens

I’d like to point out that this is a brand new installation fresh from the downloaded ISO
maybe there is sth missing in the default install-settings? some packages I forgot to check for the installation?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Also in the first post, he has no IPv4 address. Adding a gateway for IPv4
traffic will not matter if there is no bound non-localhost IPv4 address.
DHCP is to handle the distribution of IPv4 and also sets default routes.
Until this works there is no need to manually set things that definitely
will not work.

Good luck.


Want to yell at me in person?
Come to BrainShare 2011 in October: http://tinyurl.com/brainshare2011
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJOQqV3AAoJEF+XTK08PnB56QwP/3NbdIJ+i3IHdvZbIXt3B71P
uip2dTHkNQpR030sdpO8NggbL9vWPQoRT4lQUSmvJVqo7lhunLibvthweEBgz8kA
87AOTvFq3tqZU8oG6WVUAlOlaELuWw4/PKpa98VkhzdMfWbfQoV+qrAQrD+KG+YE
rNl1qnpem4U+aXgdV2w0WdAhsH1E8Nmfwq5fwOMDEnXlOSvtpWliJTnjbOS+GvVO
Q5E3h5HNNYnVVYcvaZA50GfoLn1IOYQTg+v/C0/FR2PWx2YJSz/Xk7Ra37Y1L3Mc
CIE8hU/ct0NnjBwelEqP4hmhyXZcuzNgVHJIwIxyknkZcatIIrEqfpowx6EJXa1I
KDz3gutqv0J9ZHN/RJcPmwUpwPmnbap95Izm1z61JFjfd7RbwC93SeUopkfbVhDK
s95EYkSpUnmqm7QvzNqnP6fy+OoFKVqaJ6D7G97ewn4Dj2fn6QOafBDnDgZ49Fmj
prOz0Ro6W4IjqP+eJZQOac3T7hNouiIOByiBib276AML6f9paqdj60EIom7ofPfU
Kxtn17BxYQRYzBUS/ePsY2OKKTH39opB2MSQkGJvSWtQyqn0DFtXQuH9v1dm1K8A
X/C4/V5Fh0ln1J3iblBAK6Vt2oRdGNuRKkDD38uMF5EmBINRQncn4npzxu5e72NO
dC6jFCAhCmjSSt0ogKuC
=ZG4Y
-----END PGP SIGNATURE-----

May I disagree with the route add solution? The route table as shown in post #1 does lack more routes then the default alone. That is logical when there is no IP address and the NIC is thus down. I would say that the almost empty routing table is a symptom and not the cause.

EDIT: Sorry, I missed ab’s post above which says the same.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Well, still the same stuff. Your box is asking for an IP address and
nothing is responding to give that IP address. How about we try setting
everything manually in Yast in order to see if things work once everything
is set. Do you know the IP/netmask/gateway/DNS-server information that
you could set via Yast? If not you could set them from the command line
as well with something like the following:

sudo ip addr add 192.168.1.10/24 dev eth0
sudo route add default via 192.168.1.1
sudo -i #enter sudo mode interatively
echo ‘nameserver 192.168.1.1’ >> /etc/resolv.conf
echo ‘nameserver 8.8.8.8’ >> /etc/resolv.conf
exit #exit sudo interactive stuff

These assume that your gateway is 192.168.1.1, that your gateway is also a
DNS service (often the case with home routers), and that your network is a
class C on the 192.168.1.x network. It also assumes 192.168.1.10 is free
for your system’s use. Substitute different values as appropriate. Once
done you should be able to ping your gateway, or anything online.

ping 192.168.1.1
ping 8.8.8.8
ping google.com

Good luck.


Want to yell at me in person?
Come to BrainShare 2011 in October: http://tinyurl.com/brainshare2011
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJOQqfnAAoJEF+XTK08PnB5cgIP/0emPFaB49/Dggbfdm8DhJ2U
hVwcsXpUfSK6X70iMfcwe6hEeJ3HeZgHIV/1mjuog+/ECpguDNciwkD2AS5jKdgb
qJMhRAoyOMgZxC/hz9XsPhuyy3eZ9XCK9tdxoIVy94maTXhgDkvwN/RDdAKkhYXA
qKFL9DRFBucXGVkm4btxGZQJK+FBmK8qkhU4vwpRdqM25DcZdHubBgoHlvYRYqMo
RQEm3aHSMc9cDAwEQYGcNkILp3YdhNw4+OuUD9gzneMmxUADSmNez4W5k6t1L4tK
P8YCJ0+ky6/hGYo3Ad5zIy/3QoUGl+d3GX65M7qvd+xYnyML5em/by7Ixp0odV6X
1qJcTAJZ7Fj0eeUqAJUrqp/BtY2n2e/5H1tUA7uzDNgEuFGSrQahf5wuitWCIEWt
yAZ7RiYeXeJoyoYmyqqEA5wCMlTECJs3GiGCQleziaJ65GAB7NinXazFnTLBMFij
tU+Mk2Lyc9vXrnUxchOnUtjftMf4JHUpQ9bcPjeFs8MulpKlqsIkCPEOpi/V/jUq
szx3smjp7170QrTsTn1TsGuyiV0VWwR9RSkDmV4fhk7VK1XXMy26eZmifPyxZceS
rcZKqWEvWUitartlSHP1pDh7O0tfUsmLEUsOYKAnZgqpX/j3Up4ZyIDa+V0MAOIh
dcVLgTwIKaAlCZaFb1dB
=B230
-----END PGP SIGNATURE-----

On Wed, 10 Aug 2011 19:16:03 +0530, hcvv <hcvv@no-mx.forums.opensuse.org>
wrote:

>
> Did anyone note that according to his -ifconfig- output he has an IPv6
> address on -eth0, -but no IPv4 address? I do not know what conclusion to
> draw from this, but to me it looks if tthe DHCP server at least gave the
> IPv6 address.
>

i think i’ve seen this when my network config. files weren’t in order. i
never use yast or network manager for this, but configure my NICs, static
or dynamic, via the files in /etc/sysconfig/network though.


phani.

Well, the output of

cat /etc/sysconfig/network/ifcfg-eth0

might reveal something. But the fact that it seems to ask from the server, but does not get things served is still strange.

Hi ab,

I’m sorry to report that the manual approach didn’t work either.
here’s what I did and what I got:


ARGOS:/home/rmpp # ip addr add 192.168.10.100/24 dev eth0
ARGOS:/home/rmpp # route add default via 192.168.10.1
Benutzung: inet_route -vF] del {-host|-net} Ziel[/prefix] [gw Gw] [metric M] [dev] If]
       inet_route -vF] add {-host|-net} Ziel[/Prefix] [gw Gw] [metric M]
                              [netmask N] [mss Mss] [window W] [irtt I]
                              [mod] [dyn] [reinstate] [dev] If]
       inet_route -vF] add {-host|-net} Ziel[/Präfix] [metric M] reject
       inet_route -FC] flush      NICHT unterstützt
ARGOS:/home/rmpp # echo 'nameserver 192.168.10.1' >> /etc/resolv.conf
ARGOS:/home/rmpp # echo 'nameserver 8.8.8.8' >> /etc/resolv.conf
ARGOS:/home/rmpp # echo 'nameserver 192.168.1.1' >> /etc/resolv.conf
ARGOS:/home/rmpp # ping google.de
^C
ARGOS:/home/rmpp # ping 192.168.10.1
PING 192.168.10.1 (192.168.10.1) 56(84) bytes of data.
From 192.168.10.100 icmp_seq=2 Destination Host Unreachable
From 192.168.10.100 icmp_seq=3 Destination Host Unreachable
From 192.168.10.100 icmp_seq=4 Destination Host Unreachable
From 192.168.10.100 icmp_seq=6 Destination Host Unreachable
From 192.168.10.100 icmp_seq=7 Destination Host Unreachable
From 192.168.10.100 icmp_seq=8 Destination Host Unreachable
^C
--- 192.168.10.1 ping statistics ---
8 packets transmitted, 0 received, +6 errors, 100% packet loss, time 7000ms
pipe 3
ARGOS:/home/rmpp # ping 8.8.8.8
connect: Network is unreachable
ARGOS:/home/rmpp # 

Later this evening or tomorrow morning I’m connecting my notebook to the other subnet (192.168.10.xxx) which I can’t do right now because I need it for work and it needs to be in the DMZ (a VPN-issue).
Then I’ll have a look at the router for the other subnet.
I’ll report my findings tomorrow.

Thank you for your support!:slight_smile:

Your route statement gave an error! That means that the default route is not set and that you thus can not reach the Internet.

The statement must be:

route add default gw 192.168.10.1

ASnd of course you can see if all is well (and report back here) by doing the reporting statements you did above like rout -n and ifconfig -a and cat /etc/resolv.conf.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

My bad… it should have been:

sudo ip route add default via 192.168.10.1

Good luck.


Want to yell at me in person?
Come to BrainShare 2011 in October: http://tinyurl.com/brainshare2011
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJOQsmDAAoJEF+XTK08PnB5X/oP/ibKjuRoKTjWbA4HZ9UfhlSV
JYuRDV9AroCpTmEc6LM+PifpeHt0JrAiyVH0FrR/ZY9fBeP0IHC/eq31lfItSK5Q
csm1gKTfhe6ayeVoxiB5aWLgvoK50WUni6HdAAM6qqp8/BLPD+m6pnnUt44JfODe
TRyo9T9isiypzVCUR53prReDveP7/O6F409wEY//h54Pqj+VjimQZUzbYfqaQE8h
I2Cbi47Rd/bPhkTVd40NbqdXa6y9F8xYbDdRjcmfFG+u5bfg8R4pIKeDlmOzO5b7
iZjNhcd+BckvFPFVPMN9HjtQcMrdGx2SXfOiasO1rSyxYutDAJ0zQENKaqV+W5HF
v1T5TcXaV2ekradUIsEyA37PbIzKVO+he8tx2lizIlnVWukFegly8tuHhdeaMzmT
ZkSViFPlF29api3+YkzuLc7shCcktNHpIIvdNZ0msr5PWZhss0iOoiqo+/sXyTdw
5+fzMM8zhmJ0/TV85L7YIUD3/hhDmJLdlc3yZ5E7P5jqo1tIfFy9r428Wskc7bM5
MPZVAl8MlBEQDvBNSYsbq7bzBCB+B7t4u+fI/7X8FebrKLVZBlbu3ViMl6W60ZId
FRNHvUt4sW+giNhYY5KZqqQAUtMQKfYT1mueXBObwp/xE79f+RGwrynitMENYMIC
fWkbG4DJ28rPgUJGVYGb
=yjLR
-----END PGP SIGNATURE-----

hi ab,

ip route add default via 192.168.10.1

will give me yet another error:

RTNETLINK answers: No such process

I’ll take a hit at the router…

allright, this is getting freaky.
when I ask my notebook to get a new ip address, I get the following entries in my routers DHCP log:

2011 Aug 11 08:00:08 [FVS338] [dhcpd] DHCPREQUEST for 192.168.10.101 from 00:03:0d:29:ff:09 (apollon) via ixp0
2011 Aug 11 08:00:08 [FVS338] [dhcpd] DHCPACK on 192.168.10.101 to 00:03:0d:29:ff:09 (apollon) via ixp0

but when my SUSE-box does the same,
I got

NOTHING! yeah!

so SUSE only pretends to send out a request?!?:open_mouth:

well, thats what my router says about my PC:
“I’ve never heard from this guy in my life.”