[openbeosnetteam] testread / Meeting?

  • From: "David Reid" <dreid@xxxxxxxxxxxx>
  • To: "OpenBeOS Network Team" <openbeosnetteam@xxxxxxxxxxxxx>
  • Date: Sat, 9 Feb 2002 13:08:44 -0000

Well, the fact that we're now able to read from the network card seems to
have not produced the reaction I might have expected


Also, so far only Axel has added his details to CVS, so I guess no-one else
has write access or no-one else is planning on contributing?

Still, we now have a very basic ethernet and ipv4 modules that produce the
following output...

$ ./testread
allocated a 4096 byte block starting at 0xa0000000
allocated a 4096 byte block starting at 0xa0001000
Network Card Read Test
======================

Have you set the device path to point at your card?
If not you probably won't see anything!

Opened the device.
MAC address 00:a0:cc:d0:22:dc
Unable to set promiscuous. General OS error
Ethernet packet from 00:c0:02:56:56:24 to ff:ff:ff:ff:ff:ff: BCAST proto
IPv4
IPv4 Header :
            : version       : 4
            : header length : 4
            : tos           : 0
            : total length  : 229
            : id            : 50964
            : flags         : 0x00
            : frag offset   : 0
            : ttl           : 30
            : protocol      : UDP
            : src address   : 192.168.0.12
            : dst address   : 192.168.0.255

Ethernet packet from 00:50:da:37:37:10 to ff:ff:ff:ff:ff:ff: BCAST proto ARP

Ethernet packet from 00:c0:02:56:56:24 to ff:ff:ff:ff:ff:ff: BCAST proto
IPv4
IPv4 Header :
            : version       : 4
            : header length : 4
            : tos           : 0
            : total length  : 229
            : id            : 50979
            : flags         : 0x00
            : frag offset   : 0
            : ttl           : 30
            : protocol      : UDP
            : src address   : 192.168.0.12
            : dst address   : 192.168.0.255


Yes, this is from testread (as found in CVS).  Once we have an arp module
added (next on my list) it'll be time to start thinking about how we link
all these to a central "net_server" module.

As for the net_server module, I'm guessing we need to scan the /dev/net
directory and try to open/attach to all the drivers we find?  That'll bring
the issue of ifnet structures and so onto into tehlight as well, so plenty
to talk about.

I've added openbeosnetkit to irc.openprojects.net and have it permanently
available now (ChanServ is guarding it for us :)) so are we still planning
on meeting there for a chat tomorrow afternoon?

david


Other related posts: