Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I need your help for setting up the network config. I bought Suse 8.0 in Jan, but till now I still can not manage to set up network config. I have a ntl USB cable modem (Ambit USB Cable Modem to be precise), I tried nearly everything to setup the network config it just not work, and after I send hundreds of e-mail to Suse help line, they could not give me the satisfied answer. But finally I found you guys, I have seen some of your threads, specially wai's about how to solve the problem for ntl, I followed his procedure but there are sth turn out that I do not understand. First after I setup the network config from control center and setup each field with the information that I get from windows
hostname ZHILIN
DNS server 194.168.4.100
physical address 00-D0-59-E9-CC-39
IP:81.101.208.229
Gateway:81.101.208.254
DHCP:213.105.224.21
and I could find the eth-usb-0 hotplug during the start of system, but as I use >ifconfig eth-usb-0
the thing turns out sth else,like this
eth-usb-0: error fetching interface information: Device not found
I have no idea why, the system seems can not fetch my hardware address
when I tried >ifconfig -a
this is the display
lo Link encap:Local Loopback
NTL 'bind' there DHCP to your network card Mac address, so you have to register your card with them, normally done through windows install. What I did was take the card out of my XP box that had had the NTL install run on it, and put it in my Linux box, and bang all worked first time.
I have register through the windows anyway, but the problem is like what I point before after I setup the network config, linux system could not find the valid interface name, therefore it could not get the MAC address of this bloody Ambit USB Cable Modem, I have show you what happen, if I type in ifconfig -a, so I have no idea why?
OK, well I have only set mine up using a NIC, rather than the USB, but I guess that would make no differance.
From what I have read the IP 81.101.208.229 is still a unregistered address, I think that if your final octet is high (ie .229) that your card is still not registered on there system, my final octet is .45
If you card is registered then you should just have to put in a DHCP server address, dont put in a fixed address, let NTL allocate you one. My setup went like this....
Connected my modem to my Windows XP box, run through the setup, all works.
Take NIC out of my XP box and put it into my SuSE Linux box, configured eth0 as DHCP, but still entered the IP's for the gateway & DNS. Soon as I applied my settings, DHCP set my ip to *.*.*.45 (sorry about the stars, I can remember the numbers, at work at the moment, Shhhhh
hi, I uninstall the correctconnect and reinstall it again, and during the register itsaid I have been registered, and I use winipcnfig get the same information as before.
I wonder what you mean NIC, and where should I input the DHCP server address?
Now I think the problem is not how to setup my network config, my problem is how the system can find my usb modem address, becuase I check the system, there is no eth-usb-0 such device exist, so the system could not find the vilid interface everytime, therefore it fails to reach the correct point.
in case to help you understand what I said, this is the information I can provide from my suse linux.
dmesg | grep -i usb
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 13:56:25 Sep 13 2002
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: USB UHCI at I/O 0xd400, IRQ 10
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
usb-uhci.c: USB UHCI at I/O 0xd800, IRQ 10
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: USB new device connect on bus1/1, assigned device number 2
By NIC I mean Network Interface Card, ie, I dont use the USB at all, I connect via the CAT5 connection, you should have got both leads when you got the modem, you would of course need a Network Card in you Linux box to be able to do that.
In SuSE7.2 you go into YaST2 and then select network, you dont enter any information for DHCP, you just tick the box, the DHCP server (an NTL server) will then give you a IP address and Subnet Mask (and possibly gateway, and DNS)
hi, thanks for you answer, but how do I get a Network Interface Card, do I have buy one?
And by the way, ntl provide a cable modem, why it does not work?
another question, I have setup the network config hundreds of times, and ask lots of people, but I find that must be sth wrong with the system, it can not detect the device that I setup, do you know why, also you can have a look the other thread about ntl problem, hope that would give you an idea to help me.http://www.linuxquestions.org/questi...&postid=250464
No offence, but I am really tired to setup the network config for linux, since january. maybe i am stupid or somehow, but I really hope the system will work!
NIC = network interface card = network card = 10/100 card = Ethernet card: its all the same, just a different name. Since USB is software driven, it is can be hard to configure, no matter the OS. What Led was saying is that you may want to try the ethernet connection since the reliablility and transfer rate is far superior to USB. USB (in my opinion) was invented so that casual windows users could have a place to plug their printers and scanners in at the same time (this is just a joke - no intentions of offending any windows users out there). The MAC address is trying to bind itself to something that is not there, so go crazy and spend that extra 15 bucks and get yourself a brand spanking new linksys NIC
You based in UK if so check out www.scan.co.uk they sell network cards, I am using a Pro 100 but the 3-COM 3C905-C-TX -M 10/100 is a good bet, should have no problem getting that baby working, just fire it up in Windows go through that setup at NTL to get it working, then swap it to you Linux box (fits in a PCI slot in your machine) and SuSE will with any luck work with it straight away (did mine), then go into network setup in YaST2 select DHCP (and maybe gateway & DNS) any apply, that should work.
Originally posted by jiji1978 --<snip>--
acm.c: v0.21:USB Abstract Control Model driver for USB modems and ISDN adapters
--<snip>--
This is the problem, notice that the ACM module is loaded but not detecting any devices?
This is because the acm module is for usb dial-up and dsl modems, according to this page your cable modem should use the CDCEther module.
Try the following (as root),
1) Remove the acm module with "rmmod acm"
2) Edit /etc/modules.conf and add the following line,
alias eth0 CDCEther
3) Load the CDCEther module with "modprobe CDCEther"
4) Do "dhcpcd eth0"
5) Do "ifconfig eth0" and look for a correct ntl IP.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
NTL network config problem
