Gargoyle 1.5.1 is not working in Client+AP mode

[ofbizbrazil]

Sorry dude (Eric), but I´m just trying to fix my router up and when a bum comes here and messes up all my job about explaining configurations that I made with commands and screenshoots, it´s not my fault if I lost my temper... do you know wanna mean?

I hope you can help me with this topic!!

Thanks....

[frank604]

Hijacking a thread is wrong (unethical).
Being overly aggressive on a community forum for people to help each other is wrong.

Cheer up OP. I believe DoesItMatter is working on a solution of command lines for you as per his last post. Perhaps he will find one for you. Otherwise, if no other solutions appear, I recommend changing firmware ver to one that worked or to another set of firmware. But I truly hope there's a solution for you.

Cheers!

[ofbizbrazil]

Awesome, that sounds really good...

I look forward to seeing these scripts, I would really thank @DoesItMatter for this ruge help!!!

@DoesItMatter let me know if you could get success on it!!

Regards!!

[DoesItMatter]

Awesome, that sounds really good...

I look forward to seeing these scripts, I would really thank @DoesItMatter for this ruge help!!!

@DoesItMatter let me know if you could get success on it!!

Regards!!

Sorry, busy week, I will have time on Friday night to try this out.

[DoesItMatter]

OK - Verified - Client+AP mode is working correctly

I am using 1.4.4, but from what I understand, no difference from
1.4.4 and 1.5.1 if you only have a single band 2.4ghz radio router
and that TOR is missing from 1.4.4

-------------------------

Config screens shown below

The one thing I did find I had to enable was under Internet/WAN

Wan Ethernet Port: set to "Bridge to LAN"

IF I left Wan Ethernet Port disabled, Client+AP would not work for me.

I WAS able to have different password keys for the Client
and the Access point setups, and also used different IP ranges.

Internet is working no problem - this post is actually being done
from the Client + AP config - I am connected Wirelessly to
the Gargoyle router - main router = Asus RT-N16

Recommend reset to defaults before trying to configure this.

This is configured on my DIR-601 router.

Client+AP Mode not working = Myth Busted!!!

[ofbizbrazil]

Wow, it looks an awesome job... with these amazing screenshots explaining step by step how to config.

I´ll try again to reconfigure my router using this model and see what happens now...

I keep you posted, thanks a lot for your help!!!

Regards,

[ofbizbrazil]

Hi DoesItMatter,

So, it seems a freaking problem with Gargoyle and TPLink wr1043ND version 1.6, as you can see in attachments I did all configurations that you showed me before.

When I set as Client mode I received from Ana´s router IP in the range 192.168.0.X, but when I set as ClientAP mode nothing comes more in this case using a IP range (192.168.1.X).

I detected on Ana´s router (Dlink 524) that Gargoyle couln´t really connect, DHCP list doesn´t show my TPLink as station more in use. Otherwise Client mode does it.

So I guess this Myth wasn´t really Busted !!!

Let me know what you think.

Thanks

[DoesItMatter]

You are missing one key point.

Wireless-N spec HAS to use WPA2-PSK

If you choose WPA-PSK and Wireless-N - you will never get
a working connection.

IF you set it to G+B and WPA-PSK - I bet you get a connection

If you want to use Wireless-N though - WPA2-PSK is only option.

[ofbizbrazil]

Hi DoesItMatter,

Good shot but not enough... I really tried many combinations and by chance last screenshot wast to use WPA PSK.

I set up as You told me, but I noticed one diffence now I can see my Wireless SID on air I mean Gargoyle Wireless, when I was using WPA PSK not even it happened.

But problem carries on, DHCP Ana´s router doesn´t receive TPLink connected.

Any other shot? Find enclosed my last configuration.

[DoesItMatter]

Before you try Client + AP, go ahead and just try Client mode

Set it up like a Wireless Bridge.

If you can get that to work, Client + AP should work.

If you cannot even just get the router connected via Client,
they are possibly incompatible, or there are some odd settings
somewhere, in which case, you should reset both routers to default,
re-configure from scratch, and try Client connect first,
then Client + AP.