After some more testing today it looks like sometime around the first of Nov. it broke. I tried a snapshot from 10/30 and it worked. When I went to 11/4 it didn't. Hope this helps someone know where to look.

Hi,

sorry for my late feedback but I didn't get it earlier. Today I updated to the latest snapshot, becaus I read in the rsc, that there were some fix for updating WAN interfaces IP adresse or something and now I just want to let you know, that it works for me again.

Great job, thanks!

Would you share the config you use for pfsense/draytek please?

I'm struggling with a similar setup at the moment.

Cheers!

thanks
stuck on this build due to the squid bug.
will upgrade as soon as poss.

:)

TooMeek,

Sincerely I don't know how it works on my WinXP, just works one time, but only works in my PC, all others PCs doesn't work.

I just gave up of PPTP and start using OpenVPN, much better, much safer.

Looks like something is crashing during the boot process. Are you sure that is a good CF card?

If you try even older snapshots, can you get one to work?

The embedded image only prints that to the console and then switches to serial output.

Connect a null modem serial cable and you'll see the remaining console output.

This might be another symptom of the problem causing Unable to check for updates which you have also reported.

FYI:  Seems to be a freebsd issue with intel nics.

http://redmine.pfsense.org/issues/1093

Using broadcoms now, problem not happening.

@pwnell:

Installation works, but does the application work?  It does not filter any MSN traffic for me.

That would be a topic for a new thread. This thread is only for the installation issues, which should be resolved on both i386 and amd64.

Hi,

Yes, sorry about this :-(

I already fixed it, so it should be available on next snapshots.

Sorry again,
Pierre

After a lot of head scratching I finally managed to get it to work. I'll post the settings I used, in case someone reads this post later and possibly find them useful.

Services>Rules: WAN
Proto: UDP
Source: *
Source Port: *
Destination: 224.0.0.0/4
Destination Port: *

Services>Rules: LAN
Modify the "Default allow LAN to any rule" and enable the option "This allows packets with IP options to pass. Otherwise they are blocked by default. This is usually only seen with multicast traffic.". It is found under "Advanced Options" near the bottom of the page, when editing this rule.

(The next rule is specific for my service provider and can be skipped if your service provider doesn't have a similar service. In my case it provides access to the Warner Films channel.)
Services>NAT: Port Forwarding
Proto: UDP
Src. addr: *
Src ports: *
Dest. addr: WAN address
Dest. ports: 8254
NAT IP: <ip of="" iptv-box="">NAT Ports: 8254

Services>IGMP Proxy
Here I made two rules. One for upstream and one for downstream traffic.

Upstream
Name: WAN
Type: upstream
Threshold: <empty>Values: 224.0.0.0/4, 195.238.200.0/24 (*the second address mask specific to my service provider. See note below.)

Downstream
Name: LAN
Type: downstream
Threshold: <empty>Values: 192.168.0.0/24 (This is the subnet mask of my internal network. Change it to what you use.)

Notes
The second subnet mask I specified for the upstream is the net from where the data stream is coming from, in my case. Without this I get nothing but a black screen.

To debug what was going on, I ssh'd to my pfSense box and ran igmpproxy from the command line:

igmpproxy -d -c /tmp/igmpproxy.conf

After switching to an IPTV channel I noticed the following warning coming from igmpproxy:

Warn: The source address 195.238.200.2 for group 239.192.105.14, is not in any valid net for upstream VIF.

I checked the IP and turns out my service provider own the 195.238.200.0/24 network. After adding it to my upstream settings, I was able to watch tv.

For reference, I am using "Elisa Viihde", a Finnish IPTV solution.

pfSense version that I'm using is 2.0-BETA4 (i386) built on Fri Dec 10 20:38:22 EST 2010 running on a PC Engines ALIX 2D3 board.

Posts I found useful
http://forum.pfsense.org/index.php/topic,16943.msg113914.html#msg113914
http://forum.lissyara.su/viewtopic.php?f=3&t=17080#p158230 (in Russian)</empty></empty></ip>

Thanks for the feedback.  I'm glad it's working for you. I'll try doing a clean install.

If you want the disk to almost never be touched, run the embedded version on the hard drive. Then everything that's written during normal operation is in RAM.

It would also be fine to hack your current install to run /tmp from md.

check the sticky's

http://forum.pfsense.org/index.php/topic,10409.0.html

Gotcha. Not a big deal, just seemed inconsistent. I'm not sure if it matters much, but it may be helpful to change the status icon (or remove it) for mobile tunnels so it's obvious to the user that it's not being checked and may very well be working, since right now it looks like they're never up. Of course a "show mobile status" link that adds mobile status when needed without checking every time would be optimal, but it's if non-trivial that's probably something that can wait for a point release if it is important to someone.