As always, thanks for looking
I thought it might be useful to pass along my initial impressions of our new Soekris net5501-60, with 4-port lan1641 card and vpn1411 card.
As advised from this forum, we used the generic PC m0n0 image. The first stumbling block was setting the console speed of the Soekris box to 9600 to match m0n0-the net5501 uses 19,200 baud as the default speed. To change the speed in the Soekris ComBios, hit Ctrl+P on boot when connected with your null modem cable, and then use the following command:
set conspeed = 9600 Before changing the Soekris console speed, we'd get garbage characters instead of POST (if hyper term was set to 9600), or garbage characters after POST (if hyper term was set to 19,200, or once m0n0 took over and downshifted the console speed).
Once that was done I enabled the initial interfaces, and accessed the GUI. One really nice touch with the net5501 is that you no longer need a crossover cable to connect directly to it from your PC or laptop (like you do with the net4801). Our interfaces are setup as follows:
vr0: LAN 192.168.1.x
vr1: WAN 64.140.x.x
vr2: Stats server 192.168.3.x
vr3: PBX and VoIP gateway 192.168.2.x
sis0: Admin subnet 192.168.4.x
sis1: LAN2 192.168.9.x
sis2: LAN3 192.168.8.x
sis3: Admin2 and wireless 10.10.11.x
One mistake I made was not renaming the interfaces (vr0, vr1 etc) when I tried to import the XML config file from our old net4801. Because of this, the Router locked up and I had to start over again.
We've been running for about a month, with no major issues so far (That is, no issues that I didn't cause). One thing that was very different for us this time around is that we have the entire Internet blocked on our LAN interface, with about 20 websites and domains white listed. This was a much bigger challenge to set up than originally anticipated, simply because most websites need more than one IP address opened to work properly. A website that has third party stats tracking might need 2 or 3 other IPs opened up. If images are called from another IP, that IP needs to be opened up as well. It was a pain to get it all sorted out, but using WallWatcher with verbose logging enabled on the default block rule was extremely helpful.
All in all, we're pretty happy so far with our new net5501. We have 85 employees, 14 servers of various flavors, a dozen printers, a PBX, and a VoIP gateway all running happily on m0n0wall. I think I need to figure out how to turn off unneeded interfaces on the Soekris (like the USB port for example), because we're seeing a "scheduling overrun" error on WallWatcher. Another nice thing about the net5501 is that GUI access (even remotely) is lightning fast. Our old net4801 was getting quite a workout, but the net5501 doesn't seem to be breaking a sweat.
Chris
New Hampshire