What NIC driver to compile in kernel

This'll be my first post in the *BSD forums.

Anyways my NIC is NE2000 (RealTek 8029) and I've been looking in the kernal conf file for the driver for it but haven't found one specifically for my NIC.
There are a few similair one's but none for mine.

The NIC works with the generic kernal but now that I want to compile my own I don't know which driver to compile in.
I assume I'm gonna have to use one of the similair drivers or a genric one but I'm wandering if anyone can give me a tip on which one to try first. It's 4am and definatly bed time but I'm hoping someone can give me a good starting point for tommorow.

If it matters I'm running 5.1-release and have just cvsup'ed the source to RELENG_5_1 and thought compiling the kernel was the first thing to do (according to some of freebsd's posts and I can see he gave good advice) before buildworld (I have no clue what that is but I'll deal with that later).

And yes I'm a noob to freebsd jumping in at the deep end but that's just my method of learning.

While I'm here, does anyone have a link to some kind of detailed documentation on setting up firewalls on freebsd. I'll google at a later time but once again I'd appreciate it if someone can save some time so I can jump right in tommorow.

TIA

PS I tried redhat for a week and now freebsd for the past week and so far I'm definatly picking up freebsd faster. It's generally easier and better. And the documentation rocks.
The freebsd handbook is my new bible, the php bible goes back on the bookshelf for now.
I know you guys already know that but I just had to say it.

>> The NIC works with the generic kernal but now that I want to compile my own I don't know which driver to compile in.
With the generic kernel, what driver did you use for ifconfig, when you configured the NIC. I'm guessing the 'ed' driver since you mentioned an NE2000 clone. You can find out for sure, if you type ifconfig, and see what the device name is. The letters from the name of the device indicates the driver. For example, my ifconfig output reads like this (pay special attention to the bold font):

So, from the above output, I know that I need the xl driver for a custom kernel. Determine what driver your generic kernel is using and that's what you'll need to add in for your custom kernel.

You may also need to add some additional drivers depending on your card. For example, if you're using the ed driver, then you need to include these two lines in your custom kernel file.

If you read the notes for the GENERIC file, you'll notice a comment right above the device ed0 line saying that it also requires device miibus, which is why you need to include it as well. Hope this helps

[edit]I forgot to mention that I took those two lines from the GENERIC file of a 4.9 Kernel. Since you're running 5.1, copy the corresponding lines from the GENERIC file for your kernel .[/edit]

Thanks, that's a better answer than I could have wished for.

Next time I know I can answer my own question by typing ifconfig.
thanks again.