(
Jump to the original submission)
Mon 14 Oct 2013 09:46:27 AM UTC, comment #6:
OK. TCP and UDP perform in the same way.
Anyway, rtig crashes when the IP format is not respected. See rtig -l 127.0.
|
Fri 27 Sep 2013 01:05:36 PM UTC, comment #5:
Just checked-in the UDP modification right now.
Judicael could you test it?
|
Fri 27 Sep 2013 07:58:22 AM UTC, comment #4:
Hi Judicael,
You are right there is a oldish related bug.
bugs #23360
|
Wed 11 Sep 2013 05:12:15 PM UTC, comment #3:
It seems to be OK.
With my firewall, I see that rtig listens on all TCP interfaces without the -l option and with the option only on the specified interface.
I have a doubt about UDP. Why does it always listen on the IP-address of my machine even if I specify -l 127.0.0.1 ? I don't remember why we only decide to focus on TCP.
|
Wed 04 Sep 2013 07:57:49 AM UTC, comment #2:
The -l option has been added to rtig command line.
(in CVS HEAD)
Please try and tell me if it fits the need.
|
Mon 06 May 2013 05:40:03 PM UTC, comment #1:
Yes we could use a command line option for RTIG
like
rtig -l w.x.y.z
then rtig would listen on this @IP.
and/or use CERTI_HOST environment var which is currently
used by RTIA in order to locate the @IP of the machine
on which RTIG is running.
What do you think?
|
Thu 22 Mar 2012 06:05:13 PM UTC, original submission:
RTIG is listening on all network interfaces (TCP only) which makes some firewall scream.
Could you implement something to indicate a specific interface to listen on ?
|
(Note: upload size limit is set to 16384 kB, after insertion of the required
escape characters.)
Attach File(s):
Comment:
No files currently attached
Depends on the following items
Digest:
bug dependencies.
Items that depend on this one: None found
Follow 7 latest changes.