Config WRT54GL on Tomato as AP

Running Tomato ver 1.28 on a WRT54GL and it's worked flawlessly as an AP (bridge) that then is wired to my pc. New house, new landlord and can't config this to wirelessly connect to a Linksys E1000.
Anyone know if the E1000 definitely will not play nice with a router set up this way? Know of an inexpensive AP model, any manufacturer?
I think it may be the version of Tomato. Version 1.28 will only allow AP mode to use WPA2 Personal, thus matching the E1000 settings. Landlord won't allow access or change his settings. I'm going mad trying to find a solution. Won't even tell you about a Netgear router I bought and another brand router on the way. Really just want my trusty Linksys/Tomato to work.
I'm preferring AP mode as that would be on the same subnet as the main (E1000) and seem to understand now how to release/renew in 2 of my OS's (XP and 7) but even after saving and connecting the routers LAN to LAN (and power cycle both) I get nothing.
Any assistance would be manna from heaven at this point. I have been w/o internet access for months except via wire when the landlord isn't here : )
Thank you,
Mac

Sarah, I believe cascade is a term used by Linksys for hardwiring two routers together. Yes, I found that kb article as well.
I'm trying to use the WRT54 as a wireless AP slash 'Client'; on the same network segment, so I can wire my pc to it. The main is using 192.168.1.1 as usual. Some folks use the term wireless bridge but the term bridge also refers to a specific wireless "mode" that means you're connecting 2 networks and that both routers will use DHCP to route traffic. I don't need that.
This worked before but I can't config it to connect with the Linksys. Unfortunately, I can't access the Linksys to make changes or attempt while security is temporarily off. So w/o delving into the flavors of Windows and Linux I use, I'm wondering a) if anyone knows positively that the Linksys will have a problem. I see no reason why, but Linksys may state you need both routers to be their brand.
b) I believe I've tried settings that should work (in Tomato's GUI), I save and connect LAN port to LAN port, do a power cycle, but then when I disconnect and try the wireless 'AP' - the WRT54 - I get no connection. Security settings match and the main - the E1000 - is only about 30 feet away, same floor. Just some wood and drywall between them.
The way I'm using the routers is simple, using Tomato is a little off the beaten path (and Tomato has no central community on the web that I can find) but the settings are pretty simple. Many have done this with different combos of routers yet I cannot get these two to function, hence question a).
Again, any help would be extremely appreciated.
Thank you,
Mac

Similar Messages

Use WRP400 (VoIP Router) for Voice only, and the rest with WRT54GL

Hey there, I hope you are doing great!
The reason of this thread is because I recently moved to a cable ISP and unfortunately had to also change routers in order to take advantage of the VoIP feature (analog phone) they provided me with.
Now, the new router, the WRP400, is very limited feature-wise compared to the custom flashed WRT54GL I used to use with my DSL provider.
Now the WRT54GL does not have any FXS ports, so I obviously can't just plug my cable modem to the WRT54GL. Therefore, I was hoping to achieve a setup similar to this one:
Cable modem => VoIP Router w/ voice only (WRP400) => "Main" router (WRT54GL w/ Tomato)
Is there a way to bridge the WRP400 successfully with the WRT54GL keeping only the voice feature enabled on the VoIP router while the WRT54GL takes care of the rest? (Wireless, WAN, port forwarding, etc)
Thank you very much for your help, and have an awesome day!
Lev

I am going to provide a few snapshots of the config pages as to make this easier:
Basic setup page
Advanced Settings
Administration Page
Once more, thank you very much for the assistance!

The host name cannot be resolve ? ( with linksys router )

Hi all, I have some problem with setting up a network. I tried to set my network according to http://wiki.archlinux.org/index.php/Configuring_network the network/internet is fine except the host name with "http://" cannot be resolve. For example
ping 216.239.61.104
ping www.gogle.com
both work fine, until I try,
ping http://www.google.com
it give me error, tell me that the hostname cannot be resolved. I tried to config my network using both dhcp or fix-ip, but the problem still present in both way. Internet works fine in windows/ubuntu.
Anyboy has any clue ? The router I use is wrt54gl with tomato firmware.
thanks in advance.

kowalski wrote:
Hi,
if pinging www.google.com works then dns resolving _does_ work. Why would you want to ping http://something?
You should try opening http://whatever in a browser not pinging it from command line.
Or am I missing something obvious?
Yes, for instance, all mirror list for pacman is in "http://...." or "ftp://...." form. I could easily change the repository list, but I'm not sure if it'll have same problem in future with other program. Also, if it work in ubuntu and windows, why not arch.

Time Capsule Can't connect to my wireless network

Hi there,
I can't connect my new Time Capsule to my existing wireless network. I followed screen instructions, set up my network name and password, then time capsule need to be disconnected and then nothing.. My MacBook Can't see Time Capsule
I did restored it to factory and tryed manual setup but didn't work either.
Any sugestions?
Thank you

what is your current router? (the one you're trying to connect to with your TC)? If it's not Apple (Airport series, another TC) you'll mose likely experience compatibility issues. With 3rd party routers (non-Apple) it's hit and miss. Some tips:
1. use WEP not WAP as encryption
2. Make sure your current router supports WDS, set it to turn WDS on
3. try with no encryption, if you can connect, then try WEP, then WPA, you'll see where the problem is.
4. some routers, even if spec doesn't say so, work well in WDS mode and even work with TC with WPA on. The trick is to load them with "special" firmware. Linksys WRT54GL with Tomato or DD-WRT firmware is a good example. Check if there's any alternative firmwares for your router. Start here:
http://www.polarcloud.com/tomatofaq#whatwill_this_runon
Good luck!

Samba Howto: OSX10.5.8, Linux, WinXB, Win7 shares

*Samba Howto: OSX10.5.8, Linux, WinXB, Win7 share*
After several day of research and trial and error i found a solution, so that the Finder of OSX 10.5.8 shows all samba3 shares (irrespective of the operating system) in the left sidebar below the category SHARES.
My local home network consists of an iMac 6.1 (OSX10.5.8), a MacBook 3.1 (OSX10.5.8), a Synology DSXXX (Linux), a VMWare Win7 (testing environment), a VMWare WinXP (testing environment) and Linksys WRT54GL (firmware Tomato 1,27).
On both Mac and the DS209 I don't use the built-in Samba systems!! Instead I use Samba 3.2.15 from macports on both Macs and on my Synology DSXXX I use Samba 3.2.15 from ipkg. On Windows 7 and Windows XP I use the built-in systems.
_Install macports Samba3_
DO NOT ACTIVATE THE BUILT-IN SAMBA!!!
*Important note*: The portfile of samba3 has a bug. Therefore you have to open the portfile (in a text editor) and add tow lines of code (see below). You will find the macport-samba3-portfile under
/opt/local/var/macports/sources/rsync.macports.org/release/ports/net/samba3/Port file
Change the original portfile from
system "installnametool ${changeline} ${destroot}${prefix}/bin/tdbtool"
system "installnametool ${changeline} ${destroot}${prefix}/bin/testparm"
livecheck.type regex
to
system "installnametool ${changeline} ${destroot}${prefix}/bin/tdbtool"
system "installnametool ${changeline} ${destroot}${prefix}/bin/testparm"
+system "installnametool ${changeline} ${destroot}${prefix}/sbin/smbd"+
+system "installnametool ${changeline} ${destroot}${prefix}/sbin/nmbd"+
livecheck.type regex
Afterwards you can install samba3 using the normal macport commands (or Porticus).
_Create a smb.conf_
After the installation create a smb.conf file under /opt/local/etc/samba3. (I will present only the \[global\] section of my smb.conf.)
Note: replace <specification> with specifications of your computer system
--begin smb.conf
\[global\]
workgroup = WORKGROUP
netbios name = <computername, see system-preferences->Filesharing>
server string = <computername, see system-preferences->Filesharing>
hosts allow = 192.XXX.X. localhost
socket options = TCP_NODELAY
\# use my synology ds209 as wins server
wins server = 192.XXX.XXX.XXX
name resolve order = wins lmhosts hosts bcast
\# my imac/macbook never gets local master browser
domain master = no
local master = no
preferred master = no
os level = 0
winbind enum users = yes
winbind enum groups = yes
idmap uid = 10000-110000
idmap gid = 96000-196000
max smbd processes = 10
security = user
map to guest = Bad User
encrypt passwords = yes
passdb backend = smbpasswd
smb passwd file = /opt/local/var/db/smb/smbpasswd
log file = /opt/local/var/log/smb/log.%m
log level = 0
max log size = 50
--end \[global\] sector smb.conf
_Test your samba installation_
Now you can test your samba server running as daemon using the commandline:
/opt/local/sbin/smbd -D
/opt/local/sbin/nmbd -D
Check if your samba server configuration works:
ps -ax | grep smbd
ps -ax | grep nmbd
If the samba server runs well, stop it:
/opt/local/bin/smbcontrol smbd shutdown
/opt/local/bin/smbcontrol nmbd shutdown
_Create LaunchDaemon files_
Build a wrapper file and a LaunchDaemon file in order to start the samba sever automatically at boot time. (I modified the wrapper and plist files from a official macports mysql installation.)
--beginn wrapper script
#!/bin/sh
\# MacPorts generated daemondo support script
\# Init
prefix=/opt/local
\# Start
Start()
/opt/local/sbin/smbd -D
/opt/local/sbin/nmbd -D
\# Stop
Stop()
/opt/local/bin/smbcontrol nmbd shutdown
/opt/local/bin/smbcontrol smbd shutdown
\# Restart
Restart()
Stop
Start
\# Run
Run()
case $1 in
start ) Start ;;
stop ) Stop ;;
restart) Restart ;;
* ) echo "$0: unknown argument: $1";;
esac
\# Run a phase based on the selector
Run $1
--end wrapper script
--beginn LaunchDaemon script
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Debug</key>
<false/>
<key>Label</key>
<string>org.macports.samba3</string>
<key>OnDemand</key>
<false/>
<key>ProgramArguments</key>
<array>
<string>/opt/local/bin/daemondo</string>
<string>--label=samba3</string>
<string>--start-cmd</string>
<string>/opt/local/etc/LaunchDaemons/org.macports.samba3/samba3.wrapper</string >
<string>start</string>
<string>;</string>
<string>--stop-cmd</string>
<string>/opt/local/etc/LaunchDaemons/org.macports.samba3/samba3.wrapper</string >
<string>stop</string>
<string>;</string>
<string>--restart-cmd</string>
<string>/opt/local/etc/LaunchDaemons/org.macports.samba3/samba3.wrapper</string >
<string>restart</string>
<string>;</string>
<string>--pid=none</string>
</array>
<key>RunAtLoad</key>
<false/>
</dict>
</plist>
--end LaunchDaemon script
_Install the wrapper and the plist files_
Create a directory using the commandline:
mkdir -p /opt/local/etc/LaunchDaemons/org.macports.samba3/
Save both files in the new created directory.
Call the wrapper script samba3.wrapper.
Call the plist script org.macports.samba3.plist.
Change to the following directory:
cd /Library/LaunchDaemons/
Create a symlink to the samba3 plist script:
ln -s /opt/local/etc/LaunchDaemons/org.macports.samba3/org.macports.samba3.plist
Load the plist file using launchctl on the commandline:
launchctl -w load /Library/LaunchDaemons/org.macports.samba3.plist
Now smbd and nmbd should start at boot time.
_Create a samba WINS server_
*Important note*: ONLY ON SYSTEM IN A LOCAL NETWORK SHOULD BE A WINS SERVER!!
If you don't have a Synology DSXXX try to run one of the OSX10.5.8 system as a WINS server or use a Linux box.
Chance therefore the smb.conf file from above in the following way:
replace <specification> with specification of your computer-system
--begin snb.conf
\[global\]
workgroup = WORKGROUP
netbios name = <computername, see system-preferencies->Filesharing>
server string = <computername, see system-preferencies->Filesharing>
hosts allow = 192.XXX.XXX. localhost
socket options = TCP_NODELAY
local master = no
\# my synology ds209 works as wins server
wins support = yes
name resolve order = wins lmhosts hosts bcast
dns proxy = yes
\# my synology ds209 works as local master browser
domain master = no
local master = yes
preferred master = yes
os level = 65
winbind enum users = yes
winbind enum groups = yes
idmap uid = 10000-110000
idmap gid = 96000-196000
max smbd processes = 10
security = user
map to guest = Bad User
encrypt passwords = yes
passdb backend = smbpasswd
smb passwd file = /opt/etc/samba/smbpasswd
log file = /opt/var/samba/log.%m
log level = 0
max log size = 50
--end \[global\] sector smb.conf
If you have a Synology DSXXX install samba 3.2.15 using ipkg. I won't here explain how you can install ipkg on a DSXXX. You will find a lot of information about this topic in different synology support, wiki and forums sites.
*Important note*: DO NOT ACTIVATE THE BUILT-IN SAMA SYSTEM!!
After you have installed the ipkg samba 3.2.15 on your DSXXX use the smb.conf file above in order
to create a WINS Server on your DSXXX. (Hint: You will find the netbios name and the server string using the Webinterface Disk Station Manager 2.X -> Network -> Servername.)
*Addtional Note 1*: I really think that you can run every linux box as a WINS Server, because the Synology operating system is linux (as far as I know).
*Addtional Note 2*: On my Linksys WRT54GL I use static DHCP for all components of my local network.
*Addtional Note 3*: I Have filled in Router Name (MyRouter), Hostname (MyRouter) and Domain Name (myzone.com) under Router Identification in Tomato 1.27. (Without this I couln't find my Linksys WRT54GL via full qualified domain name.)
Kind regards, maninfo

in laptop pc with arch i have installed somewhat in gnome under System-->administration called "shared folder". Maybe this sort of software override manual configuration in /etc/samba/smb.conf?
Something like that is probably standing in ubuntu as well i suppose..
Last edited by jacopastorius82 (2010-11-03 22:13:53)

Using External monitor with DVI kills wireless connectivity

I recently purchased a BenQ G2400WD 24" 1920x1200 monitor, for use with my May 2007 GMA 950 2.0Ghz. Macbook.
Upon receiving the monitor, I immediately plugged it in to my Macbook, using the Mini-DV to VGA adaptor I already had, for use with projectors. The monitor was good, but a bit blurry and not too sharp, due to the analog signal. So I ordered a Mini-DVI to DVI adaptor. When it arrived, the improved picture quality was immediately apparent.
However, as time went on, I noticed my wireless connectivity was getting terrible. Extremely slow Safari page load times, and upon going to Terminal and pinging my router, I would often get response times of 21000 milliseconds, or worse! I did a lot of research, on router firmware, on wireless connectivity, etc., but to no prevail. Then, on a whim, while continually pinging my router, I removed the DVI adaptor from my monitor. The ping instantly dropped from tens of full seconds to just a stable 0.4 milliseconds! Using my VGA connection resulted in no worse wireless connectivity than without it, but upon plugging in DVI and stressing the connection a bit (i.e. downloading a large file), the connection went bonkers. The pings also immediately jump from 0.4 milliseconds to a range of 1-4 milliseconds, regardless of any "stressing".
I have done numerous research, including searching both here and on other discussion forums. It appears this problem with DVI connection is fairly common, but with no resolution so far. Any help would be great!
A few important notes:
-Both ends of both my VGA cable and my DVI cable are shielded.
-I have tried numerous channel changes of my router, to no prevail.
-While using DVI, EVERYTHING works well except the wireless. So the monitor isn't too demanding for my computer.
And I hope my thorough post didn't scare you away!

I have this same issue with the dvi and wireless disconnect. I am using a samsung 214T. I am glad to know i am not the only one seeing this, because it is kind of one of those things that is hard to believe. Anyway, I am also curious what kind of routers people have who are experiencing this issue. I am using a wrt54GL with tomato firmware.
Also, In addition to the disconnect, my picture quality on my monitor gradually degrades over time...starting with what looks like snow flecks. After waking from screen saver, sometimes it is full static. Turning off and turning back on the monitor clears the static away.
I can use another samsung 19in monitor with dvi without any problems.

E1200 - Initial setup difficulties

I don't even know where to start... it's basically a poorly designed router! Every time you change a setting you start praying for this to come back.. most of the time you have to reset it to the defaults and start from the beginning. Try changing the routers name after the initial setup.. it immediately quits working and you are back to the hard reset. Try changing the security mode after the initial setup.... it quits.. well you get the picture. I would stay away - avoid! The good part is that once it's setup the internet works well with very good range. I might return and get the 10 year old Cisco-Linksys WRT54GL with Tomato firmware... way easier to setup and operate. I am afraid of touching this "router", god knows what it takes to add a printer to this - Another 3 hours waisted.

That’s pretty strange. Normally it’s just a matter of running the Cisco Connect CD that comes with the router and you’re up and running in under ten minutes. When you mentioned having to reset the router, do you mean by pressing the reset button or just unplugging and replugging the power to the device?

Macbook wireless connection

My macbook has recently started having problems with connecting to every wireless network I normally use. When I move more than approximately 10 feet away from any wireless router my signal strength plummets. When I ping as I move away I lose most, if not all, of the packets, and some of the packets have taken as long as 1 second to return. I think that I have tried every single suggestion I have found on any help site. I have been using 10.4.11 since it became available, but I don't specifically recall having problems since this change. I just did an archive and install from my install disc back to 10.4.6 and updated to 10.4.9 because that seems to be the OS that nobody reports having problems with. Even with this, the problem persists. Might my airport card be damaged or loose? Any suggestions will be appreciated. I'm desperate to the point of performing surgery.

Hi all,
I'm having issues with WiFi too... When I'm at home and WiFi is not strong enough (too far away, too much walls...) connections seems to be full 4 bars, dropping to 2, to 1 back and forth...
Sometimes turning it on, it's not finding the WLan for autoconnect, or suggests me to type in the password again... Very strange: Sometimes it says that none of my preferred networks are available and suggests to connect to others. In the list I can find my own network again!!! Choosing it mostly leads to connection timeout...
I have similar problems at other locations, but I'm not sure if I'm in the WiFi range all the time (although I think so)...
I did also think, sth. with my router (WRT54GL with Tomato firmware) is not OK or it's not positioned very well in my flat... Experimenting with it, I found kinda sweet spot and connection was ok, but all of a sudden, there was this weird thing:
Testing with the ping response time and packet loss, I confirmed, that response time is <3ms average and no packet loss... But afterwards the ping response time fluctuates back and forth:
64 bytes from 192.168.1.1: icmp_seq=964 ttl=64 time=0.883 ms
64 bytes from 192.168.1.1: icmp_seq=965 ttl=64 time=0.895 ms
64 bytes from 192.168.1.1: icmp_seq=966 ttl=64 time=0.928 ms
64 bytes from 192.168.1.1: icmp_seq=971 ttl=64 time=2786.449 ms
64 bytes from 192.168.1.1: icmp_seq=972 ttl=64 time=1786.363 ms
64 bytes from 192.168.1.1: icmp_seq=973 ttl=64 time=786.265 ms
64 bytes from 192.168.1.1: icmp_seq=974 ttl=64 time=0.916 ms
64 bytes from 192.168.1.1: icmp_seq=975 ttl=64 time=0.883 ms
64 bytes from 192.168.1.1: icmp_seq=976 ttl=64 time=0.933 ms
64 bytes from 192.168.1.1: icmp_seq=977 ttl=64 time=1786.283 ms
64 bytes from 192.168.1.1: icmp_seq=978 ttl=64 time=786.423 ms
64 bytes from 192.168.1.1: icmp_seq=979 ttl=64 time=0.874 ms
64 bytes from 192.168.1.1: icmp_seq=980 ttl=64 time=0.837 ms
64 bytes from 192.168.1.1: icmp_seq=981 ttl=64 time=3.301 ms
64 bytes from 192.168.1.1: icmp_seq=982 ttl=64 time=1787.292 ms
64 bytes from 192.168.1.1: icmp_seq=983 ttl=64 time=787.165 ms
64 bytes from 192.168.1.1: icmp_seq=984 ttl=64 time=0.864 ms
64 bytes from 192.168.1.1: icmp_seq=985 ttl=64 time=0.884 ms
64 bytes from 192.168.1.1: icmp_seq=986 ttl=64 time=0.815 ms
64 bytes from 192.168.1.1: icmp_seq=987 ttl=64 time=1786.229 ms
64 bytes from 192.168.1.1: icmp_seq=988 ttl=64 time=786.278 ms
64 bytes from 192.168.1.1: icmp_seq=989 ttl=64 time=0.929 ms
64 bytes from 192.168.1.1: icmp_seq=990 ttl=64 time=0.770 ms
64 bytes from 192.168.1.1: icmp_seq=991 ttl=64 time=0.929 ms
64 bytes from 192.168.1.1: icmp_seq=992 ttl=64 time=1784.993 ms
64 bytes from 192.168.1.1: icmp_seq=993 ttl=64 time=785.073 ms
64 bytes from 192.168.1.1: icmp_seq=994 ttl=64 time=0.828 ms
64 bytes from 192.168.1.1: icmp_seq=995 ttl=64 time=0.936 ms
64 bytes from 192.168.1.1: icmp_seq=996 ttl=64 time=0.881 ms
64 bytes from 192.168.1.1: icmp_seq=997 ttl=64 time=1785.504 ms
64 bytes from 192.168.1.1: icmp_seq=998 ttl=64 time=785.865 ms
64 bytes from 192.168.1.1: icmp_seq=999 ttl=64 time=1.349 ms
64 bytes from 192.168.1.1: icmp_seq=1000 ttl=64 time=0.902 ms
64 bytes from 192.168.1.1: icmp_seq=1001 ttl=64 time=0.957 ms
64 bytes from 192.168.1.1: icmp_seq=1002 ttl=64 time=1783.032 ms
64 bytes from 192.168.1.1: icmp_seq=1003 ttl=64 time=783.530 ms
64 bytes from 192.168.1.1: icmp_seq=1004 ttl=64 time=0.940 ms
64 bytes from 192.168.1.1: icmp_seq=1005 ttl=64 time=0.959 ms
64 bytes from 192.168.1.1: icmp_seq=1006 ttl=64 time=0.867 ms
64 bytes from 192.168.1.1: icmp_seq=1007 ttl=64 time=1781.236 ms
64 bytes from 192.168.1.1: icmp_seq=1008 ttl=64 time=781.330 ms
64 bytes from 192.168.1.1: icmp_seq=1009 ttl=64 time=1.308 ms
I thought, this was the routers fault, but after restarting the MacBook, it's all fine again!
Please note that these weird ping times came up when I was in the same room or even a few feet away from the router! Also The Wifi Symbol frequently reduced signal strenght by 1 to only 3...
I really don't know what causes this. Especially because this is not makeing problems all the time... I.E. connections is quite good sometimes and even in a big room with only one small access point hanging around for several douzen people, connection might be good and fast...
Best Regards,
kuetsch

Limit bandwidth per IP with Speedtouch 780WL

I want to limit the bandwidth to certain IPs in my network. However, I have no idea how to do this. My router is Speedtouch 780WL. Are there some telnet options for this?

I suggest using a Linkys WRT54GL with tomato firmware. See also:
[Tomato] QoS Bandwidth limit for IP-range?
[Tomato] limiting bandwith on wireless side of wrt54g
Last edited by Kasumi_Ninja (2010-11-13 16:59:25)

Pressed reset button on Tomato flashed WRT54GL , now can't connect to Internet

Hi everybody. I couldn't connect to the Internet yesterday and so I pressed the reset button on my WRT54GL which I flashed with Tomato firmware. This is the first time that I lost connection. I can access the http://192.168.1.1 site but I don't know what it the right configuration for my WRT54GL to be able to access the Internet. Did I bricked my router because I pressed the reset button? I can access the Internet when I plug the ethernet directly to my laptop. Any ideas? Thanks in advance.

You have to ask in a forum for tomato firmware. They should know what happens if you press the reset button. Here, in this forum, we usually deal with Linksys firmware.

Cannot Access WRT54GL Config Page

I am doing some consulting work for a small business and cannot gain access to the routers configuration page. Here is a summary of the environment:
* WRT54GL, ver. 1.1.
* The WAN port of the router is connected directly to the Verizon DSL modem for Internet access.
* Port 1 is connected to the main switch (192.168.102.x subnet).
* Users can also connect to this router by wireless (192.168.3.x subnet).
* When I connect to the wireless network, it appears that the router has been assigned an IP address of 192.168.3.1. When I execute an ipconfig command:
Connection-specific DNS suffix: lan
Dhcp Enabled: Yes
Autoconfiguration Enabled: Yes
IP Address: 192.168.3.240
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.3.1
DHCP Server: 192.168.3.1
DNS Server: 192.168.3.1
* When I connect to the "wired" network, it appears that the router has been assigned an IP address of 192.168.102.254. When I execute an ipconfig command:
Connection-specific DNS suffix: ourcompany.com
Dhcp Enabled: Yes
Autoconfiguration Enabled: Yes
IP Address: 192.168.102.111
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.102.254
DHCP Server: 192.168.102.15
DNS Server: 192.168.102.254
* When I am on the wireless network, I can successfully ping 192.168.3.1 and 192.168.1.1. When I ping 192.168.102.254, it resolves to 192.168.3.1 and returns a "Destination port unreachable".
* When I connect to the "wired" network, I can succesfully ping 192.168.3.1 (as well as 192.168.102.254 - obviously), but I cannot ping 192.168.1.1 ("Request timed out").
ACTIONS:
1) I am trying to connect to the WRT54GL device to examine the configuration and create a route between the two networks. I have downloaded Linksys Easylink Advisor and I can see the network (on both connections), but cannot get into the configuration pages I receive an error ("MSG_100_000_000 Unhandled error ...") and then goes into an endless loop "Retrieving Router Settings".
2) When I attempt to access through a web browser (from both subnets), I get a "page not found" error.
3) I connected a cable directly to an open port in the router. I immediately had Internet access and was assigned an IP in the 192.168.3.x subnet. Still I could not connect to the administration page on either 192.168.3.1 or 192.168.1.1.
4) Power cycled the router and re-attempted 1,2, and 3 above - same result.
5) Downloaded the latest firmware upgrade and tried to apply through linksys-ftp (while connected directly to the router). In the dialogue box I entered 192.168.1.1 and the default password of 'admin' and pointed to the firmware upgrade file. After clicking the "Upgrade" button and three tries, I get an "Unable to get responses from server" message. This also happens when trying to connect to 192.168.1.1.
6) Since I am not sure whether I should be connecting to 192.168.3.1 or 192.168.1.1, I also tried to assign a static IP on my laptop in the 192.168.1.x subnet, but that left me with no network connection at all.
SO .... where do I go from here? I know I can do a reset and get back to the factory installed settings on the router, but I really prefer NOT to do that. Whoever set this up is long gone, and no one here has any idea about the network or even who it was that set it up. I think it would take a long time to reconstruct things (during off hours since people need to be connected to the network all day), so I don't want to go down that path.
Any help or insights would be greatly appreciated.
Thanks,
Tom

