Hey,
I have got some settings problem on Pfsense failover:
1.What I have: 1 soekris, 1 router, 2 WANs(one is static IP,the other is
PPPoe).
2.I connected the static IP to the ETH1 of the soekris and set it in
the WAN interface,and it is working fine,but now I need to set a failover,
let
2.I connected the static IP to the ETH1 of the soekris and set it in
the WAN interface,and it is working fine,but now I need to set a failover,
let the pfsense prefers WAN2 when WAN fails.
3.I have set the PPPoe in the router,and it works,I connected the router
the ETH2 interface in the
Hey,
I have tried this,but seems the there is something wrong with the
Failover settings.
After this setting, in the load balancer-pool-edit,what monitor IP
should I put for WAN2?or 192.168.1.1?or some IPs just like
www.google.com's?
Best Regards,
Abel
Seth Mos wrote:
2.I connected the
On 13/12/09 05:07, Jeppe Øland wrote:
Just stumbled over this:
MSI Industrial WindBOXII
http://www.logicsupply.com/products/ms_9a25
Not cheap - but it's got everything in a nice pre-packaged box.
nice! it has an Intel NIC. not sure what options there are for mini-PCIe
cards with gigabit
Today I had an issue where the pfsense firewall (1.2.3RC3) could not
access the remote syslog on another server because of a network fault
(dead switch).
The end result of this was the firewall stopped responding after
behaving intermittently. I imagine the firewall buffered the messages
On 12/12/09 16:19, Nenhum_de_Nos wrote:
I couldn't upgrade from webui from 1.2.3-RC1 to Release
I upgraded a 1.2.3-RC1 to -Release this morning, uploading the full
update via web ui and it just worked (TM), so you must have been
unlucky :-/
On 14/12/09 14:13, Duncan Hall wrote:
Today I had an issue where the pfsense firewall (1.2.3RC3) could not
access the remote syslog on another server because of a network fault
(dead switch).
The end result of this was the firewall stopped responding after
behaving intermittently. I imagine
Paul Mansfield wrote:
On 14/12/09 14:13, Duncan Hall wrote:
Today I had an issue where the pfsense firewall (1.2.3RC3) could not
access the remote syslog on another server because of a network fault
(dead switch).
The end result of this was the firewall stopped responding after
behaving
On Sun, Dec 13, 2009 at 7:49 PM, Ugo Bellavance u...@lubik.ca wrote:
Hi,
http://doc.pfsense.org/index.php/NanoBSD_on_WRAP
Has someone done the first step what would be kind enough to put the
resulting image available for download? I worked a few hours on this before
discovering that
On Sun, Dec 13, 2009 at 7:49 PM, Ugo Bellavance u...@lubik.ca wrote:
and I don't have much time to setup a separate freebsd/pfsense box to do the
changes.
A quickie VMware or VirtualBox image will do just fine. Takes about
10 minutes to install a minimal freebsd image. Add a network
interface,
Wow, it works. Thank you so much. When you came to Brazil you'll have a
place to stay.
2009/12/11 Jim Pingle li...@pingle.org
[Please try not to top post, especially when others in the thread are
not top posting]
On 12/11/2009 6:28 PM, Nathaniel Simch de Morais wrote:
2009/12/11 Jim
We have a plugin that is acting up quite a bit suddenly (snort)
on reboot the system works for a few minutes - but then nothing
We cannot gain access to the web interface @ all.
Does anyone know how to disable a plugin via ssh ?
We get ssh access for about 4 minutes on a reboot - then it
On Mon, Dec 14, 2009 at 4:07 PM, Glenn Kelley gl...@typo3usa.com wrote:
We have a plugin that is acting up quite a bit suddenly (snort)
on reboot the system works for a few minutes - but then nothing
We cannot gain access to the web interface @ all.
Does anyone know how to disable a plugin
You are a life saver - thank you .
On Dec 14, 2009, at 4:21 PM, Scott Ullrich wrote:
On Mon, Dec 14, 2009 at 4:07 PM, Glenn Kelley gl...@typo3usa.com wrote:
We have a plugin that is acting up quite a bit suddenly (snort)
on reboot the system works for a few minutes - but then nothing
We
Sawadeekap
After a failed upgrade from 1.2.2 to 1.2.3, I made a fresh install from
pfSense Full, installed SpamD Package, but it didn't forward any Mails
to the internal Exchange Server.
I used the default settings from the package, added my internal exchange
server (172.22.1.x), and some
Just stumbled over this:
MSI Industrial WindBOXII
http://www.logicsupply.com/products/ms_9a25
Not cheap - but it's got everything in a nice pre-packaged box.
nice! it has an Intel NIC.
As for the PCIe wireless card: it's a MSI brand card, using a Ralink NIC.
(MS-6894, Ralink chip:
Em 14-12-2009 21:20, Fabian Abplanalp escreveu:
Sawadeekap
After a failed upgrade from 1.2.2 to 1.2.3, I made a fresh install
from pfSense Full, installed SpamD Package, but it didn't forward any
Mails to the internal Exchange Server.
I used the default settings from the package, added my
On 12/15/09 1:03 AM, zhushazang wrote:
Em 14-12-2009 21:55, zhushazang escreveu:
Sorry guy, i need advise u about a this change in permission.
I really don't know if a process like that with root permitions are
secure.
Then, think better before make this change in your system.
att
Yes,
Hi,
I have this configuration:
WAN --- 1.2.3.0/26 || --- DMZ 192.168.1.0/24
| pfsense V1.2.2 |
WAN2 --- 3.2.1.0/25 || --- LAN 10.1.1.0/24
I have to be able to connect from the LAN to the DMZ through the public IP.
I could convince my
Forward a port range and specify it manually in your client or use
passive mode.
On 2009-12-13 11:30 PM, Koray AGAYA wrote:
Hi,
I use FTPES -FTP over TLS/SSL and I want use NAT but I didnt found
(FTPES -FTP over TLS/SSL ) ports ? Can You help me please ? Which ports
can I use for NAT
I suggest a seperate DNS for LAN clients
On Tue, Dec 15, 2009 at 8:07 AM, charlyc...@yahoo.com.ar
charlyc...@yahoo.com.ar wrote:
Hi,
I have this configuration:
WAN --- 1.2.3.0/26 || --- DMZ 192.168.1.0/24
| pfsense V1.2.2 |
WAN2 --- 3.2.1.0/25 |
charlyc...@yahoo.com.ar schreef:
Hi,
I have this configuration:
WAN --- 1.2.3.0/26 || --- DMZ 192.168.1.0/24
| pfsense V1.2.2 |
WAN2 --- 3.2.1.0/25 || --- LAN 10.1.1.0/24
I have to be able to connect from the LAN to the DMZ through the
22 matches
Mail list logo
