ok….. thanks for your response. i suppose, at worst, you could hose the 1.23 slice completely so it won't boot so a fresh install and then a restore from backup would be the absolute worst case. cheers.

OK now, thanks!

WPA is broken in the latest snapshots.  The one currently building will fix it for access point mode and the next one after that will fix it for everything else.

Just put the other WAN on Tier 1 as well and it will do Load Balance and failover at the same time.  :o

@ermal: Your ipalias is the same as you carp vip ip?! Do you expect this to work? Sorry, there was a typo on the Alias, corrected now. BTW: I was unable to retrieve the redmine ticket #, so I couldnt update it there. Apologies! == I just tried out another possible scenario: Set up the pfsync AND the /27 subnet on OPT1. Loosing the (my!!) preference of a dedicated pfsync interface, but this seems to work…

I did find the "Bypass firewall rules for traffic on the same interface" option and everything is just fine if I enable it, but I can´t remember doing that in 1.2.3. Thanks! Jesper

Upgraded to i386 build 2.0-BETA4-20100901-2344 this morning and the issue seems to be resolved. Downloaded several files via FTP and no kernel panic.

I've not tried it on WAN either, only OPT interfaces.

For sure! [image: dw0scjb6ywp4xqo49qxp_thumb.jpg] [image: 9lrokbf7wp22wvea081y_thumb.jpg] [image: 4xaa4bsnpefr0yu07llr_thumb.jpg] [image: i9jjvffj08k7j8o74p2t_thumb.jpg] [image: 5kdkoz74c2fy9stehq5j_thumb.jpg]

Is DNS forwarder only woking on IP? I have 2 NAS with ftp/Web server now.

I wouldn't have guessed that, as there's no VLAN in play on this system. But I'll give it a try when the next snapshot drops.

@kpa: Edit: 2.0 BETA already seems to do this with dnsmasq –stop-dns-rebind option, the other protection methods seem a bit excessive in that case… Yes that's already done, no it's not excessive - that only helps if you're using the DNS forwarder, lots of people don't.

This has nothing to do with the thread you hijacked so I split it. Get a packet capture on the inside and outside interfaces, see what's happening. When there is no NAT involved, there are no GRE difficulties, you simply have to allow it in your inside interface's rules.

CARP generally enough, it'll protect you from the same things lagg would additionally.

A good provider in australia is TPG. They give you heaps of bandwidth (180GB) for $50 a month or so. I think you have to get a contract with them. Their service desk is crap, so hope you never have an issue Internode and iinet are the next best on bandwidth but much better on support. For $50 per month I get about 60GB bandwidth at ADSL 2+ speeds. I know this is nothing like Singapore but these are the best options.

Thanks heaps again jimp! We do use Apple Remote Desktop a bit so that is probably why they said to use tap instead of tun. Saying this, apple remote desktop does work over the connection I just setup based on your instructions. Thank You again!

Don't worry, be happy! I expect its just a reporting issue because SATA drives don't use the IDE cables. Its probably worth lodging a FreeBSD PR (Problem Report) at http://www.freebsd.org/send-pr.html inclding both FreeBSD 7.1 and FreeBSD 8.1 startup output. I expect this particular chipset is not particularly common which could make it a challenge for the developers to test a fix.

confirmed, this does it for me.

You could even flushed the vpns table and be done with it without patching. Diagnostic->Tables

Note that the list you linked is not all inclusive, some manual pages for drivers like ata(4) have their own list of supported hardware that is not included in the main HCL.