Yes, IP's are the same when going from WinXP to Suse.
-----Original Message-----
From: Jeffrey L. Taylor [mailto:suse@austinblues.dyndns.org]
Sent: Monday, November 22, 2004 4:39 PM
To: suse-linux-e@suse.com
Subject: Re: [SLE] wireless card ipw2100
The wireless status info is less than 100%. There are several reasons
for this, some technical, some we-haven't-gotten-too-it-yet.
Are you using the same IP addresses in WinXP?
Jeffrey
Quoting Thom Nowakowski
Hello Jeffrey, thanks for the quick reply.
The only reason I have both eth0 and eth1 in my router because the only way I could paste that was to plug in my cat5 :P
I took out all instances of eth0 with the "route del" command but still no joy. Link still says ultimate but still nothing :(
My setup is as follows; |--- Server PC Broadband Modem -> wireless router ------ Main PC | ~~ Wireless
Wireless works great when I boot into WinXP, but not in Suse.
My Wireless Router is a 10/100 and 802.11b
I have the same symptoms at my work as well as at home.
From: Jeffrey L. Taylor [mailto:jeff.taylor@ieee.org] Sent: Monday, November 22, 2004 4:12 PM To: Thom Nowakowski Subject: Re: [SLE] wireless card ipw2100
You have both eth0 and eth1 on the same subnet. Tricky but doable. The access MUST be a bridge instead a simple router.
You have both eth0 and eth1 as the default route. This is unlikely to work. Also both interfaces for the 10.10.0.0/255.255.255.254.0 subnet.
For debugging purposes, I suggest taking eth0 down, removing it manually from the routing table if taking the interface down does not remove all eth0 routing info. Then try just eth1, the wireless interface.
Do you have a broadband router with both wired (10/100Base-T) and wireless (802.11a/b/g)?
Jeffrey
-- 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