bandwidthd or darkstats packages might help. they show download/upload
by IP address.
sai
On 2/26/08, Bosco [EMAIL PROTECTED] wrote:
Hi all,
I am using pfSense solution for a while (about 6 months) - version
1.2 with 1 LAN + 3 WANs - and sometimes the Download or Upload traffic
Got an issue with Outbound NAT.
I have 2 interfaces, LAN and WAN.
WAN has an IP assigned to its interface, as well as an additional 4
virtual IPs for a total of 5 IP addresses which are used in various
inbound NAT rules. I have turned on manual outbound NAT, as I need my
outgoing SMTP traffic
Ermal Luçi wrote:
Log to pfsense though ssh.
pkg_add -r rate
than: rate -i {interface_to_monitor} -R (or similar) it should have
even an option to do ranking to show your most hungry host.
Anyone found the switch to see that? I tried -A, but then it asks for a
-c class, and when I use it,
Hello! I have an IPSEC tunnel configured between a mobile client running
TheGreenBow and a fresh installation of pfSense 1.2-RELEASE. The tunnel comes
up as expected yet I am unable to ping any devices on the remote subnet. There
is not a firewall tab for rules on IPsec tunnels. Where should I
I've got a dual-wan setup and I want to cause traffic between an internal
machine, and external machine to occur over WAN2 (I could use source or
destination as criteria). Both public IPs would share a gateway so I've put
a NAT device on WAN2 and connected the modem to it so now both WAN ports are
I have a dual wan (not through choice only legacy) , the issue is that
an openvpn connection needs to connect via the secondary wan connection
(192.168.9.1 == 192.168.9.2) which is not the default route for the
network see below (default route is 192.168.0.1 from pfsense).
Basically we need to
Hello,
I've noticed those lines in syslogs after an ATA
adapter rebooted while it was connected to an optional
interface:
php: : Not a valid interface action
php: : Processing -
php: : Not a valid interface action
php: : Processing start -
php: : Hotplug event detected for vr2 but ignoring
Hey guys - I am a happy camper with pfsense and recently upgraded to 1.2 and
have no issues to report so far.
I am trying to hook up two pfsense boxes with IPSEC site to site
It looks like that it needs a public ip address to create a tunnel. I could
try and get public IP address at one
Hello,
After upgrading to release 1.2 of PFsense we are not able to set up any
IPsec connection anymore. No errors in the logs of Pfsense. But wenn i put
the upgrade (PFsense 1.2 RC3) over the not working 1.2 version, it all works
again.? So why doesn't the IPsec tunnels work in the 1.2
the fact that the setup works,but only if you start a packet capture
(using the last option in the pfsense menu?) is something strange.
possibly something wrong in config (maybe routing or gateway?).
a lot of small and hard to catch bugs have been fixed in 1.2RELEASE
and so i would go for a
So then go on and use OpenVPN site-to-site... it works woth 2 dynamic
IPs...
Dynamic IPs for IPSec will be in 1.3...
Regards,
Martin
Von: Anil Garg [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 28. Februar 2008 04:51
An: support@pfsense.com
Betreff: [pfSense Support] IPSEC
11 matches
Mail list logo
