I am running an ASUS RT-N16 (tomato) as my primary gateway. I just got a Cisco E2000 and loaded TomatoUSB without a hitch. I configured the E2000 as a wireless Ethernet bridge. It connects wirelessly to the ASUS RT-N16 without issue and my Windows 7 Laptop wired to the E2000 can access any shares on my LAN perfectly. What's frustrating me is the same laptop wired to the E2000 CANNOT access the internet. What gives!? I know there must be something simple I am overlooking…DHCP..firewall settings…help!
Date: 01 May 2011 05:22
Number of posts: 23
RSS: New posts
First the obligatory question, did you do a thorough NVRAM reset after first loading Tomato? If not then that can cause all sorts of weird problems.
Also do you have Static ARP enabled? If so, seemingly wireless ethernet bridge doesn't work with it, although WDS does.
When you connect to your shares are you connecting via IP address? If you are, your connectivity to the internet might be a DNS issue.
Thanks for all of the quick replies. NVRAM has been reset without resolution. I am not terribly familiar with Static ARP beyond what I've read since your post and cannot find where to toggle this setting in spite of scouring the menus. I have not knowingly changed this setting from its default (wherever it is). I can browse my LAN like always from windows and access files normally across my LAN. I cannot access internet sites even by entering their IP address.
If you didn't enable static ARP then it's probably not enabled. On my Toastman build it's at the bottom of the static DHCP list. If you're able to browse the LAN but not connect to the Internet then seems like it's either something stopping you, which is why I thought of static ARP, or you don't have a default gateway set, since a gateway shouldn't be required to access the LAN but would be for the Internet, but I can't think of why that would be the case. I'm assuming the IP address of your E2000 is on the same subnet but different IP address than the RT-N16. Can you open up a command window on your windows 7 box and run ipconfig to be sure you have a valid IP, subnet and default gateway?
OK so my wired client running off the E2000 seems to be pulling an IP (192.168.1.100) from the DHCP on the RT-N16 (my networks gateway). However, in ipconfig on my client laptop there is no Default Gateway listed…hmmm. Any clients connected to the RT-N16 directly (wireless or wired) seem to pull full DHCP info fine; ipconfig lists the Default Gateway accurately (192.168.1.1).
Solved! OK So I am happy but kind of embarrassed. This doesn't seem to be a tomato issue at all. When examining the ipconfig info as recommended by Tex, I made the findings above. I wired the laptop directly to my RT-N16…same problem @#$! Turns out DHCP was not enabled on my laptops wired adapter (for some totally unknown reason). Maybe Win7 did this as some sort of security measure…who knows. Anyway after enabling DHCP on the adapter, it works wired directly to the RT-N16 or more importantly over my E2000 functioning as a wireless Ethernet bridge. Incidentally I am using WPA2-AES security on the gateway and bridge and all seems to work fine. Just seems like some people have trouble with that. Anyway thanks for the help and hopefully resolution of my issue may help someone else out there. Thanks for all the hard work on Tomato and TomatoUSB !!
Thanks for your follow up! I was pulling my hair out the last few days because I couldn't figure it out either!
I could see other devices on my lan via the wireless ethernet bridge but couldn't find the internet, until I read your post!
Thanks so much! Now I have it working, N, 300 Mbs mode, and WPA2!! Again, I can't thank you enough!
Wireless Ethernet Bridge works for LAN but clients cannot access Internet
1. wired connect from main tomato router to laptop…. there is internet
2. wired connect from WEB tomato router to laptop…. no internet.
3. WEB router, tools->ping GUI of any websites failed
any idea? Could this bug due to wireless driver upgrade version?
Noted versions are the following:
1. version 126.96.36.199
2. version 188.8.131.52
3. version 184.108.40.206 <==== my WL driver version (no internet)
Problem could not be in WL driver, since it failed, no internet, on setup as additional AP.