Bug 710835

Summary: Unable to connect to ad-hoc WiFi network
Product: [Fedora] Fedora Reporter: Jarmo <rh>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: dcbw, jklimes, milan.kerslager, zimon
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-07 15:26:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
messages file from ad-hoc test.
none
Correct messages file. none

Description Jarmo 2011-06-05 07:10:32 UTC 
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.
Comment 1 Jirka Klimes 2011-06-06 08:35:58 UTC 
Do you see the Ad-Hoc network in output of
$ nm-tool

Could you attach /var/log/messages?
Comment 2 Jarmo 2011-06-06 12:59:57 UTC 
Created attachment 503214 [details]
messages file from ad-hoc test.
Comment 3 Jarmo 2011-06-06 13:02:29 UTC 
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.
Comment 4 Jarmo 2011-06-06 13:49:05 UTC 
Created attachment 503227 [details]
Correct messages file.
Comment 5 Jarmo 2011-06-06 13:50:15 UTC 
Uploaded correct messages file - please ignore previous attachment 503214 [details].
Comment 6 Jirka Klimes 2011-06-07 13:07:07 UTC 
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.
Comment 7 Jarmo 2011-06-07 13:28:08 UTC 
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.
Comment 8 Jarmo 2011-06-07 15:26:02 UTC 
Found the reason. IPv4 settings was wrongly set. Works now.
Thanks for comments and help!
Definitely not a bug.
Comment 9 zimon 2011-08-03 00:17:32 UTC 
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.
Comment 10 Jarmo 2011-08-03 16:32:23 UTC 
IPv4 was not shared for others.
Comment 11 Milan Kerslager 2011-08-18 20:38:08 UTC 
Similar here. Not very self-explaining error message.

IPv6 has been set here as mandatory in a network without IPv6.