Note that there are some explanatory texts on larger screens.

plurals
  1. POloopback network kernel module not working
    primarykey
    data
    text
    <p>I am new to kernel module development. I am trying to development a pseudo network driver operates in loopback mode without any actual device. My goal is to use the following setup:</p> <pre><code>iperf -s -u.........iperf -c 192.168.1.1 -p 5001 -u </code></pre> <blockquote> <p>======..............===========</p> <p>|...if0....|.............|........if1.........|</p> <p>======..............===========</p> <pre><code> | | /|\ \|/ | | --------------- </code></pre> </blockquote> <p>I have registered two interface from the driver. Then I modified the UDP packet received from if1 so that it appeared as it was received at if0. But it never reaches to the iperf server application listening on all udp if's udp port. But whenever I sniffed the packet via wireshark on if0, it seems that the packet is being received at if0. But for some reason it is not going through the network stack.</p> <p>any clues? Both the ip checksum &amp; udp checksum have recalculated and verified (using wireshark). I am using netif_rx to indicate packet to the other interface handle (if0 handle).</p> <p>I have only used 5 function ptr callbacks {open, close, xmit_start, get_stats &amp; config} for network operations. Also checksum is set to UNNECESSARY. IF flag has been set to indicate NO_ARP.</p> <h1>EDIT: IP ADDR OUTPUT</h1> <blockquote> <p>eth1: mtu 1500 qdisc</p> <p>pfifo_fast state UP qlen 1000 link/ether 00:e0:ff:00:00:e0 brd</p> <p>ff:ff:ff:ff:ff:ff inet 192.168.1.1/24 brd 192.168.1.255 scope globa eth1 valid_lft</p> <p>forever preferred_lft forever 4: </p> <p>eth2: mtu 1500 qdisc pfifo_fast</p> <p>state UP qlen 1000 link/ether 00:e0:ff:40:00:e0 brd ff:ff:ff:ff:ff:ff</p> <p>inet 192.168.2.1/24 brd 192.168.2.255 scope global eth2 valid_lft</p> <p>forever preferred_lft forever</p> </blockquote>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload