[Dnsmasq-discuss] address=/#/192.168.0.1 - does not work!

2013-12-09 Thread Nikita N.
Hi All, its the first time for me on this maillist :) Im trying some tests with dnsmasq, but I cant make it work.. sorry :( I dont know if its a bug.. or its just me missing something.. So here what I want to do: I created a tap ethernet interface (on wireless, because I have only that, but

Re: [Dnsmasq-discuss] address=/#/192.168.0.1 - does not work!

2013-12-09 Thread Albert ARIBAUD
Le 09/12/2013 09:29, Nikita N. a écrit : Hi All, its the first time for me on this maillist :) Im trying some tests with dnsmasq, but I cant make it work.. sorry :( I dont know if its a bug.. or its just me missing something.. So here what I want to do: I created a tap ethernet interface (on

Re: [Dnsmasq-discuss] address=/#/192.168.0.1 - does not work!

2013-12-09 Thread Nikita N.
Hi Albert :) what I wrote you is what in fact I *see* from Wireshark. I see all traffic there, I see exactly when and where appears the frame into at0, the DHCP and DNS request frames from me, the correct answers from dnsmasq and the silences from dnsmasq :) Any help? On Mon, Dec 9, 2013, at

Re: [Dnsmasq-discuss] address=/#/192.168.0.1 - does not work!

2013-12-09 Thread Albert ARIBAUD
Le 09/12/2013 11:50, Nikita N. a écrit : Hi Albert :) what I wrote you is what in fact I *see* from Wireshark. I see all traffic there, I see exactly when and where appears the frame into at0, the DHCP and DNS request frames from me, the correct answers from dnsmasq and the silences from dnsmasq

Re: [Dnsmasq-discuss] address=/#/192.168.0.1 - does not work!

2013-12-09 Thread Nikita N.
Hi Albert :) I see you want a complete log/trace session for your debugging, isnt it? :) Well I didnt think to prepare that, I was thinking you could give me some more easy answer.. First of all I would like to know, is my config file correct? With such config file, am I supposed to get what I

Re: [Dnsmasq-discuss] address=/#/192.168.0.1 - does not work!

2013-12-09 Thread Albert ARIBAUD
Le 09/12/2013 12:26, Nikita N. a écrit : Hi Albert :) I see you want a complete log/trace session for your debugging, isnt it? :) *My* debugging? No. I don't intend to debu your issue, only have a look at it and see if, as a user of dnsmasq to another, I can help *you* debugging. :) Also,

Re: [Dnsmasq-discuss] address=/#/192.168.0.1 - does not work!

2013-12-09 Thread Nikita N.
OH my god! :)) I see now you are not the author of dnsmasq.. I see the author id Simon Kelley.. apologies, I thought I was talking with the author :) Of course you dont have to debug that issue! :D No, really, im pretty sure of what I saw in wireshark traces, even because I spent few hours in

Re: [Dnsmasq-discuss] address=/#/192.168.0.1 - does not work!

2013-12-09 Thread Albert ARIBAUD
Le 09/12/2013 13:41, Nikita N. a écrit : OH my god! :)) I see now you are not the author of dnsmasq.. I see the author id Simon Kelley.. apologies, I thought I was talking with the author :) Never mind. :) Of course you dont have to debug that issue! :D No, really, im pretty sure of what I

Re: [Dnsmasq-discuss] address=/#/192.168.0.1 - does not work!

2013-12-09 Thread Nikita N.
On Mon, Dec 9, 2013, at 04:59 AM, Albert ARIBAUD wrote: Mostly the DNS feature half-hour-delayed disappointed me enough.. So my question is directed to the author of dnsmasq - I still dont know, can I use dnsmasq for my needs? or im just wasting time? Thanks :) AFAICT, yes, you should

Re: [Dnsmasq-discuss] address=/#/192.168.0.1 - does not work!

2013-12-09 Thread Simon Kelley
On 09/12/13 08:29, Nikita N. wrote: Hi All, its the first time for me on this maillist :) Im trying some tests with dnsmasq, but I cant make it work.. sorry :( I dont know if its a bug.. or its just me missing something.. So here what I want to do: I created a tap ethernet interface (on

Re: [Dnsmasq-discuss] address=/#/192.168.0.1 - does not work!

2013-12-09 Thread Nikita N.
Yes, it did the trick, worked at first shot :) Still remains that silence after DHCP requests without previous discover.. really unpleasant.. Probably its not 100% protocol compliant, but I see also from dhcpd, its common behaviour to accept DHCP requests from returning clients.. Maybe implement a

Re: [Dnsmasq-discuss] address=/#/192.168.0.1 - does not work!

2013-12-09 Thread Nikita N.
Sorry sorry, it works it works :) I was looking at an old trace, apologies.. Going to trash dhcpd and that dirty disgusting wtf dnsspoof.. ;) Thanks and keep on the good work! :D On Mon, Dec 9, 2013, at 03:01 PM, Nikita N. wrote: Yes, it did the trick, worked at first shot :) Still remains that