NM 0.9.6 not setting up adhoc with static settings




I have a hard-coded adhoc network setup with a fixed ssid, channel, bssid, and
IPv4 address.  This profile works fine on Ubuntu/Precise (network-manager
v0.9.4.0-0ubuntu4) but fails on Ubuntu/quantal (network-manager
v0.9.6.0-0ubuntu7) .  On 0.9.6, it says its setting all those settings, but
then actually tries on channel 1 instead, and it dynamically generates a BSSID
rather than using the one in the config file that it said it was going to
load. Attached is the NM connection file and the log from syslog.

Here's iwconfig:
eth0      IEEE 802.11abg  ESSID:"commotionwireless.net"
          Mode:Ad-Hoc  Frequency:2.412 GHz  Cell: 9E:F3:90:CF:07:2B

The Ubuntu/Precise/12.04 machines have these wifis:
0b:00.0 Network controller: Atheros Communications Inc. AR5418 Wireless
Network Adapter [AR5008E 802.11(a)bgn] (PCI-Express) (rev 01)
02:00.0 Ethernet controller: Atheros Communications Inc. AR242x / AR542x
Wireless Network Adapter (PCI-Express) (rev 01)

The Ubuntu/Quantal/12.10 machine has this wifi:
01:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)

The idea here is to automatically attach to an OLSR mesh network, which
requires a fixed SSID, channel, and BSSID.  Any ideas how to make NM 0.9.6
work properly like NM 0.9.4?

.hc

Attachment: syslog.txt
Description: Text document

Attachment: commotionwireless.net
Description: Text document



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]