On 30/07/06 21:41, John Andersen wrote:
On Sunday 30 July 2006 15:56, Jerry Feldman wrote:
The physical connections look good. I've tried with a cable I know works, and I get the same problem.
I would suggest that you assign a static IP address. You can do this with ifconfig: ifconfig eth0 <address> Your router should be set for 192.168.1.n where 1 < n < 100. Usually routers use 100 to 254 for dynamic. The see if it works. Piong either something on your subnet or external.
What are you talking about?
I just talked him out of using a static. It masks the problem of no connectivity by letting you THINK you've got connectivity when you DON'T.
What are *you* talking about? The only way to determine if you have connectivity is to actually try to connect to something. Failing a DHCP request attempt tells you no more about the problems of your network than failing a ping, or an attempt to connect to some server. Only the raw rookie would think he had connectivity simply because he has an IP, but forgot it was assigned statically.
In his first post He was convinced he had connectivity because he had an IP. Turned out he manually assigned it. When he printed his iwconfig outout it was clear not a single packet had passed and he had no connectivity at all. Its a hardware problem.
People who recommend assigning manual IPs on network segments that have a working dhcp server don't know what they are doing. Its not a good way to solve problems. Its deceptive, and disruptive to other users on the subnet. Its unnecessary, and does not solve a cabling problem, or a dribble connection, or a switch problem.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com