Re: [misterhouse-users] Monitoring RT314 Router with monitor_router.pl

[paul <pl...@ro...>]

oops! ... forget the url

http://www.wallwatcher.com/

Paul
>Date: Mon, 30 Dec 2002 15:36:27 -0500
>To: mis...@li...
>From: paul <pl...@ro...>
>Subject: Re: [misterhouse-users] Monitoring RT314 Router with 
>monitor_router.pl
>
>
>
>Hi,
>I am using a freeware called WallWatcher to monitor Linksys BEF Series router
>from my desktop. It shows you all the traffic (in/out) that goes through 
>the router
>and can alert you on incoming traffic. It can log all or filter traffic.
>
>Couple things to remember:
>- Enable Access log in your Linksys.
>- Download both the application and library file and follow the instruction.
>- Only one application can use port 162 at one time... therefore  disable 
>all applications
>    that is using port 162 (ie monitor_router.pl if you enable it)
>
>It help me figure out that people were bouncing off my pc when I open a 
>port for an application
>and cause my internet connection speed to be slow.
>
>Not sure if it will work with NetGear routers.
>
>Paul
>
>>I'm on NT 4.0. I'll try some of the other apps around and see if they can 
>>connect.
>>Maybe I can reverse-engineer the problem.
>>thanks,
>>Kieran
>>
>>Bruce Winter wrote:
>>
>> > > Bruce Winter wrote:
>> > > > Does enabling this print show anything?
>> > > > if (my $packet = said $router) {
>> > > > #   print "db router packet: $packet\n";
>> > >
>> > > Bruce,
>> > > No, it doesn't. I saw the following in the monitor_router.pl script:
>> > >     $router = new Socket_Item(undef, undef, 'server_router');
>> > >     $router_loops++;
>> > >     if (my $packet = said $router) {
>> > >       print "db router packet: $packet\n";
>> > >
>> > > Does $router need to be initialized differently than it is done here 
>> with
>> > > 'server_router' ? Also, I don't see how "if (my $packet = said
>> > > $router)" is invoked.
>> >
>> > No, those server_router pamrs should be enough.   Here is what I have for
>> > the linksys:
>> >
>> > server_router_port=162
>> > server_router_protocol=udp
>> > server_router_datatype=raw
>> >
>> > There are other router monitor programs out there ... maybe you could try
>> > one of those?
>> >
>> > The only other thought is I made the following change to get the xAP code
>> > working with a specific hub (I'll post seperatly when I get that working
>> > well), so maybe somehow it effects you also?    In bin/mh, add the 2nd 
>> line
>> > here:
>> >
>> >     use IO::Socket;
>> >     use IO::Socket::INET;       # Gives us the INADDR constants, used in
>> > xAP.pm
>> >
>> > The later, about line 4163 from this:
>> >         else {
>> >             $Socket_Ports{$port_name}{sock} = new
>> > IO::Socket::INET->new(LocalPort => $port, Proto => 'udp') or
>> >                 die "Couldn't start a udp server on $port_name $port: 
>> $@\n";
>> >         }
>> >         $Socket_Ports{$port_name}{socka} = 
>> $Socket_Ports{$port_name}{sock};
>> > # UDP ports are always "active"
>> >
>> > to this:
>> >
>> >         else {
>> >             $Socket_Ports{$port_name}{sock} =
>> >                 new IO::Socket::INET->new(LocalPort => $port, Proto =>
>> > 'udp',
>> >                                           LocalAddr =>
>> > inet_ntoa(INADDR_ANY), Broadcast => 1) or
>> >                 die "Couldn't start a udp server on $port_name $port: 
>> $@\n";
>> >         }
>> >         $Socket_Ports{$port_name}{socka} = 
>> $Socket_Ports{$port_name}{sock};
>> > # UDP ports are always "active"
>> >
>> > I doubt the above will matter, though, since I had the netgear working on
>> > windows before.  Are you on windows or linux?
>> >
>> > Bruce