Gargoyle 1.5.9 not working in Client+AP mode for TL-WR1043ND

[jbitbyte]

Hi there.
I've been using Gargoyle 1.4.7 since some months ago and I was very happy with it. Yesterday I decided to upgrade to 1.5.x version to take advantage of USB printer network sharing.
So...I reset the configuration, then I upgraded to 1.5.9 and then I configured new firmware to fit my networking needs. Here is my configuration:
[*]I have main router in another room connected to internet (192.168.19.x, 255.255.255.0)
[*]I use TL-WR1043ND secondary router to connect wirelessly to main router (Device Configuration=gateway). This secondary router has Gargoyle firm installed. I've set another subnet for secondary router (192.168.20.x, 255.255.255.0).
[*]I also use this secondary router to repeat signal ("Client+AP" mode)

When I was using firm 1.4.7 everything was working fine. After upgrading to 1.5.9, same configuration does not work anymore. Now, when I ping to main router (192.168.19.1) from secondary network (192.168.20.x), then I get a message that remote host is not reacheable.
I observed that if I just change "Wireless Mode" to "Client" (instead of "Client+AP"), then I can see immediately ping to 192.168.19.1 working fine. If I revert back to "Client+AP" mode, then ping stops working again.

It looks like there is a bug in firm 1.5.9 for "Client+AP" mode.

Anyone can help?

Thanks in advance.

[Takenover83]

1.5.9 Client+AP mode for TL-WR1043ND worked fine for me but wireless was buggy. 1.5.6 is much more stable. Give it a wirl.

[jbitbyte]

I'm afraid that I bricked my TL-WR1043ND device by upgrading/downgrading firmware versions.
I ordered an USB-UART cable to try unbricking it.
I will update status as soon as I will be able to unbrick my router.

[TCattd]

1.5.9 Client+AP mode for TL-WR1043ND worked fine for me but wireless was buggy. 1.5.6 is much more stable. Give it a wirl.

Thanks for the tip.
Downgraded from 1.5.9 to 1.5.6 and yes, wifi is more stable.