Suse/NovellThis Forum is for the discussion of Suse Linux.
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.
Distribution: PCLinuxOS 2007 on my laptop and Suse 10.2 on my desktop.
Posts: 341
Rep:
Is your LAN card actually configured though? Being recognised in Yast doesn't mean it works!
Open a terminal as root and type 'iwconfig' Does this give a wireless option such as wlan0? Is your radio network listed or found? post your output here.
Is your LAN card actually configured though? Being recognised in Yast doesn't mean it works!
Open a terminal as root and type 'iwconfig' Does this give a wireless option such as wlan0? Is your radio network listed or found? post your output here.
Hello navik_pathak, that's surely not what it said when you entered "ifconfig". There must have been more than that. Can you do it again, enter two commands: first is su to take you into a root terminal, second is ifconfig. You can use copy/paste to put the results from your terminal session into your forum post.
We think you haven't configured your NIC but need to see the results of ifconfig to be sure.
Hello again.
The first thing this shows is that your Network Interface Card (NIC) is recognised by Suse and is working, because it has an IP address.
The second thing this shows is that you are not receiving an IP address from the DHCP server because the address starts with 169.254 - These addresses are known as APIPA addresses.
First turn off ipv6 because it severely slows internet. Here's a link.
Second - you have not got connectivity with the DHCP server.
This is addressed one of two ways. But I cannot advise you further until I know which of the two ways you are connecting to the internet. So now I ask you this: Are you connecting to a router that connects to the modem or are you connecting directly to the modem?
And I ask you this: Is your modem a dial-up modem, a DSL/ADSL modem or a cable modem?
Please answer those two questions. In the meantime here is a picture for you to consider. Make things like Pic 4 and Pic 6.
You shouldnt need to obtain the dns informati9on from comcast as their network runs on a dynamic dns strucure which means that every time boot up you will automatically be asigned an Ip address fronm their dns servers. Thus you should be able to simply hook the catogory five cable from you modem directly into your Net work Interface Card (NIC) and surf to your hearts contenet.
Second - you have not got connectivity with the DHCP server.
This is addressed one of two ways. But I cannot advise you further until I know which of the two ways you are connecting to the internet. So now I ask you this: Are you connecting to a router that connects to the modem or are you connecting directly to the modem?
And I ask you this: Is your modem a dial-up modem, a DSL/ADSL modem or a cable modem?
hey thanks for reply...
i have a cable connection which is connected to a cable modem and than i am using RJ45 connection from cable modem to Laptop.
2) i have disabled ipv6 from Yast->Network->Network Card...selected the card
and in adavance option i have disable ipv6 so thats how i have disabled ipv6
3) i have installed oracle application 11i on my machine so i dont want to change my host domain....if it is possible....
Hello again sorry for delay - busy.
Your network card works because it has an APIPA address.
OK you should be getting a DHCP-provided IP address straight to your network Interface card (NIC) from Comcast according to flanksteak). That's normal. BUT you aren't. So what else? OK there are two questions: Authentication and connectivity. Solve connectivity first:
Check in Yast software management that these packages have been installed: dhcp-client, dhcpcd, dhcddb, dhcp - but I don't think that's the problem because that's installed by default.
Check that there are lights on the NIC socket indicating traffic to and from the cable modem - mine has a rapidly flashing green light showing network traffic.
Try replacing the ethernet cable.
Do you have a windows connection from the same machine with the same hardware - the only difference being dual-boot - to check the connectivity.
[*]Check in Yast software management that these packages have been installed: dhcp-client, dhcpcd, dhcddb, dhcp - but I don't think that's the problem because that's installed by default.
all are present
Quote:
[*]Check that there are lights on the NIC socket indicating traffic to and from the cable modem - mine has a rapidly flashing green light showing network traffic.
Mine too...constantly fleshing light
Quote:
[*]Try replacing the ethernet cable.[*]Do you have a windows connection from the same machine with the same hardware - the only difference being dual-boot - to check the connectivity.[/list]That's probably enough for the basics
i have dual boot Laptop with Windows XP Media Center. I can connect from Windows and writing this reply on the same.....
Hi navik_pathak, so the problem is not the connectivity, unless there's a problem in Linux regarding full recognition of the NIC - unlikely to be a problem there. It seems to narrow to the ISP-specific issues such as mac address, authentication, etc, of which I have no knowledge. You probably need someone understanding Comcast-specific issues to chime in now. It's interesting that flanksteak can simply hook up and surf - perhaps he can tell you what is his authentication client - or is it a question of Comcast "allowing" your specific mac address? Also talk to Comcast (if they will respond to a Linux questioner) regarding authentication and their gateway.
Another thought - since you can connect via windows with exactly the same hardware setup - you can obtain the correct DNS settings and gateway address for inserting into the NIC configuration under DHCP in Linux - from the windows command at start --> programs --> accessories --> command prompt: ipconfig/all
Clearly need more help from others if this doesn't help - plus talk to Comcast.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.