378.56_2, RT-N66U

[JJ Duru]

Hi all,

I am trying to convince my router to function in Access Point mode but for some reason it is not forwarding the wifi/wired DHCP requests to the main router (a pfsense router). The pfsense hosted DHCP worked and works flawlessly but when I connect my macbook pro to the asus and wait for it to get an IP address from pfsense, it waits and waits and ends up with a "self-assigned" IP address.

The odd thing is, rt-n66u worked fine in Access Point mode up until I decided it's time for a reset due some slow wifi connectivity. Since then, I reset it to defaults multiple times, to no avail.

Any help is appreciated. Thank you.

Update 1: I forgot to mention that I tried both dynamic IP and static IP for the AP, with the correct values for IP, subnet, gateway. The moment I click apply button my mbp connection goes dark. Even if I try to use a manual IP on my laptop, I'm not able to reach the pfsense.

 

[JJ Duru]

Nvm, found the issue. Nothing wrong with the RT-N66U.

 

[joegreat]

Nvm, found the issue. Nothing wrong with the RT-N66U.

Great, but what was the issue and what was (even more important) the solution???

 

[JJ Duru]

Great, but what was the issue and what was (even more important) the solution???

Nothing related to RT-N66U.

I forgot to mention in my original post that the gateway is a virtualized pfsense on esxi. I started from the assumption that the pfsense was running fine. After losing a whole afternoon trying to make the RT-N66U (AP mode) to communicate with the gateway, I had to get a windows laptop with a vsphere client and start verifying the actual ESXi config - host, vm, nic, virtual nics, virtual switches. Just to discover that on the LAN NIC the "connect at power on" option was unchecked. And I remember now why it possibly got unchecked - because I tried to use the technical preview of the ESXi Embedded Host client instead of the vsphere client. That's why is called technical preview - to take it with a grain of salt - lesson learned.