I also have the IMQ error with this build.
Entering a value of 2 is accepted, but enabling "Restrict unlisted machines" locks all users in my "static DHCP list" out of the internet.
I currently have Static ARP enabled, and things are working well, but cannot apply restrictions.

You don't need to disable it, it's the default anyway. Just ignore it. IMQ is used in the bandwidth limiter.

***NOTE***

Due to instability in some source code commits in versions since 7454, I have completely rebuilt and re-issued. Anyone using versions 7454 to 7462 please reflash with the latest version, which is 7465.

Only thing I noticed, same as with Victek's version, is with my WDS setup I have to unplug one of the routers and plug it back in of course to get the two routers talking to each other again. For some reason a warm boot doesn't do it. Power off, power on does. Gotta be some synch thing, or a request to synch thing for the WDS mode.

Only thing I noticed, same as with Victek's version, is with my WDS setup I have to unplug one of the routers and plug it back in of course to get the two routers talking to each other again. For some reason a warm boot doesn't do it. Power off, power on does. Gotta be some synch thing, or a request to synch thing for the WDS mode.

Click to expand...

I started noticing sync problems after getting my RT-N16 and never really sorted it out. For a while I had scripts running which would did two things, every router would ping the gateway router and reboot upon loss of several pings. The gateway router upon loss of pings to any remote router would run a script and attempt to reboot all routers, itself last. Doing that, rebooting everything with the gateway last, would usually get all the WDS connections working again. Eventually I tried Teddy Bears advice and just switched to wireless Ethernet bridges. I'd used WDS flawlessly for years with routers of the same generation so didn't give up on it right away.

Well I don't have a pair of E3000s to test it with but would think you'd only need the bridge on one of the channels. Essentially one router becomes a wireless client of another AP and bridges it's wired ports to the LAN of that AP. In my case, my remote routers aren't access points but simply provide wired ports. If you are using both as APs, on the "client" router I think you'll lose whichever channel is used for the bridge. This worked for me but may or may not be what you want.

There have been reports of some people not being able to connect to the internet, it appears related to the dnsmasq resolve file not being created on startup. There was a commit in tomato-RT on 26 March that *may* have been the cause, so I am making a new build 7466 for people to try, with that commit removed.

Builds 7454 to 7462 have been deleted because of these reports of possible instability.

Have 2.4 channel set as access point on both routers. Had 5ghz channel set as wireless ethernet bridge on slave, as access point on master. Connected to both routers, could access slave router. But nothing connected to slave router could get through to the internet. It seems as though the devices connected to the slave router did not know where the gateway is. I double checked all settings, etc. Again it works fine in WDS.

Have 2.4 channel set as access point on both routers. Had 5ghz channel set as wireless ethernet bridge on slave, as access point on master. Connected to both routers, could access slave router. But nothing connected to slave router could get through to the internet. It seems as though the devices connected to the slave router did not know where the gateway is. I double checked all settings, etc. Again it works fine in WDS.

Click to expand...

Let me think about this. I may have taken some things for granted.

So try on the slave router, make sure on the basic network page under LAN make sure you set a static router IP address (unused not in the DHCP pool) on the same subnet as the main router, also same subnet mask as main router (should be 255.255.255.0), set main router IP as both default gateway and static DNS. Also set the security the same as the primary router. You need at least the static IP and security, not sure about subnet mask, default gateway and static DNS but don't think it will hurt.

You may have done all that, just being a bit more explicit and trying not to assume as I seemed to do in my previous post. After you do something like that a number of times it's easy to start taking stuff for granted, sigh... There's other stuff you could set up but nothing I can think of required to get a pulse across the link.

Had all that stuff set. Have it set for WDS. Also made sure "router" and "gateway" were selected correctly.

Click to expand...

Hmm, typo maybe? Can't have it set for both wireless ethernet bridge and WDS. Well, on an E3000 you could, one radio one way, one the other. Anyway, guess you'll post more later when you get time to play.

Hmm, typo maybe? Can't have it set for both wireless ethernet bridge and WDS. Well, on an E3000 you could, one radio one way, one the other. Anyway, guess you'll post more later when you get time to play.

Click to expand...

