I've been thinking about what kind of project I'd like to do for college next year, and I was thinking I'd go with something like a small Ethernet device. Maybe something like a "Network Mapper" which could be plugged into an Ethernet switch and would print out on an LCD screen all the IP addresses that are being used on the network. In order to do this, the only functionality I'd really need is the ability to send and receive ARP packets. (Of course I'd have to get the network address and netmask from somewhere, but I could perhaps get this by sniffing the network, or by simply having the user specify it). I've been glancing at different devices on the internet, from the $1 devices all the way up to $100. Here's one of the cheaper, simpler ones: http://tuxgraphics.org/electronics/200606/article06061.shtml And then there's big monster devices which are of course more expensive: http://www.rabbit.com/products/rcm4200/ It looks like the latter device would be doing a lot of the work for me, I wouldn't be shaping every byte transmitted as I would be with the former device. Have many of you here got experience making Ethernet devices? Any suggestions as to what I should go with? I quite like the idea of the former device which is pretty much just a micrcontroller chip in a DIP package, but then again I'm not entirely adverse to the idea of using something more advanced, depending on how fun and interesting the project and end-product will be. I realise I could probably make a Network Mapper in five minutes by using devices that do all the work for me, so I'm inclined to go more with the simpler devices that make you shape your own frames. Plus I'd be magnificient if the end product was the size of a matchbox :D
Ethernet microcontroller to create small network host
Started by ●March 9, 2008
Reply by ●March 9, 20082008-03-09
On 2008-03-09, Tom�s � h�ilidhe <toe@lavabit.com> wrote:> > I realise I could probably make a Network Mapper in five minutes by > using devices that do all the work for me, so I'm inclined to go more > with the simpler devices that make you shape your own frames. Plus I'd > be magnificient if the end product was the size of a matchbox :DMany of the microcontroller manufacturers have application notes or similar describing the connection of their products to ethernet and TCP/IP, both in terms of hardware and software, so you have usually have a simple IP stack ready made for you at least as a template. I recall seeing such notes from Microchip for PICs and TI for MSP430s, doubtless they exist for other contollers. Chips with a built in ethernet interface will probably have an example implementation of at least the hardware side in the chip's datasheet. It is probably something that needs making more concrete before you can progress much further. Have a look at the various manufacturer's web sites and other online resources for examples of ethernet interfacing. Once you have found an example that appeals to you, or you have selected your controller then you have a starting point that will tell you what you need to develop yourself for the task in hand. Most of the notes I've seen relate to creating web servers so obviously some of it won't apply, but the interfacing essentials and a good proportion of the code will be useful with only minor modifications. There are also issues relating to the feasibility of packet sniffing switched networks that you need to be aware of. I'll leave it to you to do your own research there, since it isn't really my field of expertise, but I'll point it out now so it doesn't come as a nasty surprise later on in your project. -- Andrew Smallshaw andrews@sdf.lonestar.org
Reply by ●March 9, 20082008-03-09
In comp.arch.embedded, Tom�s � h�ilidhe <toe@lavabit.com> wrote:> > I've been thinking about what kind of project I'd like to do for > college next year, and I was thinking I'd go with something like a > small Ethernet device. Maybe something like a "Network Mapper" which > could be plugged into an Ethernet switch and would print out on an LCD > screen all the IP addresses that are being used on the network. > > In order to do this, the only functionality I'd really need is the > ability to send and receive ARP packets. (Of course I'd have to get > the network address and netmask from somewhere, but I could perhaps > get this by sniffing the network, or by simply having the user specify > it).If you 'only' want to sniff what packets come by, you don't even need to have an address yourself. If you are new to ethernet, I suggest you start by reading Analog devices EE-269 and the RFCs mentioned in that document, I found that document very usefull. And as Andrew replied, understand how switched networks (which most ethernet networks are today) operate, otherwise you will be in for that very unpleasant surprise. -- Stef (remove caps, dashes and .invalid from e-mail address to reply by mail) Read the JOVE BOOK
Reply by ●March 9, 20082008-03-09
"Tom�s � h�ilidhe" <toe@lavabit.com> wrote in message news:1c2f2ca1-3f32-4f14-9001-3b53c1664af4@y77g2000hsy.googlegroups.com...> > I've been thinking about what kind of project I'd like to do for > college next year, and I was thinking I'd go with something like a > small Ethernet device. Maybe something like a "Network Mapper" which > could be plugged into an Ethernet switch and would print out on an LCD > screen all the IP addresses that are being used on the network. > > In order to do this, the only functionality I'd really need is the > ability to send and receive ARP packets. (Of course I'd have to get > the network address and netmask from somewhere, but I could perhaps > get this by sniffing the network, or by simply having the user specify > it). > > I've been glancing at different devices on the internet, from the $1 > devices all the way up to $100. Here's one of the cheaper, simpler > ones: > > http://tuxgraphics.org/electronics/200606/article06061.shtml > > And then there's big monster devices which are of course more > expensive: > > http://www.rabbit.com/products/rcm4200/ > > It looks like the latter device would be doing a lot of the work for > me, I wouldn't be shaping every byte transmitted as I would be with > the former device. > > Have many of you here got experience making Ethernet devices? Any > suggestions as to what I should go with? I quite like the idea of the > former device which is pretty much just a micrcontroller chip in a DIP > package, but then again I'm not entirely adverse to the idea of using > something more advanced, depending on how fun and interesting the > project and end-product will be. > > I realise I could probably make a Network Mapper in five minutes by > using devices that do all the work for me, so I'm inclined to go more > with the simpler devices that make you shape your own frames. Plus I'd > be magnificient if the end product was the size of a matchbox :D > > >Hi Tom�s, Please take a look at The ET-WEB51 with free uIP TCP/IP stack and webserver: http://members.iinet.net.au/~vanluynm/Embedded_8051_TCPIP_Webserver.php It has an onboard LCD port for an HD44780 controlled LCD, and now comes with all the free ARP code written in C that you could ever need! It may be a suitable platform for the project you've described. Regards, Murray R. Van Luyn. -- 32�02'14.23"S 115�53'21.30"E http://www.review-a-gadget.com/ http://www.reviewagadget.com/ http://members.iinet.net.au/~vanluynm/ <- FREE 8052 Code
Reply by ●March 9, 20082008-03-09
On Mar 9, 9:03=A0pm, Stef <stef...@yahooI-N-V-A-L-I-D.com.invalid> wrote:> If you 'only' want to sniff what packets come by, you don't even need > to have an address yourself. If you are new to ethernet, I suggest you > start by reading Analog devices EE-269 and the RFCs mentioned in that > document, I found that document very usefull.I want to do more than sniff, I want to send an ARP request to every possible IP address on the subnet.> And as =A0Andrew replied, understand how switched networks (which most > ethernet networks are today) operate, otherwise you will be in for > that very unpleasant surprise.Thanks for the suggestion, I already understand switch networks.
Reply by ●March 10, 20082008-03-10
Take a look at www.netburner.com We have dev kits starting at 99.00 that include TCP/IP stack and full C/C++. Paul (CTO NetBurner.)
Reply by ●March 10, 20082008-03-10
pbreed@netburner.com wrote:> Take a look at > www.netburner.com > > We have dev kits starting at 99.00 that include TCP/IP stack and full C/C++.Paul, And a full C/C++ what ?? source, compiler, library ???> > > Paul > (CTO NetBurner.) >
Reply by ●March 11, 20082008-03-11
On Mon, 10 Mar 2008 15:57:04 -0700, donald <Donald@dontdoithere.com> wrote:>pbreed@netburner.com wrote: >> Take a look at >> www.netburner.com >> >> We have dev kits starting at 99.00 that include TCP/IP stack and full C/C++.Full eclipse development tools. Full RTOS and Libary Full source Code Full set of examples. Full FAT 32 files system. (Source is extra for this one) All described on the web site... Start here: IDE: http://www.netburner.com/embedded_eclipse.html Libraries... http://www.netburner.com/products/netburner_software.html Paul> >Paul, > >And a full C/C++ what ?? > >source, compiler, library ??? >> >> >> Paul >> (CTO NetBurner.) >>
