Jetway Triple GIGA LAN Add-on Board (AD3RTLANG)

fwuser07

Has anyone checked which throughput is possible with this board between two gigabit ports (lan to lan traffic)?

rockbochs

paulpthcom: I am interested in getting a copy of that kernel. I've also had the same problems with warm/cold boots and the interfaces not coming up. Thanks! ;D

fwuser07: Sustained 'near' 100mbit traffic has not been a problem with these addon boards. Unfortunately, I don't have any other gigabit devices handy to check gig throughput.. :(

–Tim

Rockyboa

Just upgraded to 1.2-BETA2 today, still no support for the daughterboard with the RTL8110SC chip. Working fine with the RTL8110S-32

Will try gbelanger module tonight.

Martin

nickshore

Any follow up on the current state of these drivers ?

Be good to be able to keep up to date info on our product pages,

Nick.

dwabraxus

Any Update to this?
Anyone get the SC version working on a new snapshot?

Looking into getting a M300-LCD with a tripple gigabit card but want to make sure it will work first…

Accounts

Anyone test with 1.2 release? Did support get added? I'm looking at a new hardware buy and the jeyways price is hard to beat. 1.0.1 was fine.

PreLo

Hello,

The Jetway-board that I am using is called J7F2EDEN12G and the J2AD3RTLANG I am using unfortunately has the 8110SC-chipset.
I was able to run 1.01 just fine using the driver provided in this thread. Thanks again for that!
The only thing I could not use was the traffic shaper because altq is not supported by this rl-driver.
Hence my desire to upgrade to 1.2, hoping that the re-driver would support that.
However, my upgrade to 1.2 was not that succesful and now I am back to my old configuration.

After installing 1.2 I saw pfsense being stuck "starting" the NICs during booting the system. The system would not finish booting.
I somehow managed to get a running pfsense 1.2 just by trying out different NIC-combinations of the AD3RTLANG to be LAN/WAN at setup.
The system then worked fine just once but when I changed my NIC-configuration back to my original plans the system would be stuck at bootup again.
Really annoying and not an acceptable solution.

User paulpthcom from some posts above has probably posted this one here:
http://lists.freebsd.org/pipermail/freebsd-bugs/2007-March/023060.html
I think my problem looks quite like that.

My pciconf-output:


# pciconf -l -v
rl0@pci0:9:0:   class=0x020000 card=0x10ec16f3 chip=0x816710ec rev=0x10 hdr=0x00
    class    = network
    subclass = ethernet
rl1@pci0:11:0:  class=0x020000 card=0x10ec16f3 chip=0x816710ec rev=0x10 hdr=0x00
    class    = network
    subclass = ethernet
rl2@pci0:12:0:  class=0x020000 card=0x10ec16f3 chip=0x816710ec rev=0x10 hdr=0x00
    class    = network
    subclass = ethernet

vr0@pci0:18:0:  class=0x020000 card=0x01021106 chip=0x30651106 rev=0x78 hdr=0x00
    class    = network
    subclass = ethernet

My 2 cents here: If Jetway only built a daughterboard with some quality NICs, this Realtek-stuff has never been decent (performancewise). I'd be willing to pay two/three (ok, preferrably two times) times the price for the AD3RTLANG.

But, anyway, that has been my experience with the new 1.2 so far. I would love to actually use it but I guess so far I am stuck with 1.01. :-(

bill_mcgonigle

@PreLo:

After installing 1.2 I saw pfsense being stuck "starting" the NICs during booting the system. The system would not finish booting.

It'll hang on any interface without a link. You can even jumper two empty interfaces together and it'll boot. But you might just want to unassign the interfaces if you're not using them.

I posted about this a while back, and was encouraged to hack on the driver, but I'm waiting on 1.3 to do that so we're synched with current FreeBSD development.

PreLo

Thanks, that is interesting information.
I hope that I can find the time to give it a try next weekend.
I'll post here about my results.

rockbochs

I'm experiencing the same issues. Can anyone confirm that is is limited to the gigabit addon nic only and not the 10/100 nic? I've had to regress back to 1.0.1 for my jetway installations since all of my addon boards are gigabit… :(

Edit: I just found a patch that is supposed to fix this issue. Since I do not have a proper pfSense dev environment, can anyone patch the kernel and provide the kernel.gz? It would be most appreciated. Also, is it possible to have this patch (assuming it works) included in the next pfSense update?

Patch link: http://lists.freebsd.org/pipermail/freebsd-bugs/2007-March/023075.html

Edit 2: The latest monowall 1.3b11 works perfectly on this board. Any chance of having that functionality ported down to pfSense soon?!?

–Tim

David_W

@bill_mcgonigle:

I posted about this a while back, and was encouraged to hack on the driver, but I'm waiting on 1.3 to do that so we're synched with current FreeBSD development.

There's no need to wait for pfSense 1.3. pfSense 1.2.1 is under development, for release by the end of this month (May). It's based on FreeBSD 6.3-RELEASE, which has much more modern hardware support compared to the 6.2-RELEASE behind pfSense 1.2.

FreeBSD 6.2-RELEASE becomes end of life at the end of the month - hence the need for pfSense 1.2.1. There's no new features - just a shift in the base operating system and a few bug fixes.

gbelanger

Following up on this, our systems that were based on the Jetway boards + Triple Gig cards all crashed, one of them had to be replaced (motherboard) the other one had to be refitted with PCI cards, as the daughterboard was misbehaving.

I would not advise to go that route for those of you who want a stable setup. A via board + a multi-lan PCI might be a safer bet.

Alternatively, there are commercial manufacturers that offer all-in-one security appliance based on VIA or Intel platforms with multi-nics (and all the nice dels to go with them). These solutions have been (in my experience) very stable.

Just my 2cents.

Guillaume

rockbochs

That has been our eventual conclusion as well. The functionality (supposed) and price point make the via boards with addon modules very attractive. But, they just don't work properly. If/when the driver issue gets sorted out, I'd be willing to look at them in the future. But, for right now, we're sticking 100% with Intel based boards. They just work with no fuss or problems.

–Tim

crashnburn

Looks interesting.