LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 07-06-2004, 04:32 AM   #16
neofile
LQ Newbie
 
Registered: Jul 2004
Location: San Jose, California
Posts: 14

Original Poster
Rep: Reputation: 0

Yes, I have NAT enabled.

I've given up on DHCP for the moment, I don't think it's ever going to work. But I have now got things working with a static IP AT LAST. I went through my system log and found that the system was querying the router address and getting a response back, and was then sending a request for IP 192.168.10.138, which for some reason it did not get even though that is within the router's dynamic range.

So, I went to the router config in Windows and set up a static IP of 138 for my NIC hardware address (I had previously tried a different in-range number without success). I then set up Suse for the same static IP, restarted everything, and it connected this time. Whether it will ever do so again is something I'm not yet willing to bet on

My router setup is the same as yours, it is a DHCP client for the Net and a server for the LAN and a default gateway. Why Suse cannot operate DHCP with it when everything else can remains a mystery, and although I am now online with Suse I too dislike mysteries and would be willing to continue to explore this one.

The output from ifconfig and route when I configure for DHCP in Suse is odd in the sense that it does not show an inet4 address, and there is no routing table. Knoppix et al did get an inet4 address and did have a routing table.

This is the current output of ifconfig in Suse:

Code:
eth0      Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx
          inet addr:192.168.10.138  Bcast:192.168.10.255  Mask:255.255.255.0
          inet6 addr: fe80::240:5ff:fe7c:7176/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:123853 errors:0 dropped:0 overruns:0 frame:0
          TX packets:67297 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:163284444 (155.7 Mb)  TX bytes:4269943 (4.0 Mb)
          Interrupt:5 Base address:0x5e00

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:83 errors:0 dropped:0 overruns:0 frame:0
          TX packets:83 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5368 (5.2 Kb)  TX bytes:5368 (5.2 Kb)

sit0      Link encap:IPv6-in-IPv4
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
The only difference I can recall between this and the output under DHCP is that the latter had no "inet addr" line at all.

The output from route is:

Code:
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.10.0    *               255.255.255.0    U      0      0        0 eth0
link-local           *               255.255.0.0        U      0      0        0 eth0
loopback           *               255.0.0.0           U      0      0        0 lo
default         192.168.10.10   0.0.0.0         UG    0      0        0 eth0
and this is exactly the same as I got from the route command in Knoppix when I was using DHCP with that.

Let me know if there's any further information I can supply and good luck trying to figure it all out!

Last edited by neofile; 07-06-2004 at 04:33 AM.
 
Old 07-06-2004, 02:51 PM   #17
andrewdodsworth
Member
 
Registered: Oct 2003
Location: United Kingdom
Distribution: SuSE 10.0 - 11.4
Posts: 347

Rep: Reputation: 30
Well I've had a scout around the SuSE dhcpcd bits to see what I could find. In /var/lib/dhcpcd/ there are .info files for each interface set up by dhcp eg mine is called dhcpcd-eth0.info and the previous one is saved as dhcpcd-eth0.info.old. In it are the settings established by dhcp for the interface. My last one looks like:-

IPADDR=192.168.1.10
NETMASK=255.255.255.0
NETWORK=192.168.1.0
BROADCAST=192.168.1.255
GATEWAY=192.168.1.1
DOMAIN='my_domain_name'
DNS=192.168.1.1IPADDR=192.168.1.10
NETMASK=255.255.255.0
NETWORK=192.168.1.0
BROADCAST=192.168.1.255
GATEWAY=192.168.1.1
DOMAIN='FLINTSTONES'
DNS=192.168.1.1
DHCPSID=192.168.1.1
DHCPGIADDR=0.0.0.0
DHCPSIADDR=192.168.1.1
DHCPCHADDR=00:08:0D:F7:29:33
DHCPSHADDR=00:30:BD:B0:AF:02
DHCPSNAME=''
LEASETIME=4294967295
RENEWALTIME=2147483647
REBINDTIME=3758096383
INTERFACE='eth0'
CLASSID='Linux 2.6.4-52-default i686'
CLIENTID=00:08:0D:F7:29:33

DHCPSID=192.168.1.1
DHCPGIADDR=0.0.0.0
DHCPSIADDR=192.168.1.1
DHCPCHADDR=00:30:22:33:44:55
DHCPSHADDR=00:30:AB:BCD:EE
DHCPSNAME=''
LEASETIME=4294967295
RENEWALTIME=2147483647
REBINDTIME=3758096383
INTERFACE='eth0'
CLASSID='Linux 2.6.4-52-default i686'
CLIENTID=00:11:2D:F7:29:33

If you have one then it probably won't look as complete as that - but if there is a partial one it may give you a clue as to what's going wrong,

There's a script called dhcpcd-hook in /etc/sysconfig/network/scripts/ which is the primary script. According to it's comments it calls 'ifup <interface> -o dhcp' whenever an interface is brought down, up or IP address is changed. There are a number of config files it looks for but the primary scripts called are /sbin/ifup which gets called twice - once to get an IP address and then again to get the DHCP info. The other script is /sbin/ifup-dhcp.

I've had a browse through these and judging from the comments there are a few new things in SuSE 9.1 but from the description of how it does it's stuff your setup is failing at the first hurdle because it's not getting the IP address.

