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 15:48 +0000, ded wrote: > 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 want to post the solution. I cut and > pated the above-line from my browser into the user-pre file and it > didn't work. What I finally discovered after banging my head on this > one for several days was that the --sport and --dport argument got > converted to and en-dash or some such non-ascii character by the browser > and were invalid. > > When you past the above, make sure to change them! > > I found this by running "firestarter --start" from the command line, > which will echo all the iptables errors to the console. I found several > other problems with my firestarter configuration this way as well. For > example, I found that it was unable to resolve the "hostnames" I used in > several rules, so they weren't getting into the firewall. I had to > hard-code IP addresses instead. > > I hope this helps someone else. > > Regards, > > ded > -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
