bind ICMP to specific IP address
From: Stuart Kendrick (skendric_at_fhcrc.org)
Date: 11/30/03
- Next message: Oliver Meike: "Error message at startup: eth0 (DHCP) failed"
- Previous message: dorg_at_binet.is: "Re: Wireless under Redhat 9.0 and Slackware 9.0"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 30 Nov 2003 10:11:22 -0800
hi,
i'd like to run a number of ICMP intensive scripts from a single box.
in my experience, this is problematic ... ICMP doesn't support ports
the way TCP and UDP do, so the IP stack doesn't know to which process
to return the ICMP Echo Reply ... so process A can receive a response
to a ping which process B emitted ... neither process enjoys this ...
nor does the operator.
typically, /usr/sbin/ping supports the "-I" parameter, which allows it
to bind to a specified IP address ... that way, i can configure the box
with multiple IP addresses, bind each process' /usr/sbin/ping instance
to a different IP address ... and avoid stomping on myself.
but fping doesn't support the "-I" parameter. and i really like a number
of fping's features.
argh.
ok, so i can rewrite fping in Perl ... the Net::Ping module ships with
example code. and Net::Ping supports a 'bind' parameter, which allows
lets me specify the source IP address for the ICMP packet. but then,
i have to run my scripts as root or at least as setuid root ... neither
of which thrills me.
Net::Ping::External doesn't require root access to run, as it uses the
OS's ping binary. But ... it doesn't yet support binding to different
IP addresses (presumably, the "-I" parameter varies enough between OSes
that this is hard to support).
i think i'm stuck. i think i need more hardware -- one box per
ping-intensive app.
does anyone know of way around this?
--sk
Stuart Kendrick
FHCRC
- Next message: Oliver Meike: "Error message at startup: eth0 (DHCP) failed"
- Previous message: dorg_at_binet.is: "Re: Wireless under Redhat 9.0 and Slackware 9.0"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
