[intrepid] network-manager should recommend or suggest dnsmasq

dnsmasq-base only, as dnsmasq runs a daemon which prevents network manager's command line invocation of the binary. documentation for nm is so appalling.

Fedore connection sharing how-to [1] not work form me.

I've installed dnsmasq-base and created new wireless connection.

Can you explain step-by-step process to share connection using network-manager and dnsmasq?

[1] http://www.redhatmagazine.com/2008/10/16/video-fedora-10-connection-sharing/

I'm sorry, aftwer restarting it works, but the winxp lapton continue to connect and disconnect.

This's the log:

I change many lines like this
Nov 8 17:04:30 intrepid NetworkManager: <info> (eth1): supplicant connection state change: 7 -> 4
Nov 8 17:04:30 intrepid NetworkManager: <info> (eth1): supplicant connection state change: 4 -> 7
with "..."

Nov 8 17:04:05 intrepid NetworkManager: <info> (eth1): device state change: 5 -> 7
Nov 8 17:04:05 intrepid NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) scheduled...
Nov 8 17:04:05 intrepid NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) complete.
Nov 8 17:04:05 intrepid NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) started...
Nov 8 17:04:05 intrepid NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) scheduled...
Nov 8 17:04:05 intrepid NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) complete.
Nov 8 17:04:05 intrepid NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) started...
Nov 8 17:04:05 intrepid avahi-daemon[5487]: Joining mDNS multicast group on interface eth1.IPv4 with address 10.42.45.1.
Nov 8 17:04:05 intrepid avahi-daemon[5487]: New relevant interface eth1.IPv4 for mDNS.
Nov 8 17:04:05 intrepid avahi-daemon[5487]: Registering new address record for 10.42.45.1 on eth1.IPv4.
Nov 8 17:04:06 intrepid NetworkManager: <info> Policy set 'Auto eth0' (eth0) as default for routing and DNS.
Nov 8 17:04:07 intrepid NetworkManager: <info> Executing: /sbin/iptables --table filter --insert INPUT --in-interface eth1 --protocol tcp --destination-port 53 --jump ACCEPT
Nov 8 17:04:07 intrepid NetworkManager: <info> Executing: /sbin/iptables --table filter --insert INPUT --in-interface eth1 --protocol udp --destination-port 53 --jump ACCEPT
Nov 8 17:04:07 intrepid NetworkManager: <info> Executing: /sbin/iptables --table filter --insert INPUT --in-interface eth1 --protocol tcp --destination-port 67 --jump ACCEPT
Nov 8 17:04:07 intrepid NetworkManager: <info> Executing: /sbin/iptables --table filter --insert INPUT --in-interface eth1 --protocol udp --destination-port 67 --jump ACCEPT
Nov 8 17:04:07 intrepid NetworkManager: <info> Executing: /sbin/iptables --table filter --insert FORWARD --in-interface eth1 --jump REJECT
Nov 8 17:04:07 intrepid NetworkManager: <info> Executing: /sbin/iptables --table filter --insert FORWARD --out-interface eth1 --jump REJECT
Nov 8 17:04:07 intrepid NetworkManager: <info> Executing: /sbin/iptables --table filter --insert FORWARD --in-interface eth1 --out-interface eth1 --jump ACCEPT
Nov 8 17:04:07 intrepid NetworkManager: <info> Executing: /sbin/iptables --table filter --insert FORWARD --source 10.42.45.0/255.255.255.0 --in-interface eth1 --jump ACCEPT
Nov 8 17:04:07 intrepid NetworkManager: <info> Executing: /sbin/iptables --table filter --insert FORWARD --destination 10.42.45.0/255.255.255.0 --out-interface eth1 --match state --state ESTABLISHED,RELATED --jump ACCEPT
Nov 8 17:04:07 intrepid NetworkManager: <info> Executing: /sbin/iptables --table nat --insert P...

I can confirm connection sharing works correctly after installing dnsmasq-base. I agree that it should be a recommends.

I don't understand why dnsmasq-base would help for connection sharing? Is this a DNS issue?

ok I think i understand. Is just -base really enough?

Yeah it appears -base is all that is needed.

Can confirm it suffices. I tried to provide a debdiff but missed up with versioning. The fact there is a "Fix available" implies that we can hope to see it backported to Intrepid?

Why isn't this installed by default? It's less than 1 mg. What about when you try to create a wireless network, network-manager goes "Hey, you need dnsmasq-base in order to do this. Do you want to install it now?" I agree, it is very silly that this information isn't made more obvious to the end user. And all this time I thought the wireless card in my laptop was crap!

I agree. I've been trying to share a connection for some time now, if I would have found this page earlier, it would have saved a lot of time! ;)

Plus nm-applet really shouldn't segfault because it can't find the binary. I was away from network connectivity (as you usually are when you try to ad-hoc, otherwise you'd just both connect to the infrastructure) when I tried this a couple of days ago.

Thankfully we are both experienced sysadmins who were happy to go nuke the network-manager processes and iwconfig/ifconfig ourselves. Left a pretty sour taste seeing nm-applet crash and disappear.

Dec 28 19:06:15 launde NetworkManager: <WARN> start_sharing(): (wlan0): failed to start dnsmasq: Could not find dnsmasq binary.

I ran nm-applet from the command line and it actually segfaulted when it couldn't find dnsmasq. It definitely needs to fail gracefully.

This is needed for jaunty as well.

Just wanted to point out that this isn't just about sharing connections, but in fact affects *all* ad-hoc networks. I think dnsmasq-base should be a *requirement*, not just suggested, because Network Manager presents in its menus features that just don't work without it. If it's broken without it, it should be considered a requirement. my 2c.

has anyone had trouble with running dnsmasq service, AND letting network manager try to run individual dnsmasq processes? this affected me in intrepid.

this might change the dependency requirement, and/or be another bug.

dnsmasq provides dbus methods

network manager ignores whether dnsmasq service is running, and tries to instantiate new listeners on the interfaces it has brought up.

network manager therefore CONFLICTS with "dnsmasq" and this should be marked, so people don't install dnsmasq (which should be Depends) and dnsmasq (which would ruin everything).

to run dnsmasq as invoked automatically by network manager (since it doesn't use the dbus methods in the ubuntu build), you have to configure dnsmasq to only listen on interfaces which network manager will not need.

Typiclly, this means that you can set dnsmasq.conf to only listen on your wired connection, and ignore your wifi connections that you want to share.

Once this change is made, and dnsmasq restared, nm can then invoke dnsmasq successfully.

Use of the DBUS methods would of course make this all a lot easier.

This has been fixed in Jaunty with today's network manager upload:

0.7.1~rc4-0ubuntu1
Published in jaunty-release 8 hours ago

network-manager (0.7.1~rc4-0ubuntu1) jaunty; urgency=low

  * upstream release 0.7.1 rc4
    + http://git.freedesktop.org/NetworkManager/NetworkManager/
    + NETWORKMANAGER_0_7 (branch)
      - dont send AT commands to serial consoles that are not using a modem driver
      - nozomi probing (LP: #351803)
      - allow users with polkit authorization to view/edit secrets for system connections
      - fix crash that might be LP: #319918
  * allow connection sharing out of the box; we add dnsmasq-base to Recommends:
    - update control

 -- Alexander Sack < <email address hidden>> Mon, 06 Apr 2009 12:43:31 +0200