@johnpoz You helped me. You gave me some good tips. There will be other - non technical - solutions which will stop this kind of traffic. It is just a kind of forensic :)

pfSense logs only to ram. If you need long term logging you will need to use a syslog server. See: http://doc.pfsense.org/index.php/Copying_Logs_to_a_Remote_Host_with_Syslog Steve

@balubeto: pfSennse 2.0.1 can also directly manage the PPPoA protocol No. @balubeto: or I are obliged to set the ADSL 2+ modem in PPPoA mode? Yes. Your ADSL modem will probably talk PPPoE to pfSense but pfSense needs something else to handle the carriage of PPP in ATM cells.

Numerous ISPs, and businesses that aren't ISPs but act as one (generally sharing their Internet amongst a building of other tenants), do exactly what you describe. Limiters generally the best for that type of usage, and the easiest to configure.

Check a sqlite sample on cpan. using DBD http://search.cpan.org/~msergeant/DBD-SQLite-0.31/lib/DBD/SQLite.pm http://mailliststock.wordpress.com/2007/03/01/sqlite-examples-with-bash-perl-and-python/ using DB http://search.cpan.org/~vxx/SQLite-DB-0.04/lib/SQLite/DB.pm Remember to create the sqlite database first att, Marcello Coutinho

The reason for going with a smoothwall, Endian, or untangled type of distro is the subscriptions for the web filtering, anti virus, spam control ect… As well as they, like mentioned have done a lot of work to make the underlying packages pfsense uses to work, in a much more solid versital form. I would love to run it all in one box but i have yet to see it possible to provide the features we need to meet certain security standards while keeping the speed there. And i am guess this is why I see a lot of people who have pfsense and untangled combo.

All right jimp. Thank you for your attention! ;) []`s Jack

That's always been the case. If the interface with the IP address configured upon it goes down, then the bridge goes down. The fix is to assign the bridge interface and make the bridge interface your LAN interface, so it has the IP address on it, and your wired lan and wireless lan interfaces would be assigned separately with no IP address on them. Search around the forum, it's been covered many times.

Quote from: timbp on Today at 06:03:49 pm Four hours later PPPoE stopped and I have not been able to get it to connect since. I'm not sure what you mean by that: the ppp log reported ppp had exhausted its connection attempts and exited?  can you post an extract from the log at that time? No I don't have logs from that time. Initially, I booted from a USB and installed to a hard disk. I then did the setup wizard, and everything worked perfectly. I spent some time setting up static IPs, rules and schedules, and eventually had a system that appeared to be doing everything I wanted. PPPoE was connected, I was watching a movie streaming from a NAS, one child was playing Xbox online while simultaneously using Skype, others were browsing Facebook, and everyone was happy. Then, about 4 hours later, the power supply to the modem was interrupted. I plugged it back in, and pfsense has not been able to get a PPPoE connection. I have unplugged and replugged all the cables multiple times, both to ensure they are connected, and because i have tried putting other old routers in place of the pfsense box – and they connect to PPPoE immediately. I have gone back to the start -- booted from a USB, installed to the hard disk, run the setup wizard, all exactly as I did the first time when it worked. I doubt I'll get back to this for a while now. I'm trying another firmware on one of the old routers. It doesn't have the flexibility in scheduled rules that pfsense has, but it may be sufficient. Thanks for your help anyway.

@KaSper(S)ky: The first picture was the ip address 192.168.4.1, and later I changed to the 192.168.4.2. Later changed what to 192.168.4.2? Clearly you changed the IP address you told the browser but did you also change the IP address of the pfSense LAN interface? And why did you change what you changed? On the information you have supplied I'm left believing you have your pfSense LAN interface with IP address 192.168.4.1 and you are attempting to access the pfSense web interface by accessing IP address 192.168.4.2 and complaining you can't access it. If you can't see what is wrong with that combination then you are out of your depth and probably need to get help from someone who can sit beside you and watch what you are doing and challenge you immediately you do something "unusual". Maybe you just "forgot" to say you had also changed the pfSense LAN interface IP address to 192.168.4.2. If you repeatedly give me incorrect information or "forget" to tell me you just made a change or a few changes to my suggestions then I'm likely to feel my time would be better spent working with someone who provides accurate configuration data and closely follows my suggestions and tells when they do something different and why they did something different. @KaSper(S)ky: I dont set up default getway because I dont know which ip address should be standing there. I hope you know now what the default gateway IP address should be. @KaSper(S)ky: Version 1.2.3 works fine while 2.0.1 is not. That's why I asked for help with the setup version 1.2.3. I would be very happy to step aside if another reader wants to help you with pfSense 1.2.3. I'm not prepared to give you any assistance with pfSense 1.2.3.

"Doctor it huts when I do this!" "Don't do that!" As marcelloc said, snort is probably filling it up some way. Could be logs, or rules, or who knows what. snort is a large package. Trying to make that, and all its data, fit in a 512MB slice along with the base install of pfSense is probably not going to work out very well. Grab a 4GB CF. They're cheap, buy a couple spares.

Requested details WAN Modem IP (192.168.2.1) OPT1 Modem IP (10.2.2.1) WAN IP Address(192.168.2.2/24) , Gateway (192.168.2.1/24) OPT1 IP Address (10.2.2.2/24), Gateway (10.2.2.1/24) [image: System-Gateway-Groups.JPG] [image: System-Gateway-Groups.JPG_thumb] [image: System-GW.JPG] [image: System-GW.JPG_thumb]

If all of the hostnames for that domain can be resolved by an IP across the tunnel, setup a DNS Forwarder Domain Override to point queries for the remote site's domain name to the DNS server on the other end. Should be that easy.

Looks like lighttpd 1.4.31 is working fine in the 2.0.2 and 2.1 snapshots, so this should be resolved unless someone else finds a problem with it.

@NumLock: I have to make rules to vLan100 to get internet on vLan100? Yes.