Had the IP/gateway/dns stuff all set when doing WDS. Have 2.4 set as just AP's on both routers. Doing WDS on the 5 ghz. The IP/Gateway/DNS stuff is not in either field. Its in the basic setup. Only thing router specific in the WDS setup is the MAC address of which router linking to which.

Have network up and running. 2.4 ghz as AP's so wireless clients connect to either of the 2 E3000. Have the 5 ghz now working on WET setup instead of WDS so I've reduced the bit of overhead WDS utilizes. Setting I changed to make it work was to turn off Spanning Tree Protocol.

Problem I was having is the two E3000's would see and talk to each other but I had no internet access through the master router.

SPT off and now it works. Was using Spanning Tree Protocol with the WDS setup.

I verified the "router" and "gateway" settings were correct too. Master at gateway, slave as router.

Great. I didn't even think about spanning tree or routing mode. Don't think I touched anything on the routing tab. Doesn't changing the mode from gateway to router basically turn off NATing? When I select wireless Ethernet bridge the WAN port is disabled anyway so shouldn't be required. As for spanning tree, don't think I have any loops in my network so left that at the default of off on all my devices.

The slave router had no problem finding the master router. So the router set to ethernet bridge was fine. The master router wasn't letting any traffic through on to the web. And unlike the single channel routers in pure bridge mode with the simultaneous dual channel my slave router is still being accessed wirelessly by wireless clients via the 2.4 ghz channel. I've forced certain laptops to the slave by putting wireless filter in the master. The only way a few laptops can connect is via the slave router. Works great. Simple way of shaping which router gets used.

I loaded Victek's 8505 beta build for the E3000. Arp binding on does not block internet access through the master. Since these different builds are sharing so many of the same code I'm not sure what this means.

I loaded Victek's 8505 beta build for the E3000. Arp binding on does not block internet access through the master. Since these different builds are sharing so many of the same code I'm not sure what this means.

Click to expand...

Not necessarily sharing all the same code. This would seem to indicate there are differences in the part of the code. Toastman can comment when he has time.

Yes. Its that they share enough code that it makes it difficult to know exactly what's what on the end user side. Could have been ARP binding all along that was giving me trouble. After awhile I try so many different settings I lose track. And while this is very unscientific, Victek's 8505 build is a bit faster. Pages load quicker, etc.

While I'm sure its a low priority for all of these firmwares it would be nice for a WDS/WET aficionado to hit that part of the code and stream line it. Being on some of the home theater forums I can assure you there is a need for a stable fast 2 router setup for people who have put in home theaters but have no wired connection for all the network devices that have become common place for home theaters. Having a setup with routers talking to each other on 5 ghz meanwhile providing access for laptops, etc., on 2.4 and having devices plugged into the slave will have value.

jsmiddleton4, I get your point. I probably shouldn't have even replied to your last post as I lack the expertise and inside info to really know. As I stated before, hopefully Toastman will shed some like when he as time.

Glad you participate. There are at least two other users in this thread who had similar "can't get to internet" problem. Everything seems fine, just can't get on-line. I'm sure toastman is on top of it. Probably something simple.

The simultaneous dual channel is sweet.

One thing I like about WDS mode that WET mode does not do and that is keep the IP addresses assigned to devices on the slave router listed clearly. With WET you see the IP of the slave router for all its devices, not the IP of the device. Which is the way it works, that is not a bug. In WET bridge mode it is the IP of the slave/bridge that the master router sees. In WDS mode the master router device list shows each device going through the slave to the master separately. Makes it easier to manage static IP's, ARP binding, etc., setup. In WET the master "sees" the slave. In WDS mode the master sees each device.

This and I have to actually do something today. I turned spanning tree protocol back on. Everything works fine. I'm fairly certain is it ARP binding. Not 100% but fairly certain.

I'm not sure what the problem is with ARP Binding, can you explain? Some of the guys have been setting ARP binding with nothing in STATIC - ARP and ticking both boxes, thus cutting everyone off from the internet.

As far as I know it's working cos I use it on the gateways here. I'll check it again later to see if anything odd is happening though. You do need to put all MAC addresses of any devices using the router into the Static DHCP list, or they will be denied access once you check the limit box ...

I'll mention I was looking at the readme.txt file for 1.28.7466 and saw this:

