[Gllug] blueyonder / SuSE / DHCP problem

[Mark Williams]

On Thursday 01 Sep 2005 14:09, Mark Williams wrote:
> Hi All,
>
> I'm having problems obtaining an IP address from blueyonder via DHCP:
>
> linux:~ # ifdown eth0
> linux:~ # ifup eth0
> Starting DHCP Client Daemon on eth0... . . . . . . . . . . . . . . . no IP
> address yet... backgrounding.
> linux:~ #
>
> I'm using SuSE Professional 8.2, and have a WebSTAR cable modem connected
> via an ethernet cable.
>
> My ifcfg-eth0 contains the following:
>
> BOOTPROTO='dhcp'
> MTU=''
> REMOTE_IPADDR=''
> STARTMODE='onboot'
> UNIQUE='bSAa.hj4nBFYIjAD'
> WIRELESS='no'
>

I run Mandrake, which I must confess has worked from 7.2 with my ancient BY 
cable modem & now works with a Linksys router connected to it.

Have you checked if you can see the modem on 192.168.100.1? Mine has a useful 
http status page which tells you it's external IP, and verifies connection 
etc.

Mandrake used to use dhcpcd & now uses dhclient.
my /var/log/message (& /var/log/syslog) contain entries like:
messages:Sep  4 05:25:18 dragon dhclient: DHCPREQUEST on eth0 to 192.168.1.1 
port 67
messages:Sep  4 05:25:18 dragon dhclient: DHCPACK from 192.168.1.1
messages:Sep  4 05:25:18 dragon dhclient: bound to 192.168.1.108 -- renewal in 
35238 seconds.

which are, obviously, Linksys not blueyonder messages but are much the same.

dhclient logs stuff in /var/lib/dhcp/dhclient.leases
& /var/lib/dhcp/dhclient-eth0.leases - I'm not sure which client SuSe uses 
though.

I have always found the Blueyonder DNS very good with Linux even though it's 
not officially supported - I used to ring in & just lie about what I was 
typing when my line failed in the early days! They're more tolerant now.

-- 
Mark
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug