Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): $ rpm -qa|grep NetworkManager NetworkManager-openvpn-0.8.999-1.fc15.x86_64 NetworkManager-glib-0.8.9997-1.git20110531.fc15.x86_64 NetworkManager-openconnect-0.8.999-1.fc15.x86_64 NetworkManager-gnome-0.8.9997-1.git20110531.fc15.x86_64 NetworkManager-vpnc-0.8.999-2.fc15.x86_64 NetworkManager-pptp-0.8.999-1.fc15.x86_64 NetworkManager-0.8.9997-1.git20110531.fc15.x86_64 How reproducible: Steps to Reproduce: 1. Install Fedora 15. 2. Create new ad-hoc wireless network on laptop. 3. Try connect to this wireless ad-hoc network. Actual results: Can't create an ad-hoc network. Network applet does not show this new network. If you try via 'other', it's trying and showing status "connecting", but fails with time-out/(reason 'ip-config-unavailable') error (or similar) later. Expected results: Should work as it is working fine in Fedora 14 in same laptop. Additional info: Related bug: 699203.
Do you see the Ad-Hoc network in output of $ nm-tool Could you attach /var/log/messages?
Created attachment 503214 [details] messages file from ad-hoc test.
No, can't see Ad-hoc network in nm-tool output. Ad-hoc network can be found from network settings - other. Uploaded the messages file from ad-hoc test.
Created attachment 503227 [details] Correct messages file.
Uploaded correct messages file - please ignore previous attachment 503214 [details].
The problem is you don't get IP address from DHCP server. Do you have one configured? Maybe you want to assign the connection '99' manual IP.
I get the IP address from dhcp server normally for eth0 (wired) from ISP provider in F15. This is same for F14 where ad-hoc works and I don't need set any manual IP for ad-hoc. So don't understand why it does not work in F15, but works in F14. Same laptop, same configuration (basic desktop installation) using automatic dhcp.
Found the reason. IPv4 settings was wrongly set. Works now. Thanks for comments and help! Definitely not a bug.
How your IPv4 settings were wrong and what to you changed them? What is that "the connection '99' manual IP" Jirka is referring? I have a problem of connecting to ad-hoc Wifi network also with Network Manager. I cannot seem to be able set static IP to it and default route through it in NM. I remember doing this in F14 with NM. The other end of the ad-hoc WLAN, N900, does not have DHCPD so static IP addresses should be used and configured in NM somehow.
IPv4 was not shared for others.
Similar here. Not very self-explaining error message. IPv6 has been set here as mandatory in a network without IPv6.