[NTLUG:Discuss] Suse and knetwork manager

[Randall Weyers]

What is crazy is that the windoze works and eth0 works fine it is just
wireless
 On the suse  with 3.5 kde that is smoked


-----Original Message-----
From: discuss-bounces at ntlug.org [mailto:discuss-bounces at ntlug.org] On Behalf
Of terry
Sent: Thursday, April 02, 2009 5:11 PM
To: NTLUG Discussion List
Subject: Re: [NTLUG:Discuss] Suse and knetwork manager

Well, if you think it's the network-manager, just bypass it and initiate the
connection  yourself.

/sbin/dhclient eth1
/sbin/iwconfig
/sbin/iwconfig eth1 essid linksys
/sbin/dhclient eth1
where eth1 is the wifi device and linksys is the essid of  your AP

or
/sbin/iwconfig eth1 essid linksys ; /sbin/ifconfig eth1  192.168.1.77 ;
route add default gw 192.168.1.1

Test it:
host av.com


etc...



2009/4/2 Daniel Hauck <daniel at yacg.com>

> Randall Weyers さんは書きました:
> >
> >
> > Randall Weyers さんは書きました:
> >> Working until now.
> >>
> >> I have had Suse running fine for many months and never had an issue
> >> connecting with the wireless until this week. Now it sees the networks
> but
> >> cannot connect to them
> >>
> >>
> >> Any ideas.
> >> Suggestions to try...
> >>
> >
> > I can't speak for your problem, but with my Fedora laptop, I had an
> > issue like that when connecting to protected wireless networks where it
> > would only connect to unprotected ones.  Turned out to be an issue with
> > Network Manager.  I had tried not to put a password on the keychain
> > thing and it ended up preventing me from connecting to protected
> > wireless networks.  I resolved the problem by resetting things in the
> > keychain, but it sure took me a long time to figure it out.
> >
> > To start with, if you have control over a wireless access service
> > providing device, you might try temporarily unsecuring it and then try
> > connecting.  If it works, your problem may be similar to mine.
> >
> >
> > I even cleared the list of connections I had. I do have control and
> cannot
> > connect even unsecured. Where is the keychain
> >
>
> Since you are using SUSE and I presume KDE, I don't think I can offer
> any more than that.  When trying to connect, do you see anything in
> "dmesg" or /ver/log/messages about it?
>
> The keychain I speak of is probably a GNOME thing.
>
> Does this problem follow a software update?  If you have an old hard
> drive, perhaps you could pull your working one out, reinstall on the old
> drive to see if the problem doesn't come back after running updates?  (a
> bit time intensive...)
>
> _______________________________________________
> http://www.ntlug.org/mailman/listinfo/discuss
>



-- 
<><
_______________________________________________
http://www.ntlug.org/mailman/listinfo/discuss