Dear Michael,

    Thanks a lot. In fact, I have already done so and it works fine since that. 
Also, thanks Tobi's directions.

Best Regards,
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mars Chih-hua Wei
Engineer/Network Application Planning Group/Network Group
New Century InfoComm Tech Co., Ltd.

-----Original Message-----
From: Michael Markstaller [mailto:[EMAIL PROTECTED]
Sent: Saturday, April 26, 2003 11:53 PM
To: [EMAIL PROTECTED]
Subject: [smokeping-users] Re: Problem with IOSPing


> Dear Tobi,
>    I wonder if it is possible to add a variable for source IP for the 
> advanced Ping in IOSPing. If it's possible, what could I do? Thanks a lot.
I've just patched the IOSPing.pm to be able to specify the source-interface 
(you cannot specify the IP in the IOS ping command, at least not the rsh way).
Maybe this helps, the changed IOSPing.pm is attached. You just have to insert 
"iossrcif" i.e.:
--- cut ---
++++ PROBE_CONF
ioshost = router
iosuser = smoke
iossrcif = FastEthernet0/0
--- cut ---

May be the author (Paul J Murphy <[EMAIL PROTECTED]>) wants to integrate this 
into the IOSPing-probe sometime as I think it's quite vital to specify the 
source.. 
BTW, I'm (still) thinking of the best solution creating an SAA/RTR probe using 
SNMP which would be more convinient to use without creating the "rsh" 
security-hole.. Also there's a Cisco ping-mib which would also be smoother. But 
besides the "rsh-issue" I really like the idea of IOSPringProbe..

regards

Michael

-- Attached file removed by Ecartis and put at URL below --
-- Type: application/octet-stream
-- Desc: IOSPing.pm
-- Size: 6k (6434 bytes)
-- URL : http://www.ee.ethz.ch/~slist/p/02-IOSPing.pm


--
Unsubscribe mailto:[EMAIL PROTECTED]
Help        mailto:[EMAIL PROTECTED]
Archive     http://www.ee.ethz.ch/~slist/smokeping-users
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi

--
Unsubscribe mailto:[EMAIL PROTECTED]
Help        mailto:[EMAIL PROTECTED]
Archive     http://www.ee.ethz.ch/~slist/smokeping-users
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi

Reply via email to