I use pump (apt-get install pump) instead of dhcpcd as my DHCP client, and it works fine with optus. You might want to try that. Optus doesn't you to send anything, so don't send your machine name or host name or anything.
You could try power cycle your modem before starting your dhcp client. Unplug the power cable, wait a bit, plug it back in, and the modem will reset (LEDs flashing in a pattern). Make sure you have iface eth0 inet dhcp in your /etc/network/interfaces, then $ ifup eth0 to start the DHCP client. HTH, Ian. On 2004-02-01 05:34pm, Andrew Robson wrote: > > Hey all, > > > > Need some help setting up Optus Cable and debian. > > > > I am but a low Newbi in the setup/installation of debian.. well Linux > in general.. > > > > here's the problem. > > > > * DHCP will not fin an IP when I try to connect to Optus Cable. > > > > I have done the following. > > * Tried the standard install dhcp (well the friend that did > the install did). > > -configured the interface file so that eth0 is using dhcp > > -configured the dhcp.conf (the dhcp config file.. incase I > have miss spelt it) > > & client file to send the host name which is the machine > name > > I have not yet tried the client ID one from Optus as > everything I have read says you don't have to anymore. > And I am still trying to find it. > > *I have tried dhcpcd and after setting up the config files (or > checking them rather) and trying commands such as. > > dhcpcd -d eth0 or > > dhcpcd -h <machine name> -d eth0 > > it still does not work. > > > > *I have then tried dhcp3 set up the appropriate config files > with the most appropriate info. > > > > If i do a command line dhcpcd as above I get messages such as > > *netdev watchdog: eth0: Transmit timed out > > > > or if I go into init.d/ and do a networking restart I get messages > like. > > > > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval ?? > > where ?? is a changing number each time. or there abouts. > > > > > > I have read and tried everything I can about setting up Optus cable, > so I have turned here as a last resort. > > > > some other facts. > > > > I also run windows on the same machine "yes I know it blows" :P > > it is a dual boot. > > the NIC works as I am using it now. > > > > this is most frustrating as under winblows all I have to do is have > the interface set to DHCP and it works.... > > > > > > any help would be most appreciated. .. > > > > thanks.. > > > > Andrew > -- > SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ > Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html -- Regards, Ian Su SIRCA (Securities Industry Research Centre of Asia-Pacific) http://www.sirca.org.au/ Tel: 8374-5078 Email: <[EMAIL PROTECTED]> DISCLAIMER: The contents of this email, inclusive of attachments, may be legally privileged and confidential. Any unauthorised use of the contents is expressly prohibited. If you have received this message in error or are not the intended recipient, you should destroy the email message along with any attachment(s). Unintended recipients of this email are prohibited from retaining, disclosing, distributing or using any information contained herein. This email is also subject to copyright. No part of it should be reproduced, adapted or transmitted without the written consent of the copyright owner. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
