I Had a Linksys WRT54GS v4 running DD-WRT all the info you need is here http://www.dd-wrt.com/wiki/index.php/Switch

LAN card > 192.168.5.1/24
WAN card > Public IP from Virgin Media SuperHub Modem

But i have only config it using a wingate proxy server (Similar to pfsense) but it should work good with pfsense

;)

Thanks for the fast replies.

I think I'll stay with my current setup and use the cisco for ip4 routing…I need the gigabit speed to access my file servers in 10.1.2.0/24 in a proper way.
I'll just add another NIC to my pfsense and let it do the ip6 traffic....

Agreed, dmesg should list the card in some form. Even once/if you get it working though, you may need 2.1. I needed to go to 2.1 to get an on-board 8111e working.

I would say it's unlikely.
See:
http://lists.freebsd.org/pipermail/freebsd-net/2011-December/030620.html

Steve

Ah well it's probably a P4 type Celeron then.
The P3 server may be slightly faster but not significantly.
If I were you I would replace the CPU in your existing box. You can probably fit any Pentium 4 and a 2.8GHz P4  can be had from Ebay for almost nothing!  :)

Steve

Hmm, paid to play with pfSense. Sounds like a pretty nice job!  ;D

Steve

This is the essential point. You need the P4 power cable to make the S1200KP work, however the Pico does not not have a P4 cable. In stead you can use a convertor cable the you connect to the Molex power connector on one side and the the S1200KP on the other side. This should work even with a 65W Pico. In the end with proper power management the whole system should draw less than 20W.

I think I'd be quite hesitant to spend money on a no-name box like that.

Even major companies like ASUS are sourcing from the sweatshops of mainland China these days.  And we're seeing failure rates as high as 20-25% because they're channeling Jack Tramiel and using us as the final QA stations!  So what can we realistically expect from a source that's totally anonymous and therefore has no reputation to lose?

Most of the stuff from the sweatshops seems to be house-branded generics anyway, but at least some house-branders seem willing to pay a nickel more per unit and have them passed through some sort of final QA before shoveling them onto the boat.  But something that calls itself "OEM Production"?  Probably not.

Ended up buying a trendnet usb to ethernet adapter for $7 at radio shack.  Works great, no bouncing, negotiates at 100mb.  Definitely adapter related.

It was a BIOS related issue, just updated it and the problem has gone.

In Supermicro's web the latest BIOS Version is 1.B11, but support people sent me the 2.41 version, and that was the good ones ;)

Now my pfSense Rock's….. Thank you Guys for this wonderful FW :D

Edit:

Can't edit the first post to add [Solved] to the title, if any moderator can add this & close the Topic.

Thanks

H8SCM_OK.PNG
H8SCM_OK.PNG_thumb

Looks like a nice unit.
Are you using the status LED for anything?

I have to agree, this forum/community is by far the most helpful and satisfying I've ever been involved with.

Steve

Just a guess, but does that HP have a BIOS option to play sound through the internal speaker? If so try disabling it in the BIOS.

Yes Steve, unfortunately the Transcend device is only recognised when its Master/Slave switch is set to Master on this particular board !
I sent the thing back to the supplier when it wasn't recognised by Linux thinking it faulty and was told it had to be set to Master. When I get a chance I'll try dd'ing an .img file to the HDD and then back to the new one.
Neil

We are using the "Moxa NPort 5210", they work good… managing remote HW located at 10Km from our Office, you can't do that with a Null Modem cable  ;)

I'd suggest a low power supermicro chassis with a X9SCM motherboard coupled with a low power i3 or xeon. Passive cooling will work apart from the PSU fan. Should be pretty quiet and HEAPS more powerful.

@rjcrowder:

I used a USB stick… Can't remember for sure, but I think I made it bootable with unetbootin.

dd (or equivalent) the pfSense "memstick" image to the USB stick, the boot the target system from the USB stick.

I have successfully installed 2.0 and 2.0.1 on three IP530's using the procedures I described above. The procedures do not specifically state this, but make sure your using another machine for the procedures below, and make sure you are updating the config file on the attached HD, not the RAM disk, and make sure you re-assign both the LAN and the WAN interfaces otherwise you will get the prompt when you boot.

@rrijkse:

To assign the interfaces you have to do the following:
1. Boot from CD or USB stick with HD attached.
2. Get through the interface selection from the live boot.
3. Select "8. Shell" option
4. Mount the drive on /mnt (mount /dev/ad0s1a /mnt)
5. Edit /mnt/cf/config/config.xml
6. Find the sections "<wan>" and "<lan>" and modify the "<if>INTERFACE</if>" line with one of dc1,dc2 or dc3. On my boxes the NICs are (left to right) dc2, dc3, dc0, dc1.
7. Save the file.
8. Shutdown machine and put drive back in the IP 530.

Make sure you do not try to assign anything to dc0 using the web-interface since it will freeze up on you.</lan></wan>

Almost any new laptop is likely to have 802.11N wifi which will probably not be supported by pfSense.
You would be better off looking for a laptop with wifi on a mini pci or pci-e card so you can swap it for an older, supported, model.

Steve