Ore on Intel Pro/1000

[Bjoern Doebel]

Hello,

> We did not manage to arping ore_test_arping this time, but complete logs    
> are attached.

humm, ... please update your version of ORe from our public CVS and try 
to run some minimal setup with only the arping client and w/o L4Linux. 
See my example below and report us your experiences.

My menu.lst looks like this:

title ORe arping test
kernel (nd)/tftpboot/doebel/l4v2/bootstrap -sigma0 -roottask -serial 
-comport=2
modaddr 0x02000000
module (nd)/tftpboot/doebel/kernel/fiasco -nowait -nokdb -comport 2 
-tbuf_entries=32768 -serial_esc -esc
module (nd)/tftpboot/doebel/l4v2/sigma0
module (nd)/tftpboot/doebel/l4v2/roottask
module (nd)/tftpboot/doebel/l4v2/names --events
module (nd)/tftpboot/doebel/l4v2/log
module (nd)/tftpboot/doebel/l4v2/dm_phys --events
module (nd)/tftpboot/doebel/l4v2/l4io --noirq --nolist
module (nd)/tftpboot/doebel/l4v2/ore --events
module (nd)/tftpboot/doebel/l4v2/events
module (nd)/tftpboot/doebel/l4v2/ore_test_arping

With this setup I get a virtual MAC address (note that I have an 
Eepro100 NIC):

names   | Starting thread listening for `exit' events
io      | do_args(): Disabling internal IRQ handling.
io      | do_args(): Disabling listing of PCI devices.
arping  | main(): Hello from the ORe arping shared memory client
arping  | main(): string ipc receive
arping  | main(): sending with string ipc
arping  | l4ore_open(): called
io      | PCI: Using configuration type 1
io      | PCI: Probing PCI hardware
io      | PCI: Probing PCI hardware (bus 00)
io      | PCI: Via IRQ fixup
io      | Applying VIA southbridge workaround.
arping  | ore_initialize(): dsi_init: 0
ore     | l4dde_mm_init(): Using ...
ore     |   8192 kB at 0x00180000 (vmem)
ore     |   8192 kB in 1 regions (kmem)
ore     | eepro100.c:v1.09j-t 9/29/99 Donald Becker 
http://www.scyld.com/networ
ore     : k/eepro100.html
ore     | eepro100.c: $Revision: 1.2 $ 2000/11/17 Modified by Andrey V. 
Savochk
ore     : in <saw at saw.sw.com.sg> and others
ore     | eth0: Intel Corp. 82557/8/9 [Ethernet Pro 100], 
00:02:B3:C1:E9:93, IR
ore     : Q 10.
ore     |   Board assembly 751767-004, Physical connectors present: RJ45
ore     |   Primary interface chip i82555 PHY #1.
ore     |     Secondary interface chip i82555.
ore     |   General self-test: passed.
ore     |   Serial sub-system self-test: passed.
ore     |   Internal registers self-test: passed.
ore     |   ROM checksum self-test: passed (0x3258698e).
ore     | device lo entered promiscuous mode
ore     | device eth0 entered promiscuous mode
ore     | main(): Initialized 2 network devices.
ore     | main(): Registering at names...
ore     | main(): Ready for service.
arping  | ore_lookup_server(): ORe = 9.02
arping  | l4ore_open(): descriptor: 0
arping  | l4ore_open(): sending via string ipc
arping  | l4ore_open(): receiving via string IPC
arping  | ore_do_open(): called
arping  | ore_do_open(): opened. worker = 9.08
arping  | main(): opened eth0: 0 for 04:EA:F3:02:50:13
arping  | main(): handle = 0
arping  | main(): got send area: 0x00200008


Now I can arping this MAC from my workstation:

$>arping 04:EA:F3:02:50:13 -c 5
ARPING 04:EA:F3:02:50:13
80 bytes from 255.255.255.255 (04:ea:f3:02:50:13): icmp_seq=0 
time=503.063 usec
80 bytes from 255.255.255.255 (04:ea:f3:02:50:13): icmp_seq=0 
time=128.984 usec
80 bytes from 255.255.255.255 (04:ea:f3:02:50:13): icmp_seq=0 
time=133.991 usec
80 bytes from 255.255.255.255 (04:ea:f3:02:50:13): icmp_seq=0 
time=157.118 usec
80 bytes from 255.255.255.255 (04:ea:f3:02:50:13): icmp_seq=0 
time=128.984 usec

--- 04:EA:F3:02:50:13 statistics ---
5 packets transmitted, 5 packets received,   0% unanswered


Bjoern