dslreports logo
site
spacer

spacer
 
    All FAQs Site FAQ DSL FAQ Cable Tech About DSL Distance DSL Hurdles »»
spc

spacer




how-to block ads




1.3 Utilities

SNMPLog
Kiwi Syslog Daemon
SNMP Trap Watcher
SNMPLog
Linksys Logviewer
WallWatcher
Link Logger
Log Viewer

List courtesy of Link Logger See Profile.

by Lanik See Profile
last modified: 2008-08-19 14:30:35

DSLReports Security Scanner tests your firewall.

Shields-Up Port Scan
tests your firewall.

DSLReports Tweak Tester checks your Windows TCP/IP parameters for broadband.

DrTcp (Windows Executable Download)...Set your RWIN and MTU.

Nuke WinPoet cleanly gets rid of that pesky PPPoE client WinPOET.

MacTFTP uploads firmware to router (MacOS).

TFTP uploads firmware to router (Windows)

SNMP Trap Watcher is a free Win95/8/NT/2K utility that displays and logs the SNMP Trap messages that the Linksys routers send during operation. These include both inbound and outbound connections, plus a plethora of other diagnostic and informative messages.

Freeware for Windows includes several utilities including "Active Ports" to monitor all open TCP and UDP ports on the local computer which helps determine what port(s) may need forwarding for a particular program.

by lev See Profile edited by Lanik See Profile
last modified: 2005-11-25 15:57:43

ZoneAlarm Download a software firewall free for personal use.

by lev See Profile edited by Lanik See Profile
last modified: 2005-06-22 00:16:44

If you are using WallWatcher as a logger program for a Linksys router on a Windows XP Professional system, you might want to consider running it as a service. The advantage is that if the computer is on, WallWatcher is running regardless of whether or not anyone is currently logged on the machine.

First, if you have not already done so, download WallWatcher from http://www.wallwatcher.com and install according to the instructions. WallWatcher needs to be properly installed before proceeding with these instructions.

Next download SRVStart.exe from http://www.nick.rozanski.com/software.htm and install the software. (One method is to simply copy files srvstart.exe and srvstart.dll to C:\WINDOWS\system32. Also copy logger.dll, and msvcrt.dll to C:\WINDOWS\system32. These latter two files are also available at http://www.nick.rozanski.com/software.htm)

To install WallWatcher as a service, create an init file for the WallWatcher service. In my install, I created a directory at C:\SRVstart. Start the notepad editor and put the following text in it:

  • [WallWatcher]
  • startup=C:\Program Files\WallWatcher\WallWatcher.exe
  • startup_dir=C:\Program Files\WallWatcher

Save this file as C:\SRVstart\srvstart.ini. (Of course, this assumes that WallWatcher has been installed in the folder C:/program Files\WallWatcher, modify if your installation folder is different.)

Open a command window, (StartRun, type in cmd and return) and type in the command

  • srvstart.exe install WallWatcher -c C:\SRVstart\srvstart.ini

Next start the Services manager by typing the command services.msc in either a command window or StartRun. There will now be a service entry for WallWatcher. Double click on the service entry for WallWatcher to edit its properties.

Change startup type to Automatic to allow the service to start when the computer starts up and click Apply. At this time, you can start the service by clicking the start button. Note under the Log On tab of the WallWatcher Properties window, do not check the box to allow it to interact with the desktop. This does not work if multiple users log on and off of the system. Instead, use Wall ReViewer to view the log file. To change WallWatcher settings and options, use the service manager to stop the WallWatcher service and then run WallWatcher as a normal application. Make whatever changes you desire, exit WallWatcher and use the Service manager to restart the service.

Important note for McAfee FireWall users: If you are using McAfee FireWall you need to have the FireWall start before the WallWatcher service. If not, the Firewall will block the desired packets since it will not recognize the program as running. To correct this, download and use SVC.exe (also from http://www.nick.rozanski.com/software.htm) to add a dependency for the WallWatcher service on the McAfee FireWall service. From a command window, cd to the directory where the svc.exe program is and type svc.exe and return. See the following screen shot for the details on how to do this. Note, return accepts the current or default value.

Originally posted and copyrighted at http://computertips.toups.info/. Used with permission.



by toups See Profile edited by Lanik See Profile
last modified: 2005-06-22 00:16:05

If your running Windows 2000 SP1/SP2, XP, or know you have MDAC (Microsoft Data Access Component) installed you can download Link Logger from: Here.

If your running Windows 98/98SE/ME, or know you don't have MDAC installed you can download Link Logger (has built in MDAC install) from: Here.

by Link Logger See Profile edited by Lanik See Profile
last modified: 2005-06-22 00:16:58

One work-in-progress you might want to check out if you are looking for a Linux-based Wireless Access Point configuration and monitor utility is described and available here

Update: Wireless Access Point Utilites for Unix are pretty stable and run under Linux, FreeBSD, NetBSD, AIX and probably other UNIX'es. Homepage: ap-utils.polesye.net

by lev See Profile edited by Lanik See Profile
last modified: 2005-06-22 00:17:19

This text assumes the reader will be using a computer (motherboard and BIOS) and NIC (network card) that are compatible with WoL technology and that the hardware is properly set up to do so. Some network cards must be placed into a special PCI slot on the motherboard in order work properly while others must be tethered to the motherboard by a special cable which plugs into a particular place on both the motherboard and the NIC. A general WoL FAQ can be located here. This text was written mainly to indicate how to forward the proper port through a Linksys router in order to utilize WoL technology through the router.

In order to use WoL (Wake on LAN, aka: RWU or remote wake up) to wake up a computer from over the Internet the appropriate port needs to be forwarded from the WAN side to the LAN side of the router. Since a computer that is not turned on doesn't have an IP address, the packet sent to wake the computer needs to be forwarded to all computers on the LAN side of the router in order to ensure it gets to the computer it is destined for. This "magic packet," which can be sent using software available from different sources, contains a special string designed to work with WoL as well as the MAC address of the network card in the computer which should wake up. Because the MAC address of the correct machine is included in the packet, only the machine that is supposed to wake up actually will.

To set up port forwarding in the router go here (default). The port that needs to be forwarded will vary depending on what software you're using to send the magic packet, but the normal port used for WoL is 9. UDP is the protocol that needs to be forwarded; it is not necessary to forward the TCP protocol. The IP address that the packet needs to be forwarded to will change depending on the network mask you are using on your LAN. The default network mask is 255.255.255.0. If you are using this mask, you should forward traffic destined to your WoL port to xxx.xxx.xxx.255. If you are using the default settings in the router, this address would probably be 192.168.1.255. The 255 in the address, using the default network mask, signifies that the router should forward any information sent to the indicated port to all computers on the LAN side. If you are using the router's default settings with a program that sends the "magic packet" to port 9, basically just forward all UDP traffic on port 9 to 192.168.1.255. If there is an option for external and internal ports, the same port number should be used for both external and internal.

WoL tool allows you to wake a computer remotely over the Internet through a browser. On this page they indicate UDP port 9 is what the tool uses, but as of this writing the magic packet is actually sent through UDP port 32767. So, if you're using this tool be sure to forward port 32767 through the router.

While it is possible to locate software that will send WoL "magic packets" via a quick search in your favorite search engine, a couple of sites offering such software are:

Depicus (also provides info on WoL)
AMD (also provides info on WoL)

Feedback received on this FAQ entry:
  • DOM-inspector not working anymore

    2013-11-12 01:02:48

  • In Firefox you can use the DOM-inspector to change the value from the number you put to 255. Google it!

    2011-06-26 18:04:40

  • Just an FYI guys that if you setup your linksys router with a different subnet mask (ie: 255.255.255.128), then you can setup a port forwarding rule that allows broadcasting to that subnet - it just doesn't work with a subnet mask of 255.255.255.0

    2010-12-09 18:56:01

  • Excellent information. For those not using Linksys routers (such as me with a Connectgear WR460N), the $^%$#$ router will not allow port-forwarding to a broadcast address (router designers provide an error message saying "must specify an address between .1 to .254") on LAN targets. Mother of God. I think I can do this in Linux using iptables however. Greg

    2010-07-17 12:05:32

  • Current Linksys routers do not support forwarding traffic to xxx.xxx.xxx.255. WOL over WAN/internet is no longer feasible with Linksys routers.

    2010-01-09 03:36:51

  • My older WRT54G doesn't allow you to specify .255 for the forward address...

    2009-07-02 22:20:00

  • Super! thanks

    2009-01-26 08:02:15

  • Thank you for this page. Although I had this in mind that power off computer does not have IP address, still I was mentioning it's IP at router that I statically assigned to my pc for remote access and administration purpose. Giving in broadcast address of subnet, as you have mentioned, really makes sense. I will try and hopefully it will work.

    2008-02-15 10:54:46



by Gork See Profile edited by Lanik See Profile
last modified: 2005-06-22 00:17:33