> Hello everyone,
>
> while searching for the reason of some strange behaviour of RTnet when
> pinging a realtime box, I discovered a small but severe bug in the IP
> input chain. Under certain conditions the input route may not have been
> correctly resolved and an old value may have been mistakenly re-used.
>
> It is recommended to apply the attached patch to ip_input.c or update to
> the latest CVS version. We will try to release a new version next week,
> bundeling all the recent fixes.
>
> Jan
>
>
> PS: Arno, could you verify if this fixes all your problems? Thanks.
>
Hi Jan,
with your patch PING is working fine,
but TELNET is still not working.
after 14 TCP packets without reply ifconfig shows this:
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:508 (508.0 iB) TX bytes:508 (508.0 iB)
rtproxy Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:192.168.169.135 Bcast:192.168.169.255
Mask:255.255.255.0
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:14 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1120 (1.0 kiB) TX bytes:0 (0.0 iB)
seems to be a problem of rtnetproxy.
Thanks for your help,
Arno
--
+++ NEU bei GMX und erstmalig in Deutschland: T�V-gepr�fter Virenschutz +++
100% Virenerkennung nach Wildlist. Infos: http://www.gmx.net/virenschutz
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
RTnet-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/rtnet-users
