• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Olicom Token Ring Cards

Hardware
5
17
7.7k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S
    sullrich
    last edited by Jun 20, 2006, 5:39 PM

    @trout:

    Why is that … according to BSD docs the token cards are handled just like eth ones just a difference driver.

    And if BSD has a driver why couldn't pfsense?

    I said that I have 0 exposure to it.  Give it a try, I am not sure if it works or not.

    1 Reply Last reply Reply Quote 0
    • T
      trout
      last edited by Jun 20, 2006, 7:07 PM

      It does not …  :(

      1 Reply Last reply Reply Quote 0
      • B
        billm
        last edited by Jun 21, 2006, 4:26 AM

        FWIW, it's probably because we don't enable the oltr(4) driver:
        http://www.freebsd.org/cgi/man.cgi?query=oltr&sektion=4&apropos=0&manpath=FreeBSD+6.1-RELEASE
        in our kernel.  I don't see much use for it in general in our tree though - it's outdated hardware and it's not worth putting a driver that maybe one person on this planet might use in the tree.  I'd suggest pulling down the dev iso and rolling your own - the build process is relatively simple and all you need to do is add the driver to the kernel config.  Or get a token ring -> ethernet translational bridge from Olicom (er eBay - hell I can probably dig a few out of the scrap pile at work sigh).

        –Bill

        pfSense core developer
        blog - http://www.ucsecurity.com/
        twitter - billmarquette

        1 Reply Last reply Reply Quote 0
        • T
          trout
          last edited by Jun 21, 2006, 6:38 PM

          @billm:

          I'd suggest pulling down the dev iso and rolling your own - the build process is relatively simple and all you need to do is add the driver to the kernel config.  Or get a token ring -> ethernet translational bridge from Olicom (er eBay - hell I can probably dig a few out of the scrap pile at work sigh).

          –Bill

          Can you give me the brief howto on that …
            ... do you mean down load the dev tar or just modify an install of rc1

          Might just take you up on the bridge offer.

          Thanks

          1 Reply Last reply Reply Quote 0
          • S
            sullrich
            last edited by Jun 21, 2006, 6:50 PM

            1. Download the developer ISO
            2. Load the developer iso and then login to console
            3. Wait for the developer bootstrap process to finish
            3. Edit /home/pfsense/tools/builder_scripts/conf/pfSense.6 and add the device
            5. cd /home/pfsense/tools/builder_scripts/
            6. ./build_iso.sh

            Wait for it to finish and then you will see an ISO (it will tell you the location).

            Please keep in mind this is unsupported territory you are in.

            1 Reply Last reply Reply Quote 0
            • N
              Numbski
              last edited by Jun 22, 2006, 4:56 PM

              But it's gloriously FUN unsupported territory. :D

              Really.  This will get your foot into the burgening token-ring marketplace.  It's about to boom I tell ya.  ;D

              1 Reply Last reply Reply Quote 0
              • T
                trout
                last edited by Jun 23, 2006, 7:20 PM

                Yeah legacy is a drag.  Beats mass conversion ( $$$ and headache ) Sure Cobol programmers feel the same way.  It nice to be able to make the transition tranparent.

                Don't like it either, but it sure goes a long way when you can say "no problem can do that" to the people with the money.

                With a poor attitude open source can leave a bad taste in Power that be.  Open source is about just making it work, and work well.  With the added bonus of not spending an arm and a leg.

                On to real stuff …..

                the script that graps the CVS file for pfSense inside of build_iso.sh just fails really not much information

                1 Reply Last reply Reply Quote 0
                • S
                  sullrich
                  last edited by Jun 23, 2006, 7:23 PM

                  The Freesbie server is currently offline.  This data is needed to build a CD.

                  1 Reply Last reply Reply Quote 0
                  • T
                    trout
                    last edited by Jun 23, 2006, 7:45 PM

                    Ok, thanks

                    .. ETA … is there big problem or just routine up when u done?

                    1 Reply Last reply Reply Quote 0
                    • S
                      sullrich
                      last edited by Jun 23, 2006, 8:09 PM

                      Not sure what the problem is.  I don't admin their server.

                      1 Reply Last reply Reply Quote 0
                      • T
                        trout
                        last edited by Jun 26, 2006, 8:06 PM

                        @sullrich:

                        1. Download the developer ISO
                        2. Load the developer iso and then login to console
                        3. Wait for the developer bootstrap process to finish
                        3. Edit /home/pfsense/tools/builder_scripts/conf/pfSense.6 and add the device
                        5. cd /home/pfsense/tools/builder_scripts/
                        6. ./build_iso.sh

                        Wait for it to finish and then you will see an ISO (it will tell you the location).

                        Please keep in mind this is unsupported territory you are in.

                        I know this is unsupported but could I get a little assistance so I can learn how this works …

                        I did as above, but update_cvs_depot function from inside build_iso.sh
                        complained
                        "move away pfSense/RELENG_1; it is in the way.
                        so I did some digging
                        added export SKIP_CHECKOUT=yes
                        and    export SKIP_RSYNC=yes
                        to my pfsense_local.sh

                        but it still tries to get CVS files

                        ... so I commented out the call  ( cvs is not important to me this point )

                        ... so now when freebsd build is running I notice that it complained about not having
                        bsdinstaller
                        cpdup
                        lua
                        lighttpd

                        how do you get the these packages into the build process ????

                        thanks .......... ahead of time

                        1 Reply Last reply Reply Quote 0
                        • N
                          Numbski
                          last edited by Jul 1, 2006, 1:18 AM

                          Skip checkout and skip rsync?

                          You should probably allow one of those to run.  I'd leave the checkout in there and set rsh=ssh.

                          That's the FreeBSD admin in me talking and not a pfSense dev, so YMMV. :)

                          Side note, I have a Token Ring Jetdirect card for a color laserjet sitting here that mistakenly shipped with my printer.  Have a use for it? :D

                          1 Reply Last reply Reply Quote 0
                          15 out of 17
                          • First post
                            15/17
                            Last post
                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.