What is the model of the switch that you are using? Is this just a plain pass through switch or a manageable one? I am curious where you are getting that 192.168.102.x ip range. If wired to the router you are getting 192.168.3.1, then that should be the address that you use when you run the tftp utility. And also what is the ip address that you are getting from the modem? Is the modem bridged or is it functioning as a modem/router?
If you want to upgrade the router's firmware, I suggest that you remove the switch and the modem from the loop and see if you can access the router interface. If you cannot, then reset the router for 30 seconds, powercycle it and see if you can now access the router interface.

Linksys WRT54GL - tomato upgrade failed - SOLVED

Hello,
I had a problem with Tomato 1.28. I wanted to upgrade it as the procedure sais ( the procedure in readme.htm file ) Unfortunatelly I saw some error message like "Upgrade are failed" or something like this. Hopefully, when I disconnected router from power and connected it again, it was working I googled a liitle bit and this is what I did.
1. I disabled antyvirus
2. I disabled firewall
3. I changed my IP settings to IP address 192.168.1.10 and Netmask 255.255.255.0
4. I made sure there are no any more IP addresses, no DNS, no Gateway and no alternate IP addressess in Advanced settings.
5. I closed Firefox
6. I opened Opera
8. While the router was connected to power, I pressed "RESET" button and holded it for 30 seconds
9. I logged in. I typed in Opera 192.168.1.1 and provided login/password credentials
10. I selected Administration and upgrade firmware section. I choosed WRT54G_WRT54GL.bin file which was unpacked from Tomato_1_28.7z file
11. I pressed confirmation button. This time everything worked fine.
And what was before....
1. Antyvirus was enabled
2. Firewall was enabled
3. I didn't care for IP settings, i just put 192.168.1.3 , I left gateway and dns IP addresses , maybe even I put alternate IP address in advanced settings
4. I used Firefox
6. I took a new router from the box and didn't press "RESET" button
9. I logged in. I typed in Firefox 192.168.1.1 and provided login/password credentials
10. I selected Administration and upgrade firmware section. I choosed WRT54G_WRT54GL.bin file which was unpacked from Tomato_1_28.zip file
11. I pressed confirmation button and I saw "Upgrade are failed" or something similar.
I hope it will help someone.

