![]() With yours, there may be other ways, but You can reset it too like that and get out of bridge mode and to a web interface. With those, you have to reset it(holding the reset pin) to get to the web interface and that takes it out of bridge mode. ![]() The few i've used, when in bridge mode, have no web interface or IP. However, if you need to get this working, and you have the money, this is the first thing I'd try.How do I access my modem's GUI when it's in bridged mode? However I'm hesitant to tell you to go out and buy another router when I'm not 100% certain that this is the cause of your problem. If this is the case a router like the ASUS WL500GP would be the answer, since it has 32MB of memory, which should be plenty. It sounds like you may be pushing it past this limit. The WRT54GL has only 16MB of RAM, which is just BARELY enough to run Gargoyle. My suspicion is the combination of the PPPoE daemon and the memory getting eaten up by all those clients is making the PPPoE daemon die due to lack of RAM, and killing your internet connection. PPPoE requires a utility to be running on top of everything else, which requires extra memory. It isn't the number of quota rules exactly, but you say you have 7-8 of them, which suggests you may have 7-8 clients connecting at the same time. I've seen this happen, and it's client-dependent - not really anything to do with the router.ģ) My best guess about what's going on (though I'm far from certain) is that you're running out of memory. This is probably because your client machine isn't reconnecting after the wireless goes down and comes back up (all network interfaces get restarted after you change network settings in connection/basic). I'm just mentioning it first to make sure of this.Ģ) You say that when you connect from a wireless client the wait screen is displayed forever. but it sounds like you're doing that properly, since it works initially. Debugging PPPoE issues is also especially tricky for me, since I don't have a DSL connection to play with.ġ) My first comment when PPPoE issues arise is usually to make sure modem is in bridge mode and you're connecting via PPPoE in the router. I'm not sure what's going on, but I can make a few comments /suggestions. ![]() I can't tell if the problem appears only when configuration is changed from wireless client or when there are 7-8 quota rules taking more memory or processor time or something totally different. I loaded stable firmware to the router and in the beginning it worked also, but after after several configuration changes I was in the same situation. I tried to reconfigure from wired client, but wait screens after every apply stayed forever and I couldn't make it work. After several reboots, I got pppoe connection but no Internet access to clients. After a while I logged in again, but there was no pppoe connection. ![]() I rebooted the router but wait screen again stayed forever. Router had WAN connection and could ping it's peer successfully, but the clients could ping only router's WAN address, not it's pppoe peer. I logged in again and saw that settings were applied, but clients had no access to Internet. I tried to fine-tune quotas and wireless mac filter from remote wireless location but after applying settings, wait screen stayed forever. I configured Gargoyle from wired connection and in the beginning everything was OK. I tried Gargoyle with both stable 1.0.14 and experimental 1.1.12 on WRT54GL and I had similar problems with both versions. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |