This package has been removed from Ubuntu. Closing all related bugs.
** Changed in: firestarter (Ubuntu)
Status: Fix Committed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
when i ran into this problem again, i opened a the dhcp port for anyone
and that worked fine too as i use a non routable ip-range in mij
network.
hope this helps if someone google's this.
** Changed in: firestarter (Ubuntu)
Status: New = Fix Committed
--
You received this bug
It could also be that you have a adsl modem what does not resolve all
the names for you as you want, like say a Tomson modem, but if you are
correct in this, why does it do what it has to do, with the ' user-pre'
addition in my case and probably someone elses' .
regards.
On wo, 2009-07-08 at
dnsmasq takes care of so many headaches for a small network, this
problem was really killing me since firestarter is probably the best gui
front-end to iptables I've found.
But the above problem was plaguing me and the fix to user-pre above
didn't seem to help.
In case anyone does what I did, I
jaunty with dnsmasq. bug still present. firestarter launches dnsmasq but
blocks traffic to it. The workaround /etc/firestarter/user-pre doesn't
seem to work.
--
dnsmasq's dhcp blocked to clients by firestarter
https://bugs.launchpad.net/bugs/242869
You received this bug notification because you
A useful bit of information here: ISC dhcpd uses raw sockets to grab
incoming packets before they pass through the IP stack and IP tables, it
therefore doesn't suffer from problems caused by broken firewall rules.
Dnsmasq uses standard IP sockets so that all incoming packets are
filtered by
... 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