On your computer click on Start - RUN - CMD and click OK... In the Command Prompt window type "ipconfig" and hit enter and note down the IP address and the Default Gateway IP (Default Ip address for the router is 192.168.1.1)... Again in the Command Prompt window type "ping 192.18.1.1" and hit enter and check if you are getting any response from the Router, if not then Press and hold the reset button for 30 seconds...Release the reset button...Unplug the power cable from your router, wait for 30 seconds and re-connect the power cable... and again in the Command Prompt window type "ping 192.168.1.1" and hit enter and if you are getting any response from the Router, then you can try to update the firmware of your Router using the TFTP Utility..
Click on Download 44.3 KB the TFTP Utility.
Follow these steps to upgrade the firmware on the device : -
Double click the TFTP.exe file and click run.
For Server- Enter the IP Address of the router that you assigned. By default, the router is 192.168.1.1...
For Password- Enter the password you assigned the router. By default, the router’s password is “admin”.
For File- Click the triple “…” button and browse for the .bin firmware file...
Click Upgrade button to start upgrading. A progress bar should show up to show the progress.
Once the Upgrade is done press and hold the reset button for 30 seconds...Release the reset button...Unplug the power cable from your router, wait for 30 seconds and re-connect the power cable...Now re-configure your router...

WRT54GL config. advice please

I am trying to install "Express Talk" soft phone and it is giving me the following message:- >>"A 'Symetric' NAT or router has been detected between this computer and the internet. This means audio cannot be routed to this computer automatically. You are strongly advised to manually set up RTP/UDP redirection at the router or NAT otherwise audio may be delayed, low quality or broken." I checked to manual and the only thing that looks related is the "Filter Internet NAT Redirection" which I have tried "on" & "off" which made no difference, ie still get the same message. Could someone give me some directions please?? Cheers, Phill.

Most standard NAT routers are symmetric NAT. As they try to preserve the port number if possible they may be perceived at times as restricted cone or port restricted cone nat but this will immediately disappear for one computer in the LAN if two computers try to access the same port on the same server in the internet at the same time.
Thus it is pretty much inevitable to configure port forwardings instead. In particular in case you to try access the same internet server from two computers inside the LAN.
You have to configure a static IP address on the computer on which you run the softphone first, e.g 192.168.1.10.
Then forward the ports which the softphone uses. It depends on what you have configured in the softphone. Check the configuration for that. You have to look for the SIP port is listens to (do not confuse this with the SIP port of the service provider) and the RTP ports is uses. With the softphone running you can check the SIP port in a command prompt window. First enter "tasklist" and look the name of the executable of your softphone. Remember the PID number in the second column of that line. Next enter "netstat -aon" and look for the PID in the last column. All lines with the PID in the last column are the SIP ports on which the soft phones listens. If you'll see something like "UDP 0.0.0.0:5060" it means the program listens on port 5060. Take a note of all ports on which the program listens. If in doubt, post the full output of "netstat -aon".
Again, this will only show the SIP ports. It probably won't show the RTP ports as they are allocated during the call. Look through the configuration to find those ports. It has been suggested before that ports 8000-8020 are used for this purpose. But I don't know express talk and the ports can probably be changed in the program.
Now forward all SIP ports and the range of RTP ports to the static IP address of your computer. Always forward UDP. Save the changes.
Next please also verify that your router is directly connected to the internet: click on the Status tab. This will show you the current IP address of the router on the internet port. Then open http://whatismyip.com/ in your browser. It shows your public IP address as seen from the internet. Both IP addresses must be identical. If they are not identical you have another NAT router in your path to the internet. (Often the modem.) Your router is not directly connected to the internet. Configuring port forwarding on your router is futile unless you also configure the same port forwardings on the upstream NAT router.

Bug in ip routing in WRT54GL?

Hi everyone! During Christmas I had some problems with my WRT54GL. I'm connecting to the Internet with a Speedtouch 510 with PPPoE and dynamic ip. The Speedtouch takes care of the PPPoE login and it's set to "PPPoE in bridged mode" which means that the public ip address is passed to my computer/router or whatever is put on the "LAN" side of the modem. When I was away for Christmas I noticed that I couldn't reach my home computer anymore. When I got back the ip for my connection had changed. I usually get a 83.177.x.y address with the gateway 83.177.8.1, but this time I got the ip 90.130.6.30. Neither my computer or the WRT54GL could ping or reach anything outside my WAN ip. Until then I had been using the tomato firmware, I tried installing the original Linksys firmware, but I got the same result. Connecting the Speedtouch directly to my computer worked fine, which to me kind of proves that something is wrong with the WRT54GL. Any ideas on how to troubleshoot this? My solution was this; I think the problem occurs because of a bug in the WRT54GL firmware. The following configuration (recieved through dhcp) works fine: IP Address 83.177.13.213 Subnet Mask 255.0.0.0 Gateway 83.177.8.1 the following works when connected directly to the computer, but not when using WRT54GL: IP Address 90.130.6.30 Subnet Mask 255.0.0.0 Gateway 83.177.8.1 The solution was to power off the modem long enough for the dhcp lease to expire, power it on and hope to get a 83.x.y.z ip address (which I got and then everything worked as usual). I'm guessing the WRT54GL cannot handle either the subnetmask of 255.0.0.0 on the WAN interface and/or maybe in combination with the gateway on a address which differs from the wan ip. Thankful for any comments on this. Cheers, Tobias