Please note that CPU frequency display will show blank until you set a frequency in Advanced/Misc. The router will
run at it's default frequency if nvram is not set - the RT-N16, for example, sets itsaelf to 480.

Click to expand...

That's not entirely correct, at least not for the E3000. When the router first boots up after being flashed, it will set itself to the default frequency (480 MHz), but if the router is unplugged and plugged back in, then it changes to 133 Mhz (verified in the log), if there is no clock frequency set.

It will stay 133 MHz, until I either do a thorough NVRAM reset (at which point it is 480 MHz again until I unplug and plug in) or I set it to 480 MHz manually.

I'll mention I was looking at the readme.txt file for 1.28.7466 and saw this:

Please note that CPU frequency display will show blank until you set a frequency in Advanced/Misc. The router will
run at it's default frequency if nvram is not set - the RT-N16, for example, sets itsaelf to 480.

Click to expand...

That's not entirely correct, at least not for the E3000. When the router first boots up after being flashed, it will set itself to the default frequency (480 MHz), but if the router is unplugged and plugged back in, then it changes to 133 Mhz (verified in the log), if there is no clock frequency set.

It will stay 133 MHz, until I either do a thorough NVRAM reset (at which point it is 480 MHz again until I unplug and plug in) or I set it to 480 MHz manually.

Click to expand...

Although I realize that is what was reported in the log. I will also note that before and after setting the CPU frequency to 480MHz, telnet/SSHing to the router and doing a "cat /proc/cpuinfo" always showed 239.20 BogoMIPS, so I'm wondering if the CPU was -really- running slower or just reporting that.

Also I'm not sure the dnsmasq resolve file issue is fixed. I see the following in the log at startup about /etc/resolv.dnsmasq not existing, but dnsmasq is killed and reloaded and it exists the next time and things seem okay at that point.

I'll mention I only saw one instance where WAN access was completely disabled under 1.28.7465. I couldn't even ping my modem which wouldn't have been a DNS issue since I was using an ip address.

Although I realize that is what was reported in the log. I will also note that before and after setting the CPU frequency to 480MHz, telnet/SSHing to the router and doing a "cat /proc/cpuinfo" always showed 239.20 BogoMIPS, so I'm wondering if the CPU was -really- running slower or just reporting that.

Click to expand...

In my case right after doing a NVRAM reset, doing a "cat /proc/cpuinfo" did show a 239.20 BogoMIPS value. After unplugging and plugging my E3000 back in, doing the same thing reported around 63. So the router really was running at 133 Mhz.

Perhaps the ISP received DNS servers had not quite been received to create /etc/resolv.dnsmasq, seems like it was there a second later.

Mine seemingly does find /etc/resolv.dnsmasq, reads it, twice, then exits, restarts, reads it again and goes on. I also replaced my ISP provided DNS servers with x.x.x.x, cause, well, I'm paranoid. I left the OpenDNS entries. Having said this, DNS seems to be working fine here, just contributing my observations about the start-up logs.

I don't hard code my DNS values so maybe they hadn't been fetched yet from my ISP's DHCP server at the time. That might be why dnsmasq loads, kills itself and loads again.

Click to expand...

That makes sense as an explanation of why /etc/resolv.dnsmasq wasn't there in your case then found a second later. But I'm not sure it explains why dnsmasq is killed and restarted since in my case /etc/resolv.dnsmasq is found and read, twice in fact, but dnsmasq is still killed and restarted.

That makes sense as an explanation of why /etc/resolv.dnsmasq wasn't there in your case then found a second later. But I'm not sure it explains why dnsmasq is killed and restarted since in my case /etc/resolv.dnsmasq is found and read, twice in fact, but dnsmasq is still killed and restarted.

While I'm asking questions, why in the QOS -> View Details screen are the ip addresses listed in alphabetical order instead of numerical?

For example, 192.168.1.11 comes before 1.92.168.1.2, but after 192.168.1.100. It makes reading the list a bit confusing.

Click to expand...

Perhaps they're being sorted as strings, not numbers? Maybe due to the "." separators? I never noticed that. In fact I was unable to verify it just because there weren't any entries that would be sorted incorrectly.

