GNOME Bugzilla – Bug 731074
custom dnsmasq.conf extension for a "sharing internet" connection
Last modified: 2016-04-12 14:08:53 UTC
when enabling a "sharing internet" connection dnsmasq gets started with a fixed list of options. it is important to be able to extend these options for custom dhcp rules or tftp. currently the only way is doing: 1) disabling dns=dnsmasq 2) disabling share internet connection 3) create a dispatcher setting the iptables rules and starting the custom dnsmasq NetworkManager can do better ;-) allowing a custom per-connection dnsmasq --conf-file would make it much simpler. also, for this "advanced" usage of connection sharing it's important to be able to have post-up/pre-down dispatcher hooks.
Created attachment 277669 [details] lame dispatcher workaround I simply replicated the iptables rules you normally create, added one to allow tftp, and manually started dnsmasq with extra options for tftp
Created attachment 316579 [details] [review] Workaround patch It's my workaround
I agree. I have a PC with dual LAN motherboard, one connected to the Internet router and the other to a media player. I want assign a fixed IP to media player and it allows access to Internet through the other LAN. I can't do both things with actual NetworkManager.
I need to change lease time from 50m to 1m but since it is hard coded I can't do it now. I think its better to include a simple config option for such small tweaks. I need this for freedombox because freedombox uses NM for handling everything related to networking. I think if the option in line number 288 is given to the user will fix the problem. http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/dnsmasq-manager/nm-dnsmasq-manager.c#n288
(In reply to Bhuvan Krishna from comment #4) > I need to change lease time from 50m to 1m but since it is hard coded I > can't do it now. I think its better to include a simple config option for > such small tweaks. I need this for freedombox because freedombox uses NM for > handling everything related to networking. I think if the option in line > number 288 is given to the user will fix the problem. > > http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/dnsmasq- > manager/nm-dnsmasq-manager.c#n288 this is for NM version 1.0.10-1 for debian.
*** This bug has been marked as a duplicate of bug 761717 ***