Thank you Rich! Yes, that link between NetFlow and routing-not-bridging is beginning to sink in for me.
My reason for bridging is that I do not need VPN or NAT, I just need the subnet (ip) traffic to flow from gi0/1 to gi0/0 and back. I have been reading and re-reading this article, http://www.netcraftsmen.net/resources/archived-articles/428-integrated-routing-and-bridging.html, and it seems that "concurrent" or "integrated" routing and bridging may be the way to go.
I am concerned that, to the extent that the ip traffic is bridged (not routed), it will be invisible to NetFlow, for exactly the reason that you describe. So even if I set up a CRB or IRB, I might not get useful NetFlow data.
Or maybe there is a way to configure ip routing so that there are hardly any decisions made, rather the subnet goes straight through in both directions. I fear that is such a simple case that no one makes examples for it. I have been assigned half of a class C subnet, e.g. 209.201.225.1 through .127. I am not terribly short on ipv4 numbers so I can use up a number for the gi0/1 and/or gi0/0 and/or BVI interface(s).
For ~14 years a Cisco 2621 router has been used "here" purely for the purpose of traffic shaping. I recently upgraded to the Cisco 1941 and am keen to take advantage of traffic peak shaping and NetFlow v5 or v9. I took the config from the 2621 and used it as the basis for my config for the 1941.
I am (obviously) very new to all this and self-taught. My expert is currently ridiculously overbooked so I am trying to figure it out. In other words, I will not feel offended if you need to state the "obvious" to steer me in a useful direction.
Ann

WRT54GL using old modem/router as modem component?

I'm constantly having little issues with my ADSL modem/router, which is some Taiwanese unbranded model that my girlfriend provided.
As such, I'm thinking about buying the WRT54GL, and using Tomato or perhaps OpenWRT.
Given that this is just a router, I'll need an ADSL modem too. Will my current modem/router model be able to perform as the modem only?
(Or does it really depend exactly what my router is capable of? If so, are there any settings that I should look out for in the router web config pages, because I'm quite new to this stuff.)
Thanks.

chrispoole wrote:
OpenWRT seems nice, but I've never run Linux on any embedded systems, or used network devices more than the average consumer usage.
It seems a bit too technical to me. It seems to be a full-blown little distro, that can could be used to turn the 54GL into a seed box (perhaps?), if I understand correctly?
Tomato seems a lot easier to install and use, for my requirements.
Tomato may be easier yes - less modular, so more stuff out of the box. You barely need the command line anymore with the latest OpenWrt though, if you do not want to use it.
As for being a seed box - you need a way to connect a HD to your router for that, and the WRT54G(L) series don't have any USB ports for example to my knowledge, so it depends on your connectors (and available RAM, most importantly).

Config WRT54GL on Tomato as AP

Similar Messages

Maybe you are looking for