Page 1 of 2

AP mode (wan wired) problem

Posted: Wed Sep 16, 2009 3:12 pm
by reginaldo10
Hi everybody!!
when I set up gargoyle in dir-300 with wan port(wired not wireless),
like AP mode. I can´t connect to the router through lan ports.
only by the wireless connection.
I have to set up back to AP/client or repeater brigde to connect with lan ports again.
Thanks.

Re: AP mode (wan wired) problem

Posted: Fri Sep 18, 2009 2:17 pm
by reginaldo10
still does not work the AP mode(WAN wired)...

Re: AP mode (wan wired) problem

Posted: Sat Sep 19, 2009 10:40 am
by Eric
That does sound like a very serious problem. However, it is (unfortunately) likely to be somewhat difficult to debug, because it sounds like a driver issue. So while I understand that this is a serious issue, I can't provide an immediate fix (as much as I'd like to do so).

Also, I don't even own a a DIR-300, just an Airlink AR430W which is very similar but not quite the same. Last time I checked on that router this problem wasn't there, though that was with an older version of Gargoyle, based on an older version of OpenWrt.

So.. I'll see what I can do, but for the immediate future your best bet might be to install a different alternate firmware like dd-wrt.

Re: AP mode (wan wired) problem

Posted: Sat Sep 19, 2009 11:54 am
by DoesItMatter
Yea, the Airlink AR-430W and DIR-300 - REV A are almost identical.

Do not install Gargoyle on a DIR-300 REV B! :shock:

Those have a RaLink chipset and currently Gargoyle supports:

Broadcom
Atheros

Maybe sometime in the future RaLink?

Re: AP mode (wan wired) problem

Posted: Sun Sep 20, 2009 8:49 am
by reginaldo10
Hi Eric!
Can you send me the old firmware version of gargoyle that functioned in your AR430W?
I´ll test it in my DIR-300.
Thank you!

Re: AP mode (wan wired) problem

Posted: Sat Oct 03, 2009 12:59 am
by Statik
OK, it looks like I may have the same problem.

If I connect to the AR430W wirelessly, I get the proper IP address, 192.168.2.x for the wireless. If I connect my cable modem to the WAN connection, the WAN settings appear to come up correctly (using DHCP wired).
However, if I then connect a PC to LAN port 1 (closest to the WAN), it gets an IP from my ISP, not from the router. It appears that the WAN and LAN are connected! No NAT or VLan here!

My settings are all the basic ones:
Configure Device as: Gateway

Internet/WAN:
Connect Via: DHCP(Wired)
Current IP: 24.222.xxx.xxx
Current Lease Expires: 10/03/09 19:48 ADT
Ethernet Port Connects To: WAN
No custom MAC or MTU

Local Network/LAN
Router IP: 192.168.2.1
Subnet Mask: 255.255.255.0
Allow Alternate DNS: Force Clients To Use Router DNS Servers
Custom DNS Servers:

Wireless:
Wireless Mode: Access Point (AP)
Wireless Channel: Auto
Encryption: None
Broadcast SSID: Enabled
Wireless Client Isolation: Disabled

Is this a bug?

Statik

Re: AP mode (wan wired) problem

Posted: Sat Oct 03, 2009 1:08 am
by Statik
Forgot to add:

Gargoyle version 1.0.12
Router: Airlink101 AR430W

Plugging a PC into the router in any port, WAN, LAN1-4, causes the router web GUI to stop responding (connected wirelessly). Unplug the LAN cable and web GUI finishes loading, and/or begins to respond.

Something weird going on here.

Statik

Edit: same result with 1.0.11

Re: AP mode (wan wired) problem

Posted: Sat Oct 03, 2009 8:00 am
by DoesItMatter
Do you know if your router has redboot?

Does DD-WRT work properly on it?

Reason I ask is the DIR-300 was very similar to AR430W, but the
DIR-300 has 2 revisions, and in revision B, they changed from
Atheros chipset to RaLink chipset.

The Airlinks didn't have any safety on it as far as opening it.
I think there was just 4 crosspoint screws on the bottom.

Try and crack it open and verify its still an Atheros chipset.

Re: AP mode (wan wired) problem

Posted: Sat Oct 03, 2009 9:04 am
by Statik
Nope, still has an Atheros Chip
AR2318-ACIA

http://www.statikonline.com/Slides/AR43 ... -Large.JPG

Re: AP mode (wan wired) problem

Posted: Sat Oct 03, 2009 10:40 am
by DoesItMatter
Sweet! - thanks for the Pic!

I sent one of the AR430W's to Eric, so whenever he's got some time,
He'll probably be trying to install Gargoyle to it and can figure
out what is going on... which may take a while!

It may be the switch part inside isn't fully supported by
the OpenWRT drivers.