But why is the DD-WRT device interfering with DHCP and DNS at all? I use my devices only as access points. There is a seperate router which does the rest (DHCP, DNS, ISP dialup, routing...). So my idea was and is that the DD-WRT devices just provide wifi for my clients and pass everything through, also DNS and DHCP requests.
I just noticed another options right under the two options mentioned above: DHCP-Authoritative
What does this do? The help page does not mention it. The DHCP server is turned off on the DD-WRT devices.
DNSMasq is enabled at the moment in the services options.
Can I turn everything off which doctors the traffic sent through the device? Especially stuff like we are talking about at the moment.
But why is the DD-WRT device interfering with DHCP and DNS at all? I use my devices only as access points.....
Using as wireless access point (WAP)
Best configuration practice would be:
Setup/Basic Setup Connection type should be diabled.
Gateway set to whatever IP has the WAN connection within its subnet.
DHCP Server should be disabled w/everything under that unchecked.
Setup/Advanced Routing operating mode should be 'Router' w/interface LAN & WLAN
Services/Services DNSMasq should be disabled unless you want to run a guest network
from your WAP and only then have it enabled with everything else unchecked --- you would
use it's 'Additional DNSMasq Options' section for input of separate DHCP for guests network.
But why is the DD-WRT device interfering with DHCP and DNS at all? I use my devices only as access points.....
mrjcd wrote:
Using as wireless access point (WAP)
Best configuration practice would be:
Setup/Basic Setup Connection type should be diabled.
Gateway set to whatever IP has the WAN connection within its subnet.
DHCP Server should be disabled w/everything under that unchecked.
Setup/Advanced Routing operating mode should be 'Router' w/interface LAN & WLAN
Services/Services DNSMasq should be disabled unless you want to run a guest network
from your WAP and only then have it enabled with everything else unchecked --- you would
use it's 'Additional DNSMasq Options' section for input of separate DHCP for guests network.
Thank you! I had to disable the DNSMasq Options on General, the Router options on Advanced Routing and I turned off DNSMasq completly.
I use the DD-WRT devices as APs only. Well, I run two networks, the "normal" network and a network for guests. I put the ath0.1 and ath1.1 in a seperate VLAN and let everything else handled by the router (Fritzbox) as well as the other stuff mentioned above.
So what do you think, will my problems with the wifi login/auth also be gone by these new settings?
Posted: Thu Nov 26, 2015 16:09 Post subject: Thank You for cleaning this up....
Thanks again---I Shadow-watch this forum & am interested in the updates (running a Netgear 4300 w/current beta) & like reading the facts...not flame-wars. Really thank everyone involved with DD-WRT that keeps the updates coming.
and thanks for the hint. Will this solve both problems or just the DNS issue or also for the other problem? I'm asking because I see two options and one is mentioning DHCP as well:
Use DNSMasq for DHCP
Use DNSMasq for DNS
What is the function of those options? For the second I would say that the device is somehow doctoring with the DNS data sent through the device. The first? Is this some kind of DHCP relay server?
Both is turned on at the moment.
If I'm right and if I disable both is everything, also DHCP from the router device (which is not one of my two DD-WRT devices as mentioned before)?
If you're using it as an AP, dhcp type should be dhcp disabled, and these dnsmasq options should be grayed out, whether they're checked or not. It sounds like you're still set to dhcp server.
Posted: Thu Nov 26, 2015 18:26 Post subject: Re: New build: DD-WRT v3.0 --- 28320 --- 2015/11/25
KrypteX wrote:
The original new build thread is full of insults, therefore I created another one, quoting all actual reports that are relevant.
I apologize for the format, but I can't do better than that.
Which is totally unnecessary and shows what a big baby you are, because you can't handle things that you said antecedently. Are all the DD-WRT sheep now supposed to follow you to whichever thread you deem as "lawful" to post in, under your rule? I never knew you had some official title on the DD-WRT project rather than being unhelpful on the forum (I remember when you and tatsuya46 got into a fight and there were pages of flames from you) and filing bug reports. You obviously are not a real asset to this project; it seems to me like you are actually here to pose as helpful but have an ulterior motive to actually bring the project down.
I have caught on to your bullshit and so will other people; don't think that just because you are behind a computer screen that you can do whatever you want on this forum. Because you can't.
Last edited by pirithous on Thu Nov 26, 2015 19:03; edited 1 time in total
Router Model: TL-WDR3600
Status: Bad
Reset: No
Errors: Bricked device
Router Model: DIR-615/E3
Kernel:
Status: OK
Reset: No
Errors: Yes
Working on tftp recovery at the moment on the WDR3600; hoping I can recover it. All the lights on the front are blinking and it's completely inaccessible. This is extremely poor planning for the DD-WRT project and not acceptable. The DIR-615/E3 had to be completely reset just to get into the router GUI, I had to move that router in place of the WDR3600 or else nobody here will have an internet connection.
BrainSlayer wrote:
about your wdr problem. like all tplink devices its almost impossible to recover them without a serial console. this is a design problem by the manufacturer. they dont offer any recover method. (except for some newer device, but i havent seen it in real world right now, i count it just as a rumour
Here is some info I found on recovery for TP-Link Archer C7 V2, one of their newer devices.
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Fri Nov 27, 2015 10:52 Post subject:
@pirithous:
you did not seem to get the warning in my last post. now i take the consequences and will disable your account _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
<3>[83322.800000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42100020 DMADBG_7=0x000084c0
That error apparently didn't cause much of a problem.
I did lose the station but twas not a dd-wrt error --- I had to drive my happyass across
town in 32º F cold before daylight to see that part of town is without power ... oh well, cold they are
root@160NL-WDS-South:~# uptime
11:50:37 up 3 days, 4:56, load average: 0.00, 0.01, 0.04
root@160NL-WDS-South:~# dmesg | tail
<3>[272689.350000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42100020 DMADBG_7=0x000286c0
<3>[272864.260000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42100020 DMADBG_7=0x000084c0
<3>[272900.440000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42100020 DMADBG_7=0x000084c0
<3>[273097.040000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42100020 DMADBG_7=0x000286c0
<3>[273373.870000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42100020 DMADBG_7=0x000084c0
<3>[273831.220000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42100020 DMADBG_7=0x000084c0
<3>[274245.230000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42100020 DMADBG_7=0x000042c0
<3>[274409.610000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42100020 DMADBG_7=0x000084c0
<3>[274550.050000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42100020 DMADBG_7=0x000084c0
<3>[274879.890000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42100020 DMADBG_7=0x000084c0
----
WDS-Station ¬
root@160NL-WDS-North:~# uptime
11:49:00 up 3 days, 1:50, load average: 0.00, 0.02, 0.04
root@160NL-WDS-North:~# dmesg | tail
<6>[ 4514.520000] ath0: send auth to 00:25:9c:c0:6a:cd (try 1/3)
<6>[ 4514.530000] ath0: authenticated
<6>[ 4514.540000] ath0: associate with 00:25:9c:c0:6a:cd (try 1/3)
<6>[ 4514.540000] ath0: RX AssocResp from 00:25:9c:c0:6a:cd (capab=0x411 status=0 aid=1)
<6>[ 4514.550000] ath0: associated
<6>[ 4515.570000] br0: port 3(ath0) entered forwarding state
<6>[ 4515.570000] br0: port 3(ath0) entered forwarding state
<6>[ 4517.570000] br0: port 3(ath0) entered forwarding state
<3>[ 4691.540000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42100020 DMADBG_7=0x000286c0
<3>[15145.670000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42100020 DMADBG_7=0x000084c0
----
WAP + guests ¬
root@WRT16NL-AP:~# uptime
12:05:04 up 3 days, 3:13, load average: 0.00, 0.01, 0.04
root@WRT16NL-AP:~# dmesg | tail
<6>[ 15.040000] device ath0.1 entered promiscuous mode
<6>[ 15.060000] br1: port 1(ath0.1) entered listening state
<6>[ 15.060000] br1: port 1(ath0.1) entered listening state
<6>[ 15.780000] device br0 left promiscuous mode
<6>[ 17.030000] br0: port 3(ath0) entered forwarding state
<6>[ 17.060000] br1: port 1(ath0.1) entered learning state
<6>[ 19.060000] br1: topology change detected, propagating
<6>[ 19.060000] br1: port 1(ath0.1) entered forwarding state
<6>[ 206.310000] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
<3>[ 3030.050000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42100020 DMADBG_7=0x000084c0
root@WRT16NL-AP:~# exit
Connection closed by foreign host.