I'm afraid that the next bit's down to you in trying to track down (if you want to) exactly where the dhcp client is failing. One of the things you could try is uninstalling the dhcp client and reinstalling it. There appear to be two possible clients dhcpcd (which SuSE prefers) and dhclient.

I'll try and ahve a further look tomorrow.
 
Old 07-07-2004, 02:19 AM   #18
neofile
LQ Newbie
 
Registered: Jul 2004
Location: San Jose, California
Posts: 14

Original Poster
Rep: Reputation: 0
OK, I'll try and take a look at that lot tomorrow; after all this I reckon I'm entitled to an early night for once
 
Old 07-08-2004, 02:33 AM   #19
neofile
LQ Newbie
 
Registered: Jul 2004
Location: San Jose, California
Posts: 14

Original Poster
Rep: Reputation: 0
Bear with me ... I screwed up badly today and have had to do a reinstall of Suse ... will take a while to get my comfy settings back and then I'll have another look at the DHCP thing.

Last edited by neofile; 07-08-2004 at 03:49 AM.
 
Old 07-10-2004, 12:58 PM   #20
neofile
LQ Newbie
 
Registered: Jul 2004
Location: San Jose, California
Posts: 14

Original Poster
Rep: Reputation: 0
I reckon this is a hardware issue, I think the router is possibly on the way out because it's been doing some odd things, like sometimes not issuing an IP if I reboot my PC. I haven't found anyone else experiencing the same problems as I was having so this may well be the DHCP server in the router having its own problems. As I've got things mainly working and am no longer sure at all that this is a Linux issue after all, I'll leave it as it is until I can afford a new router.

Thanks very much for your help!
 
Old 07-10-2004, 01:27 PM   #21
bruno buys
Senior Member
 
Registered: Sep 2003
Location: Rio
Distribution: Debian
Posts: 1,509

Rep: Reputation: 46
Ok, friend.

I have seen people with suse91/dsl problems consistently. I am starting to believe there's something out there which is really troubling. But its difficult for me to reproduce the problem, as I don't use dsl connection.
To me, it seems strange that such a popular connectivity can be problematic without suse releasing at least an issue in their kdb (which I already searched).
Anyway, be welcome! And feel free to ask whatever you need.
 
Old 07-10-2004, 01:44 PM   #22
neofile
LQ Newbie
 
Registered: Jul 2004
Location: San Jose, California
Posts: 14

Original Poster
Rep: Reputation: 0
Quote:
Originally posted by bruno buys
I have seen people with suse91/dsl problems consistently.
Well thanks for that, because as a "newbie" at anything, people usually assume immediately that you've made a mistake and very rarely admit that what's gone wrong might not be your fault!

Having said that, the Linux community is outstandingly helpful in my experience to date, all credit to you guys for being so willing to help out
 
Old 07-10-2004, 02:46 PM   #23
chin808
LQ Newbie
 
Registered: Jun 2004
Location: South Fl USA
Distribution: Mandrake/SuSE
Posts: 8

Rep: Reputation: 0
I have been reading this and would like to add that I too am having eth problems in suse 9.1 pro. I have the same messages upon boot, I also can use xp to connect to the net no prob. I have a cable modem thats been working fine in mandrake and xp pro as well as suse 9.0. I have tried yast to no avail, I have tried using a different nic, actually 3. I have onboard gigabyte lan by marvell (asus a8v for athlon 64) Again it sees the nic bur cannot initialise it... bleh, I have been in wondows ever since the install. Have the purchased version and will try calling tech support on monday... If I get any news Ill post here
-C
 
Old 07-10-2004, 04:15 PM   #24
neofile
LQ Newbie
 
Registered: Jul 2004
Location: San Jose, California
Posts: 14

Original Poster
Rep: Reputation: 0
I have a slightly different problem to you, as Suse connects fine with the DSL modem, but ignores the router. Mind you I think cable gives you a static IP anyway?

Oddly, my first distro was Mandrake 10 Community Edition, it never connected at all, and ended up in the bin!
 
Old 07-27-2004, 09:18 AM   #25
martinvandongen
LQ Newbie
 
Registered: Jul 2004
Location: The Netherlands
Distribution: suse 9.0 pro suse 9.1 personal red hat 9
Posts: 3

Rep: Reputation: 0
Yesterday I had the same sort of trouble connecting to the internet with a Suse 9.0 pro laptop which first has been on another network. It turned out that somehow the ip-adress from the other network wasn't released. So with an dhcpcd-test eth0 I got the given adress by the dhcp-server, but with an ifconfig eth0 I got the ip-adress from the other network. And, ofcourse, that one was the one active ...
The solution to my problem and maybe yours is to do an ifdown eth0, an rm /var/lib/dhcpcd/* and finally an ifup eth0. Somehow I feel this should have been done during a shutdown ...

Cheers,

Martin
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
3 NIC Homebrew Router, WiFi Problem Vlad the E-Mailer Linux - Wireless Networking 3 08-22-2005 04:58 PM
3rd nic in a Suse Box running as a router dasbooter Linux - Networking 5 07-20-2005 11:29 AM
2 External Nic, 1 Internal Nic Router Problem trevanda Linux - Networking 0 10-13-2004 01:20 AM
Dual NIC router for SUSE 9.0 R Audano Linux - Networking 4 03-09-2004 02:11 PM
2 nic router problem williamc Linux - Networking 2 12-04-2003 10:32 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 09:58 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration