Well, I noticed some dnsmasq-dhcp strangeness going on with a couple of computers (Windows 7). Every two minutes or so, from every Win7 computer I would get:
I did some research, and figured out how to stop it. If you add dhcp-option=252,”\n” to the dnsmasq options, it will not show up in the log anymore.
I have no idea what it does or why it works, I am still very new to this. I just found one article from a network admin who had to add it because his logs were becoming difficult to read.
Just putting this on here if anyone else has this issue, or if someone can explain why it works LOL...
These just show up in my builds, as I have enabled logoutput from dnsmasq. BrainSlayer builds don't output anything from dnsmasq, which makes it hard to spot issues like these.
I think we should make dhcp-option=252 a default value. If this option is not set win clients will continuously query the dns server on the router for proxy auto config settings.
Joined: 14 Dec 2015 Posts: 774 Location: 127.0.0.1
Posted: Sun Jan 03, 2016 22:19 Post subject:
<Kong> wrote:
ATHF wrote:
Well, I noticed some dnsmasq-dhcp strangeness going on with a couple of computers (Windows 7). Every two minutes or so, from every Win7 computer I would get:
I did some research, and figured out how to stop it. If you add dhcp-option=252,”\n” to the dnsmasq options, it will not show up in the log anymore.
I have no idea what it does or why it works, I am still very new to this. I just found one article from a network admin who had to add it because his logs were becoming difficult to read.
Just putting this on here if anyone else has this issue, or if someone can explain why it works LOL...
These just show up in my builds, as I have enabled logoutput from dnsmasq. BrainSlayer builds don't output anything from dnsmasq, which makes it hard to spot issues like these.
I think we should make dhcp-option=252 a default value. If this option is not set win clients will continuously query the dns server on the router for proxy auto config settings.
Kong, thank you for the explanation, personally I like it if there is a little more information than not enough. _________________ Tutorial for flashing WRT series WRT Installation,Upgrade & Basic Setup–Cliff Notes
r52242: WRT3200ACM, WRT1200ACv1 & 1 Velop in bridge mode(IoT subnet), r52242 WRT1900ACv1 AP
Velop:2 WHW0101, RE6500, RE9000(AP)
Spectrum - 1000/50
SysLog Watcher 5, New security Onion box coming soon, Fingboxes, PiHoles, NEMS, Cacti, rpisurv
Joined: 13 Jun 2006 Posts: 1608 Location: SE Michigan USA
Posted: Mon Jan 04, 2016 22:07 Post subject:
[quote="<Kong>"
These just show up in my builds, as I have enabled logoutput from dnsmasq. BrainSlayer builds don't output anything from dnsmasq, which makes it hard to spot issues like these.
I think we should make dhcp-option=252 a default value. If this option is not set win clients will continuously query the dns server on the router for proxy auto config settings.[/quote]
I vote for making dhcp-option=252 a default value. Not sure why I care that a Windows box is querying proxy settings which in most cases do not exist.
Posted: Tue Jan 05, 2016 0:48 Post subject: anyone having issue with ddns ?
hello
i have the latest kong on my v1 WRT1900AC and i have ddns configured with the right ports to rdp to my home pc from outside the home network ! however this works when im on the linksys firmware and does not work when im on ddwrt ! when i ping my ddns from inside my lan at home i get reply but when i do from outside i get times out ! is there any feature on ddwrt that blocks external access through ddwrt?
Joined: 14 Dec 2015 Posts: 774 Location: 127.0.0.1
Posted: Tue Jan 05, 2016 4:34 Post subject: Re: anyone having issue with ddns ?
frankmontreal wrote:
hello
i have the latest kong on my v1 WRT1900AC and i have ddns configured with the right ports to rdp to my home pc from outside the home network ! however this works when im on the linksys firmware and does not work when im on ddwrt ! when i ping my ddns from inside my lan at home i get reply but when i do from outside i get times out ! is there any feature on ddwrt that blocks external access through ddwrt?
I don't use DDNS but, under security if you have, Block Anonymous WAN Requests (ping) checked that would make the router not answer the ping from outside your network. Sorry I couldn't be more help. _________________ Tutorial for flashing WRT series WRT Installation,Upgrade & Basic Setup–Cliff Notes
r52242: WRT3200ACM, WRT1200ACv1 & 1 Velop in bridge mode(IoT subnet), r52242 WRT1900ACv1 AP
Velop:2 WHW0101, RE6500, RE9000(AP)
Spectrum - 1000/50
SysLog Watcher 5, New security Onion box coming soon, Fingboxes, PiHoles, NEMS, Cacti, rpisurv
Posted: Wed Jan 06, 2016 14:06 Post subject: Reading change logs on TRAC
Sorry for the noob ? but I would like to understand (or at least read ) what is in the 1/2/16 changes below. I followed the TRAC link and I see a changeset 28647 by BS but it only lists madwifi for the 4.4 kernel. I have assumed 610-613, etc. are ticket #s but that must not be true since they are in the 3000-6000 range. How do I find what was fixed for USB, FTP, etc.? I'm currently still on the 12/24 build for my WRT1900AC router which has been stable and I want to upgrade only when it makes sense.
Posted: Wed Jan 06, 2016 15:00 Post subject: Port based VLAN support?
I was going through the http://svn.dd-wrt.com/timeline and did a search to see if port based VLAN is being supported I more recent builds, but, I couldn't find any indication that it is.
If not supported, any indication when it might be?
Also, even if support is not in the GUI, does anyone know if I can do port based VLAN by entering command in Administration -> Commands -> 'Startup'?
looks like a wiki needs to be uploaded to inform people how to flash and work dd-wrt on this router. i was actually working on one but then i thought something like this would not happen.
if anyone else wants to work on the wiki, your welcome to beat me to it.
Posted: Thu Jan 07, 2016 15:38 Post subject: Re: Port based VLAN support?
growler13 wrote:
I was going through the http://svn.dd-wrt.com/timeline and did a search to see if port based VLAN is being supported I more recent builds, but, I couldn't find any indication that it is.
If not supported, any indication when it might be?
Also, even if support is not in the GUI, does anyone know if I can do port based VLAN by entering command in Administration -> Commands -> 'Startup'?
) what is in the 1/2/16 changes below. I followed the TRAC link and I see a changeset 28647 by BS but it only lists madwifi for the 4.4 kernel. I have assumed 610-613, etc. are ticket #s but that must not be true since they are in the 3000-6000 range. How do I find what was fixed for USB, FTP, etc.? I'm currently still on the 12/24 build for my WRT1900AC router which has been stable and I want to upgrade only when it makes sense.