[Bug 242869] Re: dnsmasq's dhcp blocked to clients by firestarter

[ubun2-fan]

... maybe it's not a bug, but it might be handy to fix this by the
install script of dnsmasq if firestarter is detected.

** Description changed:

  Binary package hint: firestarter
  
  server: hardy, clients hardy.
  In a situation where firestarter  is sharing the internet connection and act as a firewall, dnsmasq's dhcp server can not be reached by clients. Shutting down firestarter, all works fine, except the sharing of internet. Enable firstarter again, no dhcp.
  
  The iptables rules decide that all destination traffic to
  255.255.255.255 from source 0.0.0.0 (unknown) (even if the port is
  67-68) will be dropped. (so no new dhcp requests)
  
  The workaround was to add the following line to /etc/firestarter/user-
  pre to explicitly allow the DHCP broadcasts early in the INPUT table:
  
  $IPT -A INPUT -i $INIF -p udp -s 0.0.0.0 –sport 68 -d 255.255.255.255 –dport 67 -j ACCEPT 
  (thanks Andrew)
  
  But i think firestarter should solve this. All new dhcp  resolving is
  done by sending packets to 255.255.255.255 from source 0.0.0.0.
  
+ ... maybe it's not a bug, but it might be handy to fix this by the
+ install script of dnsmasq if firestarter is detected.
+ 
  I hope this helps.
  
  Regards. ... ow.. and keep up the good work ;)

** Description changed:

  Binary package hint: firestarter
  
  server: hardy, clients hardy.
  In a situation where firestarter  is sharing the internet connection and act as a firewall, dnsmasq's dhcp server can not be reached by clients. Shutting down firestarter, all works fine, except the sharing of internet. Enable firstarter again, no dhcp.
  
  The iptables rules decide that all destination traffic to
  255.255.255.255 from source 0.0.0.0 (unknown) (even if the port is
  67-68) will be dropped. (so no new dhcp requests)
  
  The workaround was to add the following line to /etc/firestarter/user-
  pre to explicitly allow the DHCP broadcasts early in the INPUT table:
  
  $IPT -A INPUT -i $INIF -p udp -s 0.0.0.0 –sport 68 -d 255.255.255.255 –dport 67 -j ACCEPT 
  (thanks Andrew)
  
  But i think firestarter should solve this. All new dhcp  resolving is
  done by sending packets to 255.255.255.255 from source 0.0.0.0.
  
- ... maybe it's not a bug, but it might be handy to fix this by the
- install script of dnsmasq if firestarter is detected.
  
  I hope this helps.
  
  Regards. ... ow.. and keep up the good work ;)

-- 
dnsmasq's dhcp blocked to clients by firestarter
https://bugs.launchpad.net/bugs/242869
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in ubuntu.