Using IEEE1394 has the CARP interface



  • I was wondering, since my Firewire adaptor is seen as a possible interface fw0, to use the for CARP.  By any luck, if it is possible to do so, does anyone know if I only need to plug pin to pin or need to crosswire some of them…

    Thank you

    Martin



  • I haven't tried CARP on one, but ordinarily 1394 is not crosswired - one cable for all uses.



  • Nobody has tried this lately but when we tried this some time ago it was broken. Give it a shot using the latest snapshots as they run a newer freebsd version.



  • I've done some initial tests on 1.0.1-SNAPSHOT-03-23-2007.
    Added the following to loader.conf:
    firewire_load="YES"
    if_fwip_load="YES"
    copied firewire.ko and if_fwip.ko from a FreeBSD 6.2 box into /boot/kernel
    Rebooted the box, assigned fwip0 as OPT2. Added an allow all rule on OPT2.
    Repeated on second box. Connected cable between port one on both boxes. I didn't have a 6pin-6pin cable handy, but did have a spare 4pin mobo connector, so I used that and a 6pin-4pin cable.
    I can successfully ping between the two boxes now. I haven't setup CARP, but I think it should work.
    I don't need more than two nodes in the cluster, so I have no idea as to the feasibility of adding more.
    edit:
    Got a 6-6pin cable and set up a test CARP on the LAN side on the test boxes. Everything seems to work fine.



  • have you think about usb ?
    do you think it's possible ?

    soekris mainboard has usb ( usb2 in last model net5501 ).
    I will think about it later with my one.

    sincerely,
    liwoks



  • AFAIK, there is no way to network USB-USB. You best bet would be to try a couple of USB-Ethernet devices. They all suck under FreeBSD, but I've heard axe (ASIX chipset) suck slightly less than others.
    You might be able to hack it enough to use as a sync if, as the traffic should be very light. Be aware that I have never messed with USB Ethernet adapters and plan to avoid them, so don't consider me very knowledgeable on this subject.



  • more info to these USB-ethernet adaptors under the fillowing link (ie. which products use this chip)
    http://www.freebsd.org/cgi/man.cgi?query=axe&sektion=4&manpath=FreeBSD+4.11-RELEASE



  • USB networking just sucks in general, it's not a FreeBSD thing. I've used a couple different USB NIC's on FreeBSD and they aren't any better or worse than they are on Windows. They're slow and the latency is about 10-20 times higher than a PCI NIC. This was USB 1.1 equipment though, which is much slower than USB 2.0. Regardless, I have doubts as to how reliable they would be long term, and I would never suggest using one in any sort of serious production environment.



  • @dotdash:

    I've done some initial tests on 1.0.1-SNAPSHOT-03-23-2007.
    Added the following to loader.conf:
    firewire_load="YES"
    if_fwip_load="YES"
    copied firewire.ko and if_fwip.ko from a FreeBSD 6.2 box into /boot/kernel
    Rebooted the box, assigned fwip0 as OPT2. Added an allow all rule on OPT2.
    Repeated on second box. Connected cable between port one on both boxes. I didn't have a 6pin-6pin cable handy, but did have a spare 4pin mobo connector, so I used that and a 6pin-4pin cable.
    I can successfully ping between the two boxes now. I haven't setup CARP, but I think it should work.
    I don't need more than two nodes in the cluster, so I have no idea as to the feasibility of adding more.
    edit:
    Got a 6-6pin cable and set up a test CARP on the LAN side on the test boxes. Everything seems to work fine.

    Works like a charm for me, thanks for the instructions.

    If you don't have a freebsd box aside from your pfsense box, you can download the ISO and extract the files from there.

    It would however be nice if they were included …hint... hint...hint  ;D

    Motherboard ASUS M2N-SLI-DX, NFORCE 570 chipset



  • Yeah, so far fwip has worked fine for me. I think fw was removed because it wasn't working, but it looks like fw was a non-standard implementation, whereas fwip should work to an osx or windows box, etc. Not that I've tried. Maybe if we get some more reports from people that this is working, someone will put it in the base code.



  • It is actually working fine for a month now on 1.0.1.  Download 1.2-BETA-2 today, having fw support built-in but not fwip.

    I would also like to have it in 1.2

    Martin


Log in to reply