Thank you for you reply,

I forgot to load the rtcfg module, i solved that problem. But i still can't 
sniff the traffic with wireshark. I did load the rtcap right after the driver. 
I can see the RTcap dmesg and also the rtping is responding slowly (i assume 
RTcap adds some delay). But i still cant see the the rteth0 (or its mirror as 
written in readme) with wireshark. If i understand this correctly after i load 
the the RTcap module, the $ifconfig should show the mirror of the rteth0 
interface? A pasted the module load order, tmesg and ifconfig reply below. 

Regards,
Klemen


sudo mknod /dev/rtnet c 10 240

# unbind the NIC from the driver
echo -n '0000:05:00.0' | sudo tee -a /sys/bus/pci/drivers/r8169/unbind

sudo insmod /usr/realtime-2.6.32-122-rtai/modules/rtai_hal.ko
sudo insmod /usr/realtime-2.6.32-122-rtai/modules/rtai_lxrt.ko
sudo insmod
 /usr/realtime-2.6.32-122-rtai/modules/rtai_sem.ko
sudo insmod /usr/realtime-2.6.32-122-rtai/modules/rtai_rtdm.ko

sudo insmod /usr/local/rtnet/modules/rtnet.ko #needed for all rtnet modules
sudo insmod /usr/local/rtnet/modules/rt_loopback.ko
sudo insmod /usr/local/rtnet/modules/rt_r8169.ko
sudo insmod /usr/local/rtnet/modules/rtcap.ko #needed for sneefer

sudo insmod /usr/local/rtnet/modules/rtpacket.ko
sudo insmod /usr/local/rtnet/modules/rtipv4.ko
sudo insmod /usr/local/rtnet/modules/rtcfg.ko
sudo insmod /usr/local/rtnet/modules/rtudp.ko

sudo /usr/local/rtnet/sbin/rtifconfig rtlo up 127.0.0.1
sudo /usr/local/rtnet/sbin/rtifconfig rteth0 up 142.1.1.2 netmask 255.255.255.0
sudo /usr/local/rtnet/sbin/rtroute solicit 142.1.1.3 dev rteth0 # Add host 
route using ARP



[   68.849874] r8169 0000:05:00.0: PCI INT A disabled
[   68.894566] I-pipe: Domain RTAI registered.
[   68.894584] RTAI[hal]: <3.8.1> mounted over IPIPE-NOTHREADS 2.6-03.
[   68.894591] RTAI[hal]: compiled with gcc version 4.4.3 (Ubuntu 
4.4.3-4ubuntu5) .
[   68.894712] RTAI[hal]: mounted (IPIPE-NOTHREADS, IMMEDIATE (INTERNAL IRQs 
DISPATCHED), ISOL_CPUS_MASK: 0).
[   68.894719] PIPELINE layers:
[   68.894726] f9a6fe20 9ac15d93 RTAI 200
[   68.894733] c085cb20 0 Linux 100
[   68.960925] RTAI[malloc]: global heap size = 2097152 bytes, <BSD>.
[   68.962170] RTAI[sched]: IMMEDIATE, MP, USER/KERNEL SPACE: <without RTAI OWN 
KTASKs>, kstacks pool size = 524288
 bytes.
[   68.962187] RTAI[sched]: hard timer type/freq = APIC/12500438(Hz); default 
timing: periodic; linear timed lists.
[   68.962198] RTAI[sched]: Linux timer freq = 250 (Hz), TimeBase freq = 
1800098000 hz.
[   68.962207] RTAI[sched]: timer setup = 999 ns, resched latency = 2943 ns.
[   68.962367] RTAI[usi]: enabled.
[   69.047896] RTDM started.
[   69.089874] 
[   69.089878] *** RTnet 0.9.13 - built on Mar 12 2013 19:32:58 ***
[   69.089881] 
[   69.089885] RTnet: initialising real-time networking
[   69.115100] initializing loopback...
[   69.115125] RTnet: registered rtlo
[   69.153813] Initializing rt_r8169 driver
[   69.153913] rt_r8169 0000:05:00.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[   69.154933] rt_r8169: PCI device 0000:05:00.0: unknown chip
 version, assuming RTL-8169
[   69.155642] RTnet: registered rteth0
[   69.155654] rteth0: Identified chip type is 'RTL8169'.
[   69.155666] rteth0: rt_r8169 RTnet Gigabit Ethernet driver 2.2-04 at 0x1000, 
64:70:02:12:fa:f9, IRQ 20
[   69.163630] rteth0: Auto-negotiation Enabled.
[   72.184219] rteth0: 1000Mbps Full-duplex operation.
[   72.208396] RTcap: real-time capturing interface
[   72.304630] RTcfg: init real-time configuration distribution protocol



$
 ifconfig
eth0      Link encap:Ethernet  HWaddr e8:40:f2:06:53:89  
          inet addr:192.168.1.13  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::ea40:f2ff:fe06:5389/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1809 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1718 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1766355 (1.7 MB)  TX bytes:268548 (268.5 KB)
          Interrupt:28
 Base address:0xe000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:42 errors:0 dropped:0 overruns:0 frame:0
          TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:4302 (4.3 KB)  TX bytes:4302 (4.3 KB)

$ sudo ./sbin/rtifconfig
rtlo      Medium: Local Loopback
          IP address: 127.0.0.1  
          UP LOOPBACK RUNNING  MTU: 1500

rteth0    Medium: Ethernet  Hardware address: 64:70:02:12:FA:F9
          IP address: 142.1.1.2  Broadcast address: 142.1.1.255
          UP BROADCAST RUNNING  MTU:
 1500
          RX packets:5 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 
          RX bytes:1710 (1.6 Kb)  TX bytes:120 (120.0 b)






________________________________
 From: Jan Kiszka <jan.kis...@web.de>
To: Klemen Dovrtel <klemen_dovr...@yahoo.com> 
Cc: "rtnet-users@lists.sourceforge.net" <rtnet-users@lists.sourceforge.net> 
Sent: Monday, May 27, 2013 7:33 AM
Subject: Re: rtnet beginner troubles
 

On 2013-05-25 11:18, Klemen Dovrtel wrote:
> I set up two computers with rtnet and configure the network cards so that i 
> can successfully rtping.
> 
> Then I tried sniff for data with wireshark, but when i run it, the wireshark 
> does not detect the rteth0 network card. I have the rtcap module 
> installed/loaded.

Does your RT-NIC work (rtifconfig etc.)? Then, rtcap has to be loaded
after that driver but before starting its interface via rtifconfig. The
rtnet start script implicitly documents the steps. And then there is
README.rtcap, of course.

> 
> 
> I also tried to test some Server Command. I tried to "rtcfg rteth0 
> add/server/whatever" but i get an error reply: "ioctl: Inappropriate ioctl 
> for device".

insmod rtcfg? Again, the startup script can serve as a guide - or may
just work for you.

Jan
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
_______________________________________________
RTnet-users mailing list
RTnet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rtnet-users

Reply via email to