@syedadi: the reason my network have two isolated subnet because of the security, so changing the subnetmask is not piratical. You may find it helpful to read http://forum.pfsense.org/index.php/topic,39604.0.html It is not a trivial task to provide real isolation between two subnets sharing the same ethernet segment.

Don't bug people via private message for help, it's against our rules (otherwise we'd all be wading through 1000 PMs every day) and definitely not going to encourage answers (I /dev/nulled that and am answering now just because I stumbled across it browsing threads). That isn't currently supported, you can't use md5sig currently (far more to it than a kernel option).

@submicron: If a company already has a significant investment in Juniper gear, they're going to be fairly skeptical of some candidate who wants to strip it all out for another solution.  Its better to learn the gear they have, be proficient with it and then after you've proved yourself to your employer, make appropriate recommendations for how to make improvements.  You'll also find that this approach tends to help you plan your pfSense deployments a little better since you already know how the network is configured and can keep an eye out for the little gotchas that any large network retooling project has. This is a very honest advice. Two thumbs up for this. @Derek: "if it ain't broke, don't fix it." This one I learned in a hard way. ::)

Because nobody took the effort to convert to mpd5 and/or nobody has requested/supported for it to go to mpd5.

@tim29: Is there any way to do this with just two NICs? That would make this particular installation a lot easier. Yes, use a small VLAN capable switch as "port multiplier" for one of your pfSense NIC: one "trunk" port between the switch and pfSense, one switch port to each office. There has been a number of posts on VLANs in the last few weeks. A search of the forums for VLAN should turn up useful additional information.

The network map will help. http://www.pfsense.org/index.php?option=com_content&task=view&id=62&Itemid=73 Steve

https://…/services_captiveportal.php "Enable captive portal" is not enabled

@thewev: The 00:bd:4a:4c:00:00 MAC is for TAP0. I guess pfSense assigned it TAP0 when I created an old OVPN configuration. Is there such a thing like a "private MAC range" similar to the privat IP subnets? Where does pfSense pull the MAC from?

Actually i can't i've got only one isp link and no cp at use.. But here are smarter ones also

@Metu69salemi: mpls is done by operators, but still some other vpn over it would be nice something from wiki concerning mpls Thanks for the link.

Thanks a lot.  It seems that the reset RRD data method will get rid of all graphs and recreate the rrd files according to the latest interface/gw info.  If I accidentally deleted the wrong rrd file (ie interface still exists) via shell, it seems it won't auto recreate it on next refresh.

No problem. It has taken me a while to find my way around the menus and what the items mean.

It's a known issue. http://redmine.pfsense.org/issues/1572

I upgraded to the latest 2.0 snapshot and the problem is still there. After a reboot I still have to set my WAN interface to 'none', save and then reset it to PPPoE with the proper credentials. After that the PPPoE connection comes up immediately. Below an excerpt of my logfile: Jul 30 19:34:29    ppp: [wan_link0] Link: reconnection attempt 42 in 4 seconds Jul 30 19:34:29    ppp: [wan_link0] LCP: Down event Jul 30 19:34:29    ppp: [wan_link0] Link: DOWN event Jul 30 19:34:29    ppp: [wan_link0] can't remove hook mpd8424-0 from node "[11]:": No such file or directory Jul 30 19:34:29    ppp: [wan_link0] PPPoE: can't connect "[11]:"->"mpd8424-0" and "[f]:"->"left": No such file or directory Jul 30 19:34:29    ppp: [wan_link0] Link: reconnection attempt 41 I also compared the /cf/conf/config.xml from the appliance at my work and the appliance at home. They are running exactly the same version 2.0RC 3 Fri Jul 29 22:08:01 EDT 2011. The only differnce between the two installations is that the appliance at home is upgraded from 1.2.3 to 2.0 RC3 and the appliance at my work is a preinstalled 2.0 appliance updated to the latest 2.0 snapshot. config WAN interface / pppoe home: <wan><enable><if>pppoe0</if>       <blockpriv><blockbogons><spoofmac>00:00:c0:7a:bc:47</spoofmac>       <ipaddr>pppoe</ipaddr></blockbogons></blockpriv></enable></wan> <ppp><ptpid>0</ptpid>       <type>pppoe</type>       <if>pppoe0</if>       <ports>fxp1</ports>       <username>xxxxxx@yyyyyy</username>       <password>hdgvcfdr</password></ppp> config WAN interface / pppoe work: <wan><if>pppoe0</if>       <blockpriv><blockbogons><disableftpproxy><bandwidth>100</bandwidth>       <bandwidthtype>Mb</bandwidthtype>       <enable><spoofmac><ipaddr>pppoe</ipaddr></spoofmac></enable></disableftpproxy></blockbogons></blockpriv></wan> <ppp><ptpid>0</ptpid>       <type>pppoe</type>       <if>pppoe0</if>       <ports>vr1</ports>       <username>xxxxxx@yyyyyy</username>       <password>ksdfghkkldjsf</password>       <bandwidth></bandwidth></ppp> Looks like on my device at home I'm missing some fields in the wan and ppp part of the XML config file. Can this be the cause of the PPPoE problems? Erik

Typically when you change your ADSL modem from router to bridge mode you need to also change the corresponding pfSense interface from DHCP and enable pppoe on it: Interfaces -> (assign), click on PPP tab, add a PPP interface, go back to Interfaces -> (assign), add the ppp interface, assign it to WAN (or whatever) then add the username and password that had previously been configured in the ADSL modem for ppp. I don't know if that applies to your service.

Exactly, I expected that - just showing that its not pfsense not handling a torrent.