knetworkmanager can't share the connection • KDE Community Forums

This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Board index

knetworkmanager can't share the connection

Page 1 of 1 (9 posts)

Tags:

speedyx Registered Member Posts 13 Karma 0 OS	knetworkmanager can't share the connection Sat Mar 12, 2011 4:59 pm I used to share my mobile connection with kde to other notebook I have with kde. I installed Chakra with kde 4.6.1 on a netbook with this wifi card: Atheros AR5001 Wireless Network Adapter driver ath5k I used to create in knetworkmanager a connection ad-hoc and shared without password. But knm cannot create. I can connect other wireless networks. I can't create a shared connection. knetworkmanager, after trying to obtain a network address fail. Have you some suggestion? networkmanagement 20110226-1 networkmanager 0.8.2-3 I have chakra stable 2011.02 Mar 12 14:38:33 chakra-pc NetworkManager[1972]: <info> Activation (wlan0) starting connection 'home-server' Mar 12 14:38:33 chakra-pc NetworkManager[1972]: <info> (wlan0): device state change: 3 -> 4 (reason 0) Mar 12 14:38:33 chakra-pc NetworkManager[1972]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Mar 12 14:38:33 chakra-pc NetworkManager[1972]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Mar 12 14:38:33 chakra-pc NetworkManager[1972]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Mar 12 14:38:33 chakra-pc NetworkManager[1972]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Mar 12 14:38:33 chakra-pc NetworkManager[1972]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Mar 12 14:38:33 chakra-pc NetworkManager[1972]: <info> (wlan0): device state change: 4 -> 5 (reason 0) Mar 12 14:38:33 chakra-pc NetworkManager[1972]: <info> Activation (wlan0/wireless): connection 'home-server' requires no security. No secrets needed. Mar 12 14:38:33 chakra-pc NetworkManager[1972]: <info> Config: added 'ssid' value 'mynet' Mar 12 14:38:33 chakra-pc NetworkManager[1972]: <info> Config: added 'mode' value '1' Mar 12 14:38:33 chakra-pc NetworkManager[1972]: <info> Config: added 'frequency' value '2412' Mar 12 14:38:33 chakra-pc NetworkManager[1972]: <info> Config: added 'key_mgmt' value 'NONE' Mar 12 14:38:33 chakra-pc NetworkManager[1972]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Mar 12 14:38:33 chakra-pc NetworkManager[1972]: <info> (wlan0): supplicant connection state: scanning -> disconnected Mar 12 14:38:33 chakra-pc NetworkManager[1972]: <info> Config: set interface ap_scan to 2 Mar 12 14:38:33 chakra-pc kernel: wlan0: Trigger new scan to find an IBSS to join Mar 12 14:38:33 chakra-pc NetworkManager[1972]: <info> (wlan0): supplicant connection state: disconnected -> scanning Mar 12 14:38:33 chakra-pc NetworkManager[1972]: <info> (wlan0): supplicant connection state: scanning -> associating Mar 12 14:38:37 chakra-pc kernel: wlan0: Trigger new scan to find an IBSS to join Mar 12 14:38:42 chakra-pc kernel: wlan0: Trigger new scan to find an IBSS to join Mar 12 14:38:43 chakra-pc kernel: wlan0: Creating new IBSS network, BSSID f6:c9:ea:b7:59:3b Mar 12 14:38:43 chakra-pc NetworkManager[1972]: <info> (wlan0): supplicant connection state: associating -> associated Mar 12 14:38:43 chakra-pc NetworkManager[1972]: <info> (wlan0): supplicant connection state: associated -> completed Mar 12 14:38:43 chakra-pc NetworkManager[1972]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'mynet'. Mar 12 14:38:43 chakra-pc NetworkManager[1972]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled. Mar 12 14:38:43 chakra-pc NetworkManager[1972]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started... Mar 12 14:38:43 chakra-pc NetworkManager[1972]: <info> (wlan0): device state change: 5 -> 7 (reason 0) Mar 12 14:38:43 chakra-pc NetworkManager[1972]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled... Mar 12 14:38:43 chakra-pc NetworkManager[1972]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. Mar 12 14:38:43 chakra-pc NetworkManager[1972]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started... Mar 12 14:38:43 chakra-pc NetworkManager[1972]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled... Mar 12 14:38:43 chakra-pc NetworkManager[1972]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete. Mar 12 14:38:43 chakra-pc NetworkManager[1972]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started... Mar 12 14:38:43 chakra-pc avahi-daemon[1988]: Joining mDNS multicast group on interface wlan0.IPv4 with address 10.42.43.1. Mar 12 14:38:43 chakra-pc avahi-daemon[1988]: New relevant interface wlan0.IPv4 for mDNS. Mar 12 14:38:43 chakra-pc avahi-daemon[1988]: Registering new address record for 10.42.43.1 on wlan0.IPv4. Mar 12 14:38:44 chakra-pc NetworkManager[1972]: <info> Policy set 'IProvider' (ppp0) as default for IPv4 routing and DNS. Mar 12 14:38:44 chakra-pc NetworkManager[1972]: <info> Executing: /usr/sbin/iptables --table filter --insert INPUT --in-interface wlan0 --protocol tcp --destination-port 53 --jump ACCEPT Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> Executing: /usr/sbin/iptables --table filter --insert INPUT --in-interface wlan0 --protocol udp --destination-port 53 --jump ACCEPT Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> Executing: /usr/sbin/iptables --table filter --insert INPUT --in-interface wlan0 --protocol tcp --destination-port 67 --jump ACCEPT Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> Executing: /usr/sbin/iptables --table filter --insert INPUT --in-interface wlan0 --protocol udp --destination-port 67 --jump ACCEPT Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> Executing: /usr/sbin/iptables --table filter --insert FORWARD --in-interface wlan0 --jump REJECT Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> Executing: /usr/sbin/iptables --table filter --insert FORWARD --out-interface wlan0 --jump REJECT Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> Executing: /usr/sbin/iptables --table filter --insert FORWARD --in-interface wlan0 --out-interface wlan0 --jump ACCEPT Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> Executing: /usr/sbin/iptables --table filter --insert FORWARD --source 10.42.43.0/255.255.255.0 --in-interface wlan0 --jump ACCEPT Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> Executing: /usr/sbin/iptables --table filter --insert FORWARD --destination 10.42.43.0/255.255.255.0 --out-interface wlan0 --match state --state ESTABLISHED,RELATED --jump ACCEPT Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> Executing: /usr/sbin/iptables --table nat --insert POSTROUTING --source 10.42.43.0/255.255.255.0 --destination ! 10.42.43.0/255.255.255.0 --jump MASQUERADE Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <error> [1299937125.81795] [nm-device.c:2470] start_sharing(): (wlan0/wlan0): failed to start dnsmasq: Could not find dnsmasq binary. Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> Executing: /usr/sbin/iptables --table nat --delete POSTROUTING --source 10.42.43.0/255.255.255.0 --destination ! 10.42.43.0/255.255.255.0 --jump MASQUERADE Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> Executing: /usr/sbin/iptables --table filter --delete FORWARD --destination 10.42.43.0/255.255.255.0 --out-interface wlan0 --match state --state ESTABLISHED,RELATED --jump ACCEPT Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> Executing: /usr/sbin/iptables --table filter --delete FORWARD --source 10.42.43.0/255.255.255.0 --in-interface wlan0 --jump ACCEPT Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> Executing: /usr/sbin/iptables --table filter --delete FORWARD --in-interface wlan0 --out-interface wlan0 --jump ACCEPT Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> Executing: /usr/sbin/iptables --table filter --delete FORWARD --out-interface wlan0 --jump REJECT Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> Executing: /usr/sbin/iptables --table filter --delete FORWARD --in-interface wlan0 --jump REJECT Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> Executing: /usr/sbin/iptables --table filter --delete INPUT --in-interface wlan0 --protocol udp --destination-port 67 --jump ACCEPT Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> Executing: /usr/sbin/iptables --table filter --delete INPUT --in-interface wlan0 --protocol tcp --destination-port 67 --jump ACCEPT Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> Executing: /usr/sbin/iptables --table filter --delete INPUT --in-interface wlan0 --protocol udp --destination-port 53 --jump ACCEPT Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> Executing: /usr/sbin/iptables --table filter --delete INPUT --in-interface wlan0 --protocol tcp --destination-port 53 --jump ACCEPT Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <warn> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) start sharing failed. Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> (wlan0): device state change: 7 -> 9 (reason 18) Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <warn> Activation (wlan0) failed for access point (mynet) Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> Marking connection 'home-server' invalid. Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <warn> Activation (wlan0) failed. Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete. Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> (wlan0): device state change: 9 -> 3 (reason 0) Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> (wlan0): deactivating device (reason: 0). Mar 12 14:38:45 chakra-pc avahi-daemon[1988]: Withdrawing address record for 10.42.43.1 on wlan0. Mar 12 14:38:45 chakra-pc avahi-daemon[1988]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 10.42.43.1. Mar 12 14:38:45 chakra-pc avahi-daemon[1988]: Interface wlan0.IPv4 no longer relevant for mDNS. Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> Policy set 'IProvider' (ppp0) as default for IPv4 routing and DNS. Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <info> Policy set 'IProvider' (ppp0) as default for IPv4 routing and DNS. Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <error> [1299937125.164502] [nm-device-wifi.c:1544] nm_device_wifi_set_mode(): (wlan0): error setting mode 2 The Freedom Technologies Are Available! I love KDE!
bcooksley Administrator Posts 19765 Karma 87 OS	Re: knetworkmanager can't share the connection Sat Mar 12, 2011 8:18 pm Code: Select all `Mar 12 14:38:45 chakra-pc NetworkManager[1972]: <error> [1299937125.81795] [nm-device.c:2470] start_sharing(): (wlan0/wlan0): failed to start dnsmasq: Could not find dnsmasq binary.` Please install dnsmasq. KDE Sysadmin [img]content/bcooksley_sig.png[/img]
speedyx Registered Member Posts 13 Karma 0 OS	Re: knetworkmanager can't share the connection Sat Mar 12, 2011 9:26 pm bcooksley wrote:Please install dnsmasq. Thank you very much! I try soon! The Freedom Technologies Are Available! I love KDE!
speedyx Registered Member Posts 13 Karma 0 OS	Re: knetworkmanager can't share the connection Sat Mar 12, 2011 10:55 pm No dnsmasq not solved the problem. The Freedom Technologies Are Available! I love KDE!
speedyx Registered Member Posts 13 Karma 0 OS	Re: knetworkmanager can't share the connection Sun Mar 13, 2011 9:26 pm If you think dnsmasq is the way, how should I configure that? The Freedom Technologies Are Available! I love KDE!
aqeeliz Registered Member Posts 11 Karma 0 OS	Re: knetworkmanager can't share the connection Mon Mar 14, 2011 4:09 pm dnsmasq doesn't need any configuration. It usually works out of the box, if you still can't connect, post relevant part of /var/log/messages again. I am having same problem, shared connections were working fine, but they aren't working now. Assuming you are having the same problem, as my /var/log/messages is identical, with exception of dnsmasq lines: Code: Select all ... ... Mar 14 20:55:31 aqeel-laptop NetworkManager[1339]: <info> Executing: /usr/sbin/iptables --table filter --insert FORWARD --destination 10.42.43.0/255.255.255.0 --out-interface wlan0 --match state --state ESTABLISHED,RELATED --jump ACCEPT Mar 14 20:55:31 aqeel-laptop NetworkManager[1339]: <info> Executing: /usr/sbin/iptables --table nat --insert POSTROUTING --source 10.42.43.0/255.255.255.0 --destination ! 10.42.43.0/255.255.255.0 --jump MASQUERADE Mar 14 20:55:31 aqeel-laptop NetworkManager[1339]: <info> Starting dnsmasq... Mar 14 20:55:31 aqeel-laptop NetworkManager[1339]: <info> (wlan0): device state change: 7 -> 8 (reason 0) Mar 14 20:55:31 aqeel-laptop NetworkManager[1339]: <info> Activation (wlan0) successful, device activated. Mar 14 20:55:31 aqeel-laptop NetworkManager[1339]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete. Mar 14 20:55:31 aqeel-laptop NetworkManager[1339]: <warn> dnsmasq exited with error: Configuration problem (1) Mar 14 20:55:31 aqeel-laptop NetworkManager[1339]: <info> (wlan0): device state change: 8 -> 9 (reason 18) Mar 14 20:55:31 aqeel-laptop NetworkManager[1339]: <warn> Activation (wlan0) failed for access point (aqeel-laptop) Mar 14 20:55:31 aqeel-laptop NetworkManager[1339]: <warn> Activation (wlan0) failed. Mar 14 20:55:31 aqeel-laptop NetworkManager[1339]: <info> (wlan0): device state change: 9 -> 3 (reason 0) Mar 14 20:55:31 aqeel-laptop NetworkManager[1339]: <info> (wlan0): deactivating device (reason: 0). Mar 14 20:55:31 aqeel-laptop avahi-daemon[1373]: Withdrawing address record for 10.42.43.1 on wlan0. Mar 14 20:55:31 aqeel-laptop avahi-daemon[1373]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 10.42.43.1. Mar 14 20:55:31 aqeel-laptop avahi-daemon[1373]: Interface wlan0.IPv4 no longer relevant for mDNS. Update: Apparently the problem is the recent update of dnsmasq (and maybe the way networkmanager uses it), everyone is having problem. If you search online, there are atleast dozens of posts from feb. Here are few links: https://bugs.launchpad.net/ubuntu/+sour ... bug/725041 http://us.generation-nt.com/answer/bug- ... 01812.html https://bugs.archlinux.org/task/23078?p ... om=-1+week
speedyx Registered Member Posts 13 Karma 0 OS	Re: knetworkmanager can't share the connection Mon Mar 14, 2011 5:30 pm Interesting your search and observation. I have now only one issue: Mar 14 07:09:05 chakra-pc NetworkManager[2084]: <error> [1300082945.419707] [nm-device-wifi.c:1544] nm_device_wifi_set_mode(): (wlan0): error setting mode 2 The Freedom Technologies Are Available! I love KDE!
bcooksley Administrator Posts 19765 Karma 87 OS	Re: knetworkmanager can't share the connection Wed Mar 16, 2011 6:07 am You might be affected by this as well - https://bugs.launchpad.net/network-manager/+bug/75358 KDE Sysadmin [img]content/bcooksley_sig.png[/img]
nikiobicata Registered Member Posts 1 Karma 0	Re: knetworkmanager can't share the connection Wed Mar 23, 2011 8:18 pm speedyx wrote:Interesting your search and observation. I have now only one issue: Mar 14 07:09:05 chakra-pc NetworkManager[2084]: <error> [1300082945.419707] [nm-device-wifi.c:1544] nm_device_wifi_set_mode(): (wlan0): error setting mode 2 Administrator thank you for this ! Just what i look in for

Page 1 of 1 (9 posts)

Bookmarks

Who is online

Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]