Re: [Dnsmasq-discuss] Very accurate bandwidth tracking...

2011-05-11 Thread Ed W
On 11/05/2011 14:59, Simon Kelley wrote: > > CAP_NETADMIN is already in use for the DHCP side, so that's not a problem. > Libnetfilter_conntrac dependency is a bit of a problem, but should be OK. > I hadn't noticed that subtlety that it needs to depend on conntrack... However, superb if it's po

Re: [Dnsmasq-discuss] Serve DNS requests to hosts outside subnet

2011-05-11 Thread Pepe Barbe
On May 11, 2011, at 2:03 AM, SamLT wrote: > Ok, so you see the requests using tcpdump, but dnsmasq doesn't seem to > get them, or does it?(do you see them in the dnsmasq log(probably > daemon.log), remember to enable --log-queries first) > > If dnsmasq does not get the requests, then your firewa

Re: [Dnsmasq-discuss] Very accurate bandwidth tracking...

2011-05-11 Thread Simon Kelley
"richardvo...@gmail.com" wrote: >On Wed, May 11, 2011 at 4:03 AM, Ed W wrote: >> On 11/05/2011 01:32, richardvo...@gmail.com wrote: Note that it's the nf_mark we will be setting. But:        get/setsockopt(fd, SOL_SOCKET, SO_MARK, ...) >>> That allows you to set a mark for your outgoin

Re: [Dnsmasq-discuss] Very accurate bandwidth tracking...

2011-05-11 Thread richardvo...@gmail.com
On Wed, May 11, 2011 at 4:03 AM, Ed W wrote: > On 11/05/2011 01:32, richardvo...@gmail.com wrote: >>> Note that it's the nf_mark we will be setting. But: >>>        get/setsockopt(fd, SOL_SOCKET, SO_MARK, ...) >> That allows you to set a mark for your outgoing packets, and find out >> what mark is

Re: [Dnsmasq-discuss] Very accurate bandwidth tracking...

2011-05-11 Thread Ed W
On 11/05/2011 01:32, richardvo...@gmail.com wrote: > There's still a large piece of the puzzle missing, namely finding out > what mark is carried by incoming requests, since this determines that > mark that goes on the forwarded query (when it cannot be answered from > cache). Just to phrase my l

Re: [Dnsmasq-discuss] Very accurate bandwidth tracking...

2011-05-11 Thread Ed W
On 11/05/2011 01:32, richardvo...@gmail.com wrote: >> Note that it's the nf_mark we will be setting. But: >>get/setsockopt(fd, SOL_SOCKET, SO_MARK, ...) > That allows you to set a mark for your outgoing packets, and find out > what mark is in effect on outgoing packets. > > There's still a

Re: [Dnsmasq-discuss] Serve DNS requests to hosts outside subnet

2011-05-11 Thread Jan Psota
> I would like to resolve domains using it from the clients that are > connected via the VPN, but it haven't figured out how, the clients can > reach dnsmasq but the requests are refused. to complicate things, the > VPN with racoon does not offer any kind of interface to bind, all the > routing is

Re: [Dnsmasq-discuss] Serve DNS requests to hosts outside subnet

2011-05-11 Thread SamLT
On Wed, May 11, 2011 at 12:58:09AM -0500, Pepe Barbe wrote: > > On May 11, 2011, at 12:55 AM, SamLT wrote: > > > How do you see those requests got refused? which log(firewall? dnsmasq > > itself??) > > I see them refused using tcpdump. Also using host domain dnsmasq_ip returns > the answer REFU

Re: [Dnsmasq-discuss] Serve DNS requests to hosts outside subnet

2011-05-11 Thread Pepe Barbe
On May 11, 2011, at 12:55 AM, SamLT wrote: > How do you see those requests got refused? which log(firewall? dnsmasq > itself??) I see them refused using tcpdump. Also using host domain dnsmasq_ip returns the answer REFUSED. Pepe

Re: [Dnsmasq-discuss] Serve DNS requests to hosts outside subnet

2011-05-11 Thread SamLT
On Tue, May 10, 2011 at 04:57:57PM -0500, Pepe Barbe wrote: > Hello all, Hello > > I have a VPN setup using IPSec with racoon to access as specific subnet, > where dnsmasq runs as a DNS and DHCP server. > > I would like to resolve domains using it from the clients that are connected > via th

Re: [Dnsmasq-discuss] Very accurate bandwidth tracking...

2011-05-11 Thread richardvo...@gmail.com
> Note that it's the nf_mark we will be setting. But: >        get/setsockopt(fd, SOL_SOCKET, SO_MARK, ...) That allows you to set a mark for your outgoing packets, and find out what mark is in effect on outgoing packets. There's still a large piece of the puzzle missing, namely finding out what