[otkaz]

My EA6400 has been running fine for years with the same config until I flashed r48141 2 days ago. It's running as a AP in my office. No services being utilized on it not even DHCP or firewall. Just works as a wireless access point and switch. After flashing I notice my phone would no longer connect to it just fail with a auth error. Turned logging on but nothing shows in log. Flashed back to r45000 which was a know working build and the problem is still there. did a 30-30-30 reset. Wifi devices will connect until I turn off DHCP and connect it back to the rest of my network. Strange thing is at that point if I turn DHCP back off and disconnect from my other device running DHCP wifi wont go back to working until I do another rest. Tried flashing r42278 with same issues and now just flashed r48218 and same same. Wifi on the router can scan and see other devices with both wl0 and wl1. Anyone have some trouble shooting steps I could try? I spent the whole day yesterday flashing and resting and I'm at a total loss.

[kernel-panic69]

The only thing that changed is likely the vlans and assign WAN port to switch being removed; Otherwise, the Wireless Access Point Wiki procedure should still work. I presume by 30-30-30, you mean 'nvram erase && reboot' since you do not do a 30-30-30 on Broadcom ARM devices.

[otkaz]

I'm currently on DD-WRT v3.0-r48218 (01/28/22) Linux 4.4.300 #5085 SMP Thu Jan 27 19:03:20 +07 2022 armv7l.
I went to commands on the admin tab and sent 'nvram erase', then 'reboot'. Plugged my desktop into LAN port 2. Changed the default login/password when it came up. Went to the setup tab and set WAN to disabled. Changed my local IP to 192.168.0.4. Set gateway and DNS to 192.168.0.1. Disabled DHCP hit apply and plugged my gateway(mikrotik router) into port 1. Left everything else where it was with a open network and I still can not connect to the network over wifi. My phone, laptop, and 3d printer will not connect. They just try over and over again.

[kernel-panic69]

Here, let me reiterate:

[otkaz]

What part of my post above differed from what's on the wiki you pointed me too?

[kernel-panic69]

You mean other than trying to shortcut the process that works? The "simple version" does not work AFAIK. Just to reiterate again, regardless of the wiki:

Setup -> Basic Setup

• WAN Connection Type: Disabled
  
• Local IP Address in same subnet as upstream router
  
• Subnet Mask (24 since it is now CIDR)
  
• Gateway set to IP of upstream router (no need for DNS entry)
  
• Enable NTP client, leave server field blank
  
• Save

Setup -> Advanced Routing

• Router mode
  
• Save

Wireless -> Basic Settings

• SSID
  
• Sensitivity Range (I personally use 1350)
  
• Save

Wireless -> Wireless Security

• WPA2
  
• CCMP-128(AES)
  
• Password
  
• Save

Services -> Services

• Disable DNSMASQ and all associated settings
  
• Disable ttraff
  
• Enable SSH/Disable Telnet
  
• Enable syslogd/klogd
  
• Save

Security -> Firewall

• Disable SPI Firewall, Save
  
• Check Filter Multicast, Save (the check may "disappear")

Administration -> Management

• Apply settings
  
• If apply doesn't work and you have nothing after a few minutes, REBOOT.

Also refer to basic and advanced wireless wikis. You will not want to use auto channel on wireless.

[otkaz]

I was short cutting the process to keep it simple. Its still not connecting even after following all of those instructions step by step. Is there anyway to log wifi connections so I can see why they fail?

[otkaz]

I get that "it should work" but it's not and I'm looking for some more advanced trouble shooting steps. I've used ddwrt for years and run many different routers with it. I've never had an issue like this before. I've spent 2 days now fiddling with this and have gotten no where. It really doesn't make any sense.

[egc]

Do you use a different SSID and different channel from your main router?

WPA2 personal CCMP-128 AES for security?

[kernel-panic69]

If your client devices were on previous wifi setup, you may have to "forget network" and connect fresh. Outside of that, I see no reasons for it not to work in recent / current build(s) outside of a bad config.

[otkaz]

[kernel-panic69]

The only other piece of this puzzle to look at is your MicroTik router and it's configuration(s). I don't see any commits in the past 10-20 days that would break this mode; at least nothing blatantly obvious.

[otkaz]

It works fine until I turn off DHCP which at that point it has to get an IP from a DHCP server connected to a LAN port. Other devices connected by LAN work fine. Could it somehow not be bridging the wifi clients to LAN?

[otkaz]

[kernel-panic69]

Please focus on using a single wired client to config the router and configure it completely *first*, *then* test it. If you have wireless clients connected to it while configuring, you are likely shooting yourself in the foot. It sounds as if your wireless clients are not releasing their old IP address or something to that effect, or we do not have the full picture here. The wireless interfaces should be in the bridging table if you did not change them from default to unbridged, which shouldn't be touched anyway.