A Dijous 15 Novembre 2007, Karl Reichert va escriure: > > I guess he is talking about the rt_e1000 driver (based on e1000 driver).
yes ... > > > > I compared the e1000 driver in SVN trunk with the one in 0.9.9. > > > > As the syslog show, I always have worked with 0.9.10 (trunk), :-) > > well that what I have seen ... > > Are you sure? Because the SVN version of RTnet has this rt_e1000 patch > already applied and it seems like you don't, so maybe you are not running > rtnet SVN version. Better try a diff to be sure. yes I'm sure. I was working all the day yesterday with the rtnet 0.9.10 (trunk). I have looked the e1000/e1000_main.c to ensure that the patch was applied. However I wouldn't lost in this know. Yesterday my box was doing strange things. The route table behaviour is very disconcerting. [....] > > You don't have to understand RTcap. Just enable it at rtnet configuration > (make menuconfig) and load its module, enable its interface and let > wireshark/tcpdump capture the traffic. The only thing you have to do then > is to check the frames (which are sent, are they corrupt ... ) ok, rtcap compiled ... .... driver loaded; module rtcap loaded and rteth0 enable sbin/rtifconfig rteth0 up 10.0.0.1 promisc netmask 255.255.255.0 but wireshark doesn't see it. I'm using wireshark 0.99.4, from debian etch > ... and last but not least ... send me one of those tickets ;) are you a nice girl with blond hair, blue eyes and intelligent? ;-) ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ RTnet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rtnet-users
