https://bugzilla.novell.com/show_bug.cgi?id=308518#c2 Matej Horvath changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |jg@novell.com Component|YaST2 |Network --- Comment #2 from Matej Horvath 2007-09-07 01:51:05 MST --- This might be related to Bug 211102. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=308518#c4 --- Comment #4 from Glenn Conover 2007-09-07 02:43:38 MST --- Might be, you folks know more that I do :). In the same machine, I placed in a rt2500 card. The connection problem with the rt2500pci card was fixed with the posed patches in Bets 2 Here https://bugzilla.novell.com/show_bug.cgi?id=304119 YaST2 still keeps "No Zone, All traffic Blocked." with this card as well. I have tried rebooting and setting this a few times. I can bring this card online with a) Yast2 - setting it to internet zone b) command line ifup wlan1. Only after one of the two above do I get an IP, and I must do this for every boot. # hwinfo --netcard|grep "rt2500pci" Driver: "rt2500pci" Driver Modules: "rt2500pci" Driver Status: rt2500pci is active Driver Activation Cmd: "modprobe rt2500pci" again - I have attached yast2logs for the rt2500. hopefully help, and not a hinderance. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=308518#c6 Joachim Gleissner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |gconover@nmsu.edu --- Comment #6 from Joachim Gleissner 2007-11-27 06:52:16 MST --- Is this still an issue with 10.3 final? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.