Perhaps they're being sorted as strings, not numbers? Maybe due to the "." separators? I never noticed that. In fact I was unable to verify it just because there weren't any entries that would be sorted incorrectly.

Click to expand...

I can pretty much guarantee they are being sorted as strings, but what's odd is that the original Tomato 1.28 firmware did sort them as numbers. Since that's what I'm coming from I find the difference jarring.

I can pretty much guarantee they are being sorted as strings, but what's odd is that the original Tomato 1.28 firmware did sort them as numbers. Since that's what I'm coming from I find the difference jarring.

Click to expand...

I just went and checked my QOS details just now and did see any example of the IP addresses being out of numerical order. Funny I remember years ago having to come up with a way in Microsoft Excel to properly sort IP addresses numerically. Hadn't thought about that in a long time, :smile:.

I probably would have never noticed this but seemingly you're right as I just went and checked my QOS details just now and did see an example of the IP addresses being out of numerical order this time.

Assuming the original Tomato had these sorted in numerical order, which I can't prove right now as I don't have it loaded on anything currently, wonder when it changed (and if it could be put back)? Not a big deal but I would think more useful in numerical order.

I just noticed something odd. The logout link didn't working under Toastman's v1.28.7466. When I clicked the link it brought me to the Goodbye page, but it didn't log out the browser. I've never seen that before.

I manually cleared the active logins in my browser (Firefox 4) and that logged me out. Then when I logged in and logged out it worked, but something weird happened that time.

Assuming the original Tomato had these sorted in numerical order, which I can't prove right now as I don't have it loaded on anything currently, wonder when it changed (and if it could be put back)? Not a big deal but I would think more useful in numerical order.

Click to expand...

My guess when they started to DNS resolution (well displaying host names) for the source ip addresses since that's something that's not in the original Tomato.

Just tested logout on my E3000 router running "Tomato Firmware v1.28.7466 MIPSR2-Toastman E3000 USB VPN" and it worked fine, just like always, Firefox 3.6.13, logging out brings me back to the login prompt where I'm directed to blank the password and try to login, clearned the credentials. Could be a Firefox 4 thing, but I'm not loading it to find out, I don't much care for the bleeding edge. Major new releases gotta be out for more than a few weeks before I go there. I actually got daring and ran the beta of Firefox 4 for a while and came to regret it so dumped it after it took a dump on me. Hell some of the time I even regret being on 3.6.x and think about going back further, :wink:.

Just tested logout on my E3000 router running "Tomato Firmware v1.28.7466 MIPSR2-Toastman E3000 USB VPN" and it worked fine, just like always, Firefox 3.6.13, logging out brings me back to the login prompt where I'm directed to blank the password and try to login, clearned the credentials. Could be a Firefox 4 thing, but I'm not loading it to find out, I don't much care for the bleeding edge. Major new releases gotta be out for more than a few weeks before I go there. I actually got daring and ran the beta of Firefox 4 for a while and came to regret it so dumped it after it took a dump on me. Hell some of the time I even regret being on 3.6.x and think about going back further, :wink:.

Click to expand...

I don't think it's a Firefox 4 thing since it appears to be working again, but something odd obviously happened.

I never really used the 'Log Out' feature ever since I flashed my routers with Tomato. And as far as I know, even the stock Linksys firmwares doesn't have this feature. I just close my browser - which is always set to auto-delete its cache...

Anyways, for the sake of testing, I tried it more than 20 times on a couple of laptops, and 3 desktops. All with IE9, a couple of desktops with the latest version of Chrome, (I've never been a fan of FF). All logged-off without any issues. So I think it works

@Toastman

I notice that the Linksys E4200 is now supported in your latest 7467 builds. I should get me one of those nifty routers to test 'em Also, the CTF (Cut-Through Forwarding) has been dropped in the Miscellaneous option? Or is it model specific? It's not much of a big deal. Just curious....

CTF apparently doesn't do anything useful, maybe because it's broken - but Teddy Bear has withdrawn it because it causes instability in iptables. It certainly never did anything here but cause aggravation, the same goes for Fast NAT, as far as I am concerned.

Be careful of the 4200 - there are reports coming in from the DDT forum of whole forests being burned down already, and electricity generators everywhere are struggling with the load!