Description of problem: See the attached text files Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: connection Additional info:
Created attachment 109841 [details] 3 text files
Can you try with a more recent version of NetworkManager? FC3-updates has a cvs20050119.2.fc3 version that has some DNS changes.
here is what drivers & versions on NM I have ipw2200-0.21-21.rhfc3.at <--- Wireless Driver NetworkManager-0.3.3-1.cvs20050119.2.fc3 NetworkManager-gnome-0.3.3-1.cvs20050119.2.fc3 all is working now...
the only problem i have now is when i reboot or shut down named causes errors if you would like, i could start a new bug pertaining to named. hered is what i have from var/log/messages Feb 3 09:56:01 JimsNotebook atd: atd shutdown succeeded Feb 3 09:56:02 JimsNotebook xfs[4045]: terminating Feb 3 09:56:03 JimsNotebook NetworkManager: exiting... Feb 3 09:56:03 JimsNotebook xfs: xfs shutdown succeeded Feb 3 09:56:03 JimsNotebook gpm: gpm shutdown succeeded Feb 3 09:56:03 JimsNotebook sshd: sshd -TERM succeeded Feb 3 09:56:03 JimsNotebook smartd[3957]: smartd received signal 15: Terminated Feb 3 09:56:03 JimsNotebook smartd[3957]: smartd is exiting (exit status 0) Feb 3 09:56:04 JimsNotebook smartd: smartd shutdown succeeded Feb 3 09:56:04 JimsNotebook kernel: audit(1107442564.740:0): avc: denied { read } for pid=15385 exe=/usr/sbin/rndc name=hosts dev=hda8 ino=460335 scontext=user_u:system_r:ndc_t tcontext=system_u:object_r:file_t tclass=file Feb 3 09:56:04 JimsNotebook kernel: audit(1107442564.755:0): avc: denied { read } for pid=15512 exe=/usr/sbin/rndc name=hosts dev=hda8 ino=460335 scontext=user_u:system_r:ndc_t tcontext=system_u:object_r:file_t tclass=file Feb 3 09:56:04 JimsNotebook acpid: acpid shutdown succeeded Feb 3 09:56:05 JimsNotebook crond: crond shutdown succeeded
Technically on FC3 you no longer need named+caching-nameserver, which will remain true for a long time. You can "yum remove bind caching-nameserver" and that should fix the issue... (or "rpm -e bind caching-nameserver")
Thats funny, after I started useing NM and couldn't connect to the internet, i was told that named needed to be running, and once it was, i was able to connect.
Should already be fixed in FC3 updates and FC4. FC3 no longer uses named.