Darkelve Posted November 22, 2003 Report Share Posted November 22, 2003 Well, everybody's out of the house, so I thought I'd get the ol' cable back out and get on the internet to get some updates, software and try out certain things. I cannot seem to connect to the cable modem though. The cable modem, a Motorola SB4200, is functioning: all the led's are on and there is a blinking orange one to indicate activity. This worked fine in 9.1, after I discovered I first had to reset my cable modem. Now, I cannot get a IP adress. I think the problem has something to do with this line: "SIOCSIFFLAGS: Device or resource busy". I ran a few config tools, you can see their results in the attachment. The components alone seem to work fine, but something is wrong... Darkelve cable_connection.txt Quote Link to comment Share on other sites More sharing options...
bvc Posted November 22, 2003 Report Share Posted November 22, 2003 I got the exact same errors when switching from dialup to cable for the first time. I wasn't telling drakconnect to config LAN (eth0) AND 'Cable' connection'. I just wasn't taking my time and didn't see the 'Cable' option to tick it. Probably not your prob but I thought I'd mention it anyway. Quote Link to comment Share on other sites More sharing options...
Darkelve Posted November 22, 2003 Author Report Share Posted November 22, 2003 (edited) I googled around a bit and have tried and come up with some more info: Dhclient gives: [root@localhost wouter]# dhclientInternet Software Consortium DHCP Client V3.0.1rc11 Copyright 1995-2002 Internet Software Consortium. All rights reserved. For info, please visit http://www.isc.org/products/DHCP SIOCSIFFLAGS: Device or resource busy SIOCSIFFLAGS: Device or resource busy Listening on LPF/eth0/00:e0:18:5d:84:61 Sending on LPF/eth0/00:e0:18:5d:84:61 Listening on LPF/lo/ Sending on LPF/lo/ Sending on Socket/fallback receive_packet failed on eth0: Network is down DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 send_packet: Network is down DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 send_packet: Network is down DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 12 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 send_packet: Network is down DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 16 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18 send_packet: Network is down DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 18 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 send_packet: Network is down DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 send_packet: Network is down No DHCPOFFERS received. No working leases in persistent database - sleeping. The connection does work under WinXP, with following settings: Windows IP-configuratie Ethernet-adapter LAN-verbinding: Verbindingsspec. DNS-achtervoegsel: pandora.be IP-adres. . . . . . . . . . . . . : 81.83.73.26 Subnetmasker. . . . . . . . . . . : 255.255.252.0 Standaardgateway. . . . . . . . . : 81.83.72.1 Gonna follow a suggestion by someone, by adding the IP-address (or gateway address?) and adding 1 number e.g. 81.83.73.27 or 81.83.72.2 If anyone has a clue on why or how, plz let me know ;) Darkelve Edited November 22, 2003 by Darkelve Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.