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
2. Open the unit and move the serial cable to serial #1.. It's most likely on COM2.
That doesn't apply to the 1041C. The front serial port already is COM1. See http://firstname.lastname@example.org/msg03811.html for how to get the nexcom 1041c work with pfSense. I have 3 1041c out for production use, 2 with hdd installs, 1 with cf-card embedded version. All of them working great.
Please be aware of the following bug. Been haunting me on the Hacom units for the last week:
When we're talking multi-interface systems, this becomes an issue. I was trying to build an 11 interface box (to handle all of the carp interfaces since you can't alias) and if it weren't for this bug I'd have no problems…
I case you want to use the hdd in this device you sould have a full install running at the hdd without a cf-card. The cf-card version won't utilize a hdd or any other media without preforming unsupported hacks.
Mine is an AMD-K6-2 400 mhz chip. It has 2 slots for memory, one which is filled with 256 meg of PC100 memory.
Would you mind taking a good high-resolution photo of the CPU area, like this one?
I'm specifically interested in JP2.
I have purchased 2 units of this hardware, and I have problems installing pfSense the full version on a 2,5'' HDD. The problems are about UDMA, and it seems to be the 44 pin cable because I've used other cable (the one which is included in a Soekris hard disk kit) and pfSense installed with no problem. The big problem is that the Soekris cable is only 1cm long.
Has anyone installed pfSense full version in the FX5620?
Yes I had the same problem:
I found that the problem was due to it trying to use UDMA100, and that's
not really possible on a 2.5" drive with a 44 pin cable.
atacontrol mode ad0 udma33
in the shell allowed me to complete the install
then I added
into /boot/loader.conf which turns off dma for the hard drive
seems to have fixed all the issues.
I tried adding <earlyshellcmd>atacrontrol mode ad0
udma33</earlyshellcmd> into config.xml but didn't manage to get that to
I might actually have an answer, though I can't say for sure until I get in to the office: the very high interrupt load caused by the flood of incoming connections could be tripping the watchdog timer, and looking at the init code here, it looks like the watchdog is enabled at boot. Looking at the watchdogd manpage it looks like I can kill watchdogd to disable the checking – I'll try that in the morning and let you know how it goes.
I am currently using monowall and it is not shaping my VOIP properly. Basically controls the upload fine, but the download shaping isn't there so if we are downloading the voice goes all choppy.
You can't effectively control download using any type of QoS or traffic shaping. You'd have to control your ISP's end of the link to control download speed.
Im not sure, but I dont think that is possible on the IP330's since the only way to watch them boot is through the management port and hyperterm. There is no boot loader prompt.
Bollocks. You need to get a proper null modem cable. There is a BIOS that looks like a text version of a normal AWARD bios.
I had exactly the same issue using a three-wire null modem, where you really need all the handshake lines etc. The FreeBSD stuff starts coming up after the boot loader prompt, if you have the wrong serial cable.
The cable is worth under $10 in any currency. G'luck!
http://criggie.dyndns.org/tech/ip330/ <– lots of pictures and info on IP330 and pfSense.
There is another encryption card on ebay like the one above if anyone wants to grab it for testing.
done …i have beta 4 now but still got this problem
May 11 01:54:15 last message repeated 22 times
May 11 01:52:26 last message repeated 49 times
May 11 01:50:12 last message repeated 6 times
May 11 01:50:12 dhcpd: lease 192.168.11.66: no subnet..............etc etc
If you can increase the number of lines of syslog output, then try and give some earlier lines would be helpful.
Different USB keyboards. I've messed with every USB option I could think of in the bios. It's the same in every case, no difference. The keyboard must be unplugged after the kernel is loaded and plugged back in to be used.
Does FreeBSD even support it? When there's an in tree driver, we can add it to our driver list - we aren't going to ship binary blobs or apply non-BSD licensed vendor patches to make this work. FWIW, usb ethernet adapters do work, if the cable modem presents itself as a supported usb ethernet adapter, then it should "just work". Give it a try, worst case is that is just won't work and you've cost yourself 15 minutes of play time on the livecd (alot less than this discussion has taken I'm guessing).
It is autodetected as a USB network card in IPCop.
I'll give it a try when I get home.
Thanks, Ill try to do my best. There is maybe something in the BIOS that can be changed (didnt help to change PCI slot). But anyway, these used network cards doesnt cost much so I can just buy a new one. Thanks for the help though
And MUCH MUCH more noise! I would not want to sleep anywhere near a nexcom.
And thats the old three way trade-off… Pick any two of FAST QUIET CHEAP
Silent / near silent computers are relatively easy to build, but that comes at a price. And More Speed makes heat, which has to be removed somehow. And airflow is the most common way for doing that.... etc etc.
Sometimes I wonder if its reasonable to cool an entire 19" cabinet with some hefty large slow speed fans, rather than having lots of spuddy little fans whirling at top speed.
It probably is power supply related. The ones that ship with the Soekris boxes can barely handle the unit itself (12v @1A if I recall). I went to Radio Crap er Shack and picked up a 15V @1.5A for my WRAPs - the Soekris should handle the same supply. 12-18V if I remember correctly. I've seen 4801's lock up with the original supply (and you'll see that on the Soekris lists too).
For such purpose I would recommend the Soekris 4801 and a 2,5" HDD - works just fine.
Which reminds me, it's time to put my 6GB drive back in my soekris after doing an install to it on my laptop so I can play around with packages (poor poor box) :)
Search the m0n0 list, the guy who sold them answered that question somewhere. He said that they were custom build and there is nowhere to buy these. At least the ones he sells but maybe something similiar exists.
I just reset the resource configs, still cant see my network card :-(
PS: yea I know I have to instal freeradius on my own, that is not that hard, but sometimes SQL functionality freaks me out…. never installs as it should, although on RedHat installs are easy
OK - to answer my own question…
Based on this post [ http://m0n0.ch/wall/list/showmsg.php?id=73/62 ], I edited the /boot/loader.rc file on the ISO and added the following 2 lines to the very top:
Then burned the ISO and booted - pfSense now loaded in PIO mode and everything worked fine. The setting was retained during the install.
Question for the developers - Will the pfSense update process lose these changes or am I now good until I need to do a new full install?
For reference I used a trial of a program called UltraISO to edit the file. You need to extract the file out of the iso, edit it, then paste it back in and save your new ISO. http://www.ezbsystems.com/ultraiso/index.html
With "only" 40 mbit/s you won't push this device that hard that you'll notice a difference I think. Realteks put more load on the CPU than Intels but that shouldn't be noticable in your scenario and your bandwidth. You even should be able to go 100 mbit/s with this device (at least between 2 interfaces). I get full wirespeed with my C3 1 GHz with 2 Via Rhine nics.
Ah, so in order to do this, I'd have to have 4 nics in each server, 2 frontside, 2 backside. Plus, those nics would have to support team failover on whatever OS they're using (mostly MacOS X Servers, and now I'm adding in about 10-11 FreeBSD servers).
Yay…that's a lot of nics. Some of these boxes don't even have that many pci slots. I know for fact that several of the on-board gigabit ports are supposed to replace the need for pci slots, so they only have 1-2 slots available.
Switch failover may be a lost cause in my environment. I may just have to be ready with the swappable switch sitting there as a just-in-case measure. :(