• Snapshot Server Sleeping??

    Locked
    4
    0 Votes
    4 Posts
    2k Views
    S

    Ha, yeah, it's a busy little machine!! It's been cool being able to test new features shortly after they're added though!!

    :D Thanks for all your hard work everyone involved, pfSense rocks!! :D

  • Resolve hostnames on Dioagnostics: Show States page

    Locked
    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • Problem in system log

    Locked
    2
    0 Votes
    2 Posts
    1k Views
    H

    This is the complete message? There is nothing in front of it telling which service caused the log entry? Also what have been happening before you get that message?

  • PPPOE Wan testers needed

    Locked
    15
    0 Votes
    15 Posts
    6k Views
    J

    Ok then I won't expect a change till then.  Just wanted to know incase it broke after an update.

  • Need help with restoring system

    Locked
    3
    0 Votes
    3 Posts
    2k Views
    D

    Thx - solved

    mount -t msdos /dev/fd0 /mnt
    cd /mnt
    cp config.xml /cf/conf/config.xml
    rm /tmp/config.xml
    shutdown -r now

  • What is the use of "Bridge With" option in LAN Interface configuration?

    Locked
    2
    0 Votes
    2 Posts
    2k Views
    H

    Have a look at http://pfsense.trendchiller.com/transparent_firewall.pdf

  • Why cannot FTP to pfsense file system?

    Locked
    3
    0 Votes
    3 Posts
    3k Views
    B

    Thanks Hoba
    My mistake that I was trying to logon using admin/pfsense and not roort/pfsense through secure ftp

    Regards
    Bassam

  • PPPoA

    Locked
    5
    0 Votes
    5 Posts
    11k Views
    J

    Yes, try to get PPPoE working, your performance will improve greatly under a heavy load.  Often times the routing tables on modems can't hold all that much, they tend to all but crash after a couple thousand states hit it.  My ISP says they offer PPPoA only.  Here is how you see if you can run PPPoE anyways.  Set your modem to transparent bridge, that makes it just a media converter basically.  Then just set your wan on pfsense to send your PPPoA user/pass.  My experience has been that it works just fine, althought I haven't tested it with that many ISPs.

  • Clear /reset rrd grphs

    Locked
    6
    0 Votes
    6 Posts
    5k Views
    G

    thanks a lot :D

  • 0 Votes
    1 Posts
    1k Views
    No one has replied
  • Using PFSense as server (raid 5)

    Locked
    4
    0 Votes
    4 Posts
    3k Views
    S

    Either that or FreeNAS (which would be my preferred solution).

  • Postfix/pfsense installation

    Locked
    3
    0 Votes
    3 Posts
    5k Views
    W

    Ive started on an Exim package, and although its far from complete its definitely very possible to add this. The only problem is, has Hoba has said, is how to handle the upgrading etc. which I havent even looked at just yet.

    Currently the package supports:

    Quotas per mailbox
    Subnets that are allowed to relay
    SMTP Auth (both client side and server side)
    Smarthost
    ClamAv
    SpamAssassin
    multiple domains

    and numerous other smaller settings. Its not at a point where I am comfortable with it as there is still too many settings that are hard coded and these settings should be configured via the web interface.

    It gets tricky when adding users though cos you will need to support aliases, forwarding and possibly store and forwarding. You also then need to decide whether you have to store the mail locally (requires some POP3 or IMAP server) or whether it should just act as a mailhub for an internal mail server(s).

  • Dropped WAN connection

    Locked
    4
    0 Votes
    4 Posts
    2k Views
    H

    Upgrade to the latest snapshot. There has been some dhclient updates that should fix that situation (see http://forum.pfsense.org/index.php/topic,2645.0.html ).

  • Range / List of IP for VPN

    Locked
    4
    0 Votes
    4 Posts
    2k Views
    P

    I think you will need to provide a small diagram with your setup….
    but read the info on this site http://www.firewall.cx/vlans-intro.php first

  • DST 2007

    Locked
    3
    0 Votes
    3 Posts
    3k Views
    M

    Thanks, hoba!

  • SMTP redirect

    Locked
    4
    0 Votes
    4 Posts
    2k Views
    A

    if you have a vlan switch make a vlan up on one of the nis and put the mail server there

  • MOVED: New forum request.

    Locked
    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • Pfsense crashing

    Locked
    5
    0 Votes
    5 Posts
    4k Views
    P

    ok i've setup pfsense to send the logs, i've installed syslog-ng on this linux machine, i'm just not sure how to set it up. This is what i've made the syslog-ng.conf

    # # Configuration file for syslog-ng under Debian # # attempts at reproducing default syslog behavior # the standard syslog levels are (in descending order of priority): # emerg alert crit err warning notice info debug # the aliases "error", "panic", and "warn" are deprecated # the "none" priority found in the original syslogd configuration is # only used in internal messages created by syslogd ###### # options options { long_hostnames(off); sync(0); }; src info_src { udp(514); }; destination info_dst { file(”/var/log/hosts/$HOST.log”); }; filter info_filter { level(info); }; log { source(info_src); filter(info_filter); destination(info_dst); }; options {         # disable the chained hostname format in logs         # (default is enabled)         chain_hostnames(0);         # the time to wait before a died connection is re-established         # (default is 60)         time_reopen(10);         # the time to wait before an idle destination file is closed         # (default is 60)         time_reap(360);         # the number of lines buffered before written to file         # you might want to increase this if your disk isn't catching with         # all the log messages you get or if you want less disk activity         # (say on a laptop)         # (default is 0)         #sync(0);         # the number of lines fitting in the output queue         log_fifo_size(2048);         # enable or disable directory creation for destination files         create_dirs(yes);         # default owner, group, and permissions for log files         # (defaults are 0, 0, 0600)         #owner(root);         group(adm);         perm(0640);         # default owner, group, and permissions for created directories         # (defaults are 0, 0, 0700)         #dir_owner(root);         #dir_group(root);         dir_perm(0755);         # enable or disable DNS usage         # syslog-ng blocks on DNS queries, so enabling DNS may lead to         # a Denial of Service attack         # (default is yes)         use_dns(no);         # maximum length of message in bytes         # this is only limited by the program listening on the /dev/log Unix         # socket, glibc can handle arbitrary length log messages, but -- for         # example -- syslogd accepts only 1024 bytes         # (default is 2048)         #log_msg_size(2048); #Disable statistic log messages. stats_freq(0); }; ###### # sources # all known message sources source s_all {         # message generated by Syslog-NG         internal();         # standard Linux log source (this is the default place for the syslog()         # function to send logs to)         unix-stream("/dev/log");         # messages from the kernel         file("/proc/kmsg" log_prefix("kernel: "));         # use the following line if you want to receive remote UDP logging messages         # (this is equivalent to the "-r" syslogd flag)         # udp(); }; ###### # destinations # some standard log files destination df_auth { file("/var/log/auth.log"); }; destination df_syslog { file("/var/log/syslog"); }; destination df_cron { file("/var/log/cron.log"); }; destination df_daemon { file("/var/log/daemon.log"); }; destination df_kern { file("/var/log/kern.log"); }; destination df_lpr { file("/var/log/lpr.log"); }; destination df_mail { file("/var/log/mail.log"); }; destination df_user { file("/var/log/user.log"); }; destination df_uucp { file("/var/log/uucp.log"); }; # these files are meant for the mail system log files # and provide re-usable destinations for {mail,cron,...}.info, # {mail,cron,...}.notice, etc. destination df_facility_dot_info { file("/var/log/$FACILITY.info"); }; destination df_facility_dot_notice { file("/var/log/$FACILITY.notice"); }; destination df_facility_dot_warn { file("/var/log/$FACILITY.warn"); }; destination df_facility_dot_err { file("/var/log/$FACILITY.err"); }; destination df_facility_dot_crit { file("/var/log/$FACILITY.crit"); }; # these files are meant for the news system, and are kept separated # because they should be owned by "news" instead of "root" destination df_news_dot_notice { file("/var/log/news/news.notice" owner("news")); }; destination df_news_dot_err { file("/var/log/news/news.err" owner("news")); }; destination df_news_dot_crit { file("/var/log/news/news.crit" owner("news")); }; # some more classical and useful files found in standard syslog configurations destination df_debug { file("/var/log/debug"); }; destination df_messages { file("/var/log/messages"); }; # pipes # a console to view log messages under X destination dp_xconsole { pipe("/dev/xconsole"); }; # consoles # this will send messages to everyone logged in destination du_all { usertty("*"); }; ###### # filters # all messages from the auth and authpriv facilities filter f_auth { facility(auth, authpriv); }; # all messages except from the auth and authpriv facilities filter f_syslog { not facility(auth, authpriv); }; # respectively: messages from the cron, daemon, kern, lpr, mail, news, user, # and uucp facilities filter f_cron { facility(cron); }; filter f_daemon { facility(daemon); }; filter f_kern { facility(kern); }; filter f_lpr { facility(lpr); }; filter f_mail { facility(mail); }; filter f_news { facility(news); }; filter f_user { facility(user); }; filter f_uucp { facility(uucp); }; # some filters to select messages of priority greater or equal to info, warn, # and err # (equivalents of syslogd's *.info, *.warn, and *.err) filter f_at_least_info { level(info..emerg); }; filter f_at_least_notice { level(notice..emerg); }; filter f_at_least_warn { level(warn..emerg); }; filter f_at_least_err { level(err..emerg); }; filter f_at_least_crit { level(crit..emerg); }; # all messages of priority debug not coming from the auth, authpriv, news, and # mail facilities filter f_debug { level(debug) and not facility(auth, authpriv, news, mail); }; # all messages of info, notice, or warn priority not coming form the auth, # authpriv, cron, daemon, mail, and news facilities filter f_messages {         level(info,notice,warn)             and not facility(auth,authpriv,cron,daemon,mail,news); }; # messages with priority emerg filter f_emerg { level(emerg); }; # complex filter for messages usually sent to the xconsole filter f_xconsole {     facility(daemon,mail)         or level(debug,info,notice,warn)         or (facility(news)                 and level(crit,err,notice)); }; ###### # logs # order matters if you use "flags(final);" to mark the end of processing in a # "log" statement # these rules provide the same behavior as the commented original syslogd rules # auth,authpriv.*                /var/log/auth.log log {         source(s_all);         filter(f_auth);         destination(df_auth); }; # *.*;auth,authpriv.none          -/var/log/syslog log {         source(s_all);         filter(f_syslog);         destination(df_syslog); }; # this is commented out in the default syslog.conf # cron.*                        /var/log/cron.log #log { #        source(s_all); #        filter(f_cron); #        destination(df_cron); #}; # daemon.*                        -/var/log/daemon.log log {         source(s_all);         filter(f_daemon);         destination(df_daemon); }; # kern.*                          -/var/log/kern.log log {         source(s_all);         filter(f_kern);         destination(df_kern); }; # lpr.*                          -/var/log/lpr.log log {         source(s_all);         filter(f_lpr);         destination(df_lpr); }; # mail.*                          -/var/log/mail.log log {         source(s_all);         filter(f_mail);         destination(df_mail); }; # user.*                          -/var/log/user.log log {         source(s_all);         filter(f_user);         destination(df_user); }; # uucp.*                          /var/log/uucp.log log {         source(s_all);         filter(f_uucp);         destination(df_uucp); }; # mail.info                      -/var/log/mail.info log {         source(s_all);         filter(f_mail);         filter(f_at_least_info);         destination(df_facility_dot_info); }; # mail.warn                      -/var/log/mail.warn log {         source(s_all);         filter(f_mail);         filter(f_at_least_warn);         destination(df_facility_dot_warn); }; # mail.err                        /var/log/mail.err log {         source(s_all);         filter(f_mail);         filter(f_at_least_err);         destination(df_facility_dot_err); }; # news.crit                      /var/log/news/news.crit log {         source(s_all);         filter(f_news);         filter(f_at_least_crit);         destination(df_news_dot_crit); }; # news.err                        /var/log/news/news.err log {         source(s_all);         filter(f_news);         filter(f_at_least_err);         destination(df_news_dot_err); }; # news.notice                    /var/log/news/news.notice log {         source(s_all);         filter(f_news);         filter(f_at_least_notice);         destination(df_news_dot_notice); }; # *.=debug;\ #        auth,authpriv.none;\ #        news.none;mail.none    -/var/log/debug log {         source(s_all);         filter(f_debug);         destination(df_debug); }; # *.=info;*.=notice;*.=warn;\ #        auth,authpriv.none;\ #        cron,daemon.none;\ #        mail,news.none          -/var/log/messages log {         source(s_all);         filter(f_messages);         destination(df_messages); }; # *.emerg                        * log {         source(s_all);         filter(f_emerg);         destination(du_all); }; # daemon.*;mail.*;\ #        news.crit;news.err;news.notice;\ #        *.=debug;*.=info;\ #        *.=notice;*.=warn      |/dev/xconsole log {         source(s_all);         filter(f_xconsole);         destination(dp_xconsole); };

    the problem is when i run it i get this

    syslog-ng -f /etc/syslog-ng/syslog-ng.conf
    syntax error at 17

    where this is line 17:

    src info_src { udp(514); };
  • PfSense Newb here, please help

    Locked
    3
    0 Votes
    3 Posts
    2k Views
    Y

    You need to make sure you created the appropriate Virtual IPs. Also you will need Firewall rules to allow the traffic.

  • Earlyshellcmd

    Locked
    1
    0 Votes
    1 Posts
    2k Views
    No one has replied
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.