The pfSense Store

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - vsaad

Pages: [1]
1
Installation and Upgrades / After update - weird errors on systemlog
« on: November 20, 2017, 04:28:51 pm »
Hey, after the update this pfs started to play up. I googled but couldn't find any info.

It's coming up a error constantly in the systemlog (Image attached).

I also can't see any firewall logs.

I've done
pkg upgrade -f after the updates and I'm still having the same issue.


Anyone have any clue how to fix this?

[2.4.0-RELEASE][root@fw.next.local]/root: cat /etc/crontab
# /etc/crontab - root's crontab for FreeBSD
#
# $FreeBSD$
#
SHELL=/bin/sh
PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin
#
#minute hour    mday    month   wday    who     command
#
#*/5    *       *       *       *       root    /usr/libexec/atrun
#
# Save some entropy so that /dev/random can re-seed on boot.
#*/11   *       *       *       *       operator /usr/libexec/save-entropy
#
# Rotate log files every hour, if necessary.
#0      *       *       *       *       root    newsyslog
#
# Perform daily/weekly/monthly maintenance.
#1      3       *       *       *       root    periodic daily
#15     4       *       *       6       root    periodic weekly
#30     5       1       *       *       root    periodic monthly
#
# Adjust the time zone if the CMOS clock keeps local time, as opposed to
# UTC time.  See adjkerntz(8) for details.
#1,31   0-5     *       *       *       root    adjkerntz -a
#
# pfSense specific crontab entries
# Created: November 3, 2017, 1:30 pm
#

1,31    0-5     *       *       *       root    /usr/bin/nice -n20 adjkerntz -a
1       3       1       *       *       root    /usr/bin/nice -n20 /etc/rc.update_bogons.sh
*/60    *       *       *       *       root    /usr/bin/nice -n20 /usr/local/sbin/expiretable -v -t 3600 sshlockout
*/60    *       *       *       *       root    /usr/bin/nice -n20 /usr/local/sbin/expiretable -v -t 3600 webConfiguratorlockout
1       1       *       *       *       root    /usr/bin/nice -n20 /etc/rc.dyndns.update
*/60    *       *       *       *       root    /usr/bin/nice -n20 /usr/local/sbin/expiretable -v -t 3600 virusprot
30      12      *       *       *       root    /usr/bin/nice -n20 /etc/rc.update_urltables
0       0       *       *       *       root    /usr/bin/nice -n20 /usr/local/etc/rc.d/squidGuard_logrotate
0       0       *       *       *       root    /usr/local/sbin/squid -k rotate -f /usr/local/etc/squid/squid.conf
15      0       *       *       *       root    /usr/local/pkg/swapstate_check.php
*/5     *       *       *       *       root    /usr/bin/nice -n20 /usr/local/bin/php -f /usr/local/pkg/snort/snort_check_cron_misc.inc
5       0,12    *       *       *       root    /usr/bin/nice -n20 /usr/local/bin/php -f /usr/local/pkg/snort/snort_check_for_rule_updates.php
*/1     *       *       *       *       root    /usr/local/pkg/servicewatchdog_cron.php
1       0       *       *       *       root    /usr/bin/nice -n20 /etc/rc.update_pkg_metadata
*/60    *       *       *       *       root    /usr/local/bin/perl /usr/local/www/lightsquid/lightparser.pl today
15      0       *       *       *       root    /usr/local/bin/perl /usr/local/www/lightsquid/lightparser.pl yesterday
#
# If possible do not add items to this file manually.
# If done so, this file must be terminated with a blank line (e.g. new line)
#

[2.4.0-RELEASE][root@fw.next.local]/root:

2
Portuguese / Erro no cron - Invalid argument.
« on: November 05, 2017, 07:03:37 pm »
Um dos PFS começou "do nada", acredito na possibilidade de pau depois da atualização, alguem ja viu isso?

Nada foi adicionado manualmente no crontab.


[2.4.0-RELEASE][root@fw.next.local]/root: cat /etc/crontab
# /etc/crontab - root's crontab for FreeBSD
#
# $FreeBSD$
#
SHELL=/bin/sh
PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin
#
#minute hour    mday    month   wday    who     command
#
#*/5    *       *       *       *       root    /usr/libexec/atrun
#
# Save some entropy so that /dev/random can re-seed on boot.
#*/11   *       *       *       *       operator /usr/libexec/save-entropy
#
# Rotate log files every hour, if necessary.
#0      *       *       *       *       root    newsyslog
#
# Perform daily/weekly/monthly maintenance.
#1      3       *       *       *       root    periodic daily
#15     4       *       *       6       root    periodic weekly
#30     5       1       *       *       root    periodic monthly
#
# Adjust the time zone if the CMOS clock keeps local time, as opposed to
# UTC time.  See adjkerntz(8) for details.
#1,31   0-5     *       *       *       root    adjkerntz -a
#
# pfSense specific crontab entries
# Created: November 3, 2017, 1:30 pm
#

1,31    0-5     *       *       *       root    /usr/bin/nice -n20 adjkerntz -a
1       3       1       *       *       root    /usr/bin/nice -n20 /etc/rc.update_bogons.sh
*/60    *       *       *       *       root    /usr/bin/nice -n20 /usr/local/sbin/expiretable -v -t 3600 sshlockout
*/60    *       *       *       *       root    /usr/bin/nice -n20 /usr/local/sbin/expiretable -v -t 3600 webConfiguratorlockout
1       1       *       *       *       root    /usr/bin/nice -n20 /etc/rc.dyndns.update
*/60    *       *       *       *       root    /usr/bin/nice -n20 /usr/local/sbin/expiretable -v -t 3600 virusprot
30      12      *       *       *       root    /usr/bin/nice -n20 /etc/rc.update_urltables
0       0       *       *       *       root    /usr/bin/nice -n20 /usr/local/etc/rc.d/squidGuard_logrotate
0       0       *       *       *       root    /usr/local/sbin/squid -k rotate -f /usr/local/etc/squid/squid.conf
15      0       *       *       *       root    /usr/local/pkg/swapstate_check.php
*/5     *       *       *       *       root    /usr/bin/nice -n20 /usr/local/bin/php -f /usr/local/pkg/snort/snort_check_cron_misc.inc
5       0,12    *       *       *       root    /usr/bin/nice -n20 /usr/local/bin/php -f /usr/local/pkg/snort/snort_check_for_rule_updates.php
*/1     *       *       *       *       root    /usr/local/pkg/servicewatchdog_cron.php
1       0       *       *       *       root    /usr/bin/nice -n20 /etc/rc.update_pkg_metadata
*/60    *       *       *       *       root    /usr/local/bin/perl /usr/local/www/lightsquid/lightparser.pl today
15      0       *       *       *       root    /usr/local/bin/perl /usr/local/www/lightsquid/lightparser.pl yesterday
#
# If possible do not add items to this file manually.
# If done so, this file must be terminated with a blank line (e.g. new line)
#

[2.4.0-RELEASE][root@fw.next.local]/root:

3
Portuguese / [Resolvido]Squid+SSL = Não "Cacheia"
« on: October 09, 2017, 12:01:01 am »
Fala Galera, beleza?


To com o Squid3 com interceptação SSL, certificado tudo "funcionando".

Porém no Tail access.log não aparece 1 hit, só TCP_MISS/200 e TCP_TUNNEL/200. Eu usei o GREP p filtrar se dava algum hit, mas sem sucesso.

Não uso squidguardian ou e2guardian nesse cenario, somente squid( a Internet vai ser toda bloqueada e liberado somente alguns sites.) E poucas maquinas terão acesso ilimitado.

Uso WPAD.

Aumentei o tamanho do cache tanto em memoria qto em disco para ver se melhorava, mas ainda continua.
Já pesquisei a lot e não achei nada atual sobre o assunto.



1507523173.628  40359 192.168.15.108 TCP_MISS/200 594 GET https://142-trouter-easia-a.drip.trouter.io/socket.io/1/xhr-polling/5705f31c0b79b686-492b61e34b3d06eb? - HIER_DIRECT/52.229.169.170 text/plain
1507523173.628  40422 192.168.15.69 TCP_MISS/200 594 GET https://53-trouter-easia-a.drip.trouter.io/socket.io/1/xhr-polling/ff222b61dbf3572f-413906146202beed? - HIER_DIRECT/52.229.169.126 text/plain
1507523173.637  40224 192.168.15.62 TCP_MISS/200 602 GET https://237-trouter-easia-a.drip.trouter.io/socket.io/1/xhr-polling/7150e5ee605d45aa-41e8da85985ede04? - HIER_DIRECT/52.229.169.152 text/plain
1507523173.739  40615 192.168.15.54 TCP_MISS/200 594 GET https://68-trouter-easia-a.drip.trouter.io/socket.io/1/xhr-polling/28364499bafc8538-46b2fa2c8e49a6fa? - HIER_DIRECT/52.229.175.208 text/plain
1507523173.940   6664 192.168.15.54 TCP_TUNNEL/200 6983 CONNECT browser.pipe.aria.microsoft.com:443 - HIER_DIRECT/13.78.93.8 -
1507523173.945   4279 192.168.15.54 TCP_TUNNEL/200 18655 CONNECT skyapi.onedrive.live.com:443 - HIER_DIRECT/157.55.109.224 -
1507523173.945   7278 192.168.15.54 TCP_TUNNEL/200 10930 CONNECT api.onedrive.com:443 - HIER_DIRECT/204.79.197.213 -
1507523174.764  40169 192.168.15.142 TCP_MISS/200 498 GET https://121-trouter-easia-a.drip.trouter.io/socket.io/1/xhr-polling/d0705fce2761d23a-4ad39080c0834955? - HIER_DIRECT/52.229.170.40 text/plain
1507523174.955  40215 192.168.15.82 TCP_MISS/200 498 GET https://31-trouter-easia-a.drip.trouter.io/socket.io/1/xhr-polling/e6ed11886f6318dd-4b754508fe9f07cb? - HIER_DIRECT/52.229.173.7 text/plain


Ambiente:

Network: 192.168.15.0/24
~150 PCS



4
General Questions / [SOLVED]PFSense clock doesn't update
« on: September 27, 2017, 10:37:53 pm »
Hey, That's anyone having issues with the clock?

I updated my PFSense for new version(the hardware is new as well, just restored backup).
Everything running fine, just the clock is not updating right.

I changed (General Setup) the NTP server for au.pool.ntp.org (australian), has set the timezone as well, and the clock still showing wrong.

Cheers.


5
Portuguese / [BUG Identificado]2.3.4 on XenServer7 Perdendo pacote
« on: September 12, 2017, 09:24:19 pm »
Fala pessoal,

Editei para deixar documentado no forum em portugues.

-
O Hardware do PFS travou geral, eu fiz uma nova instalacao em uma VM e voltei um backup de 3 dias atras. está funcionando, porém alguns sites não estao indo mto bem.
Servidor Windows provendo DHCP e DNS para os clientes.
A Interface de rede do dominio windows ta configurada estatica e apontando dns para ele mesmo. (Não quis mexer pois estava funcionando antes)

Liberei geral as regras da  LAN, e to testando por fora do squid.

Hypervisor - XenServer7
PFS WAN - 192.168.16.2 (ISP ROUTER 192.168.16.1)
PFS LAN - 192.168.15.2

Liguei um laptop antes do firewall e funcionou normal bem.

O tracert para o site da amazon ta assim

Tracing route to us-east-1.console.aws.amazon.com [54.239.31.83]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.15.2
  2     2 ms     2 ms     1 ms  192.168.16.1
  3     6 ms     6 ms     6 ms  bundle-ether1051-378.ken-edge902.sydney.telstra.
net [144.130.164.121]
  4     7 ms     5 ms     6 ms  bundle-ether14.ken-core10.sydney.telstra.net [20
3.50.11.96]
  5     6 ms     8 ms     5 ms  bundle-ether1.pad-gw11.sydney.telstra.net [203.5
0.6.61]
  6     8 ms     6 ms     6 ms  bundle-ether1.sydp-core04.sydney.reach.com [203.
50.13.90]
  7   155 ms   155 ms   155 ms  i-52.tlot-core02.bx.telstraglobal.net [202.84.13
7.101]
  8   150 ms   150 ms   150 ms  i-0-0-0-6.eqla01.bi.telstraglobal.net [202.40.14
9.226]
  9   153 ms   150 ms   149 ms  los-brdr-01.inet.qwest.net [63.235.40.45]
 10     *        *        *     Request timed out.
 11   216 ms   216 ms   216 ms  72.165.86.74
 12   242 ms   240 ms   308 ms  54.239.109.218
 13   234 ms   235 ms   235 ms  54.239.111.107
 14   233 ms   234 ms   234 ms  205.251.244.233
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.

Eu tava pensando em DNS, mas o nslookup ta vindo bem e rapido.


EDIT: Subi uma instalação limpa do PFS ligado no mesmo ISP ROUTER(WAN) e com ip diferente na LAN, Setei uma estacao com ele de gateway e o problema persiste, to achando isso muito estranho.

EDIT2: Coloquei o ISP Router(Lancom 1781AW) como gateway da rede, e agora esta esta indo bem... Estou suspeitando de algo com o XenServer com o PFS, pois as duas instalações que testei, foram em hardwares diferentes mas usando o mesmo HyperV.

6
Portuguese / [RESOLVIDO]DNS por VPN?
« on: July 27, 2017, 12:47:01 am »
Senhores,

A empresa tem um parceiro que usa VPN(PPTP) para utilizar um sistema que eh WEB BASED.

Normalmente o sistema eh accessado por http://websystem e nao tem acesso externo.

Setamos o cliente para accessar utilizando http://192.168.1.1 ao inves de http://websystem

Porém quando eles geram algum tipo de relatorio no site, o patch aponta para http://websystem/report ao inves de http://192.168.1.1 e nao funciona da VPN.

Teria alguma solucao na infra ao inves de mexer com o dev do websystem?

Eu não tenho acesso as maquinas dos clientes, entao eu tenho que pedir para o T.I deles fazer qualquer modificacao necessaria.

Qual ideia seria mais plausivel? Criar entradas manuais nas maquinas que utilizam? talvez no gateway deles? (Fortinet)

7
Portuguese / [RESOLVIDO]Alarme SNMP Linux Meminfo
« on: March 24, 2017, 12:31:42 am »
To usando o PRTG como SNMP monitor, e hoje ele comecou a me alertar sobre Memoria available no pfsense.

Olhando no dashboard, ele me mostra usage de 19%, o que eh normal, Agora nao sei se o sensor SNMP que ta dando algum bug, ou se realmente tenho q me preucupar com o PFSENSE

Alguem ja viu algo do genero?

Screenshots:

http://imgur.com/a/WZaXn

EDIT

Achei esse link (ENGLISH), mas eh de 2010.
https://kb.paessler.com/en/topic/9973-how-to-correctly-monitor-linux-real-memory-usage

8
Portuguese / [SOLVED]WebGui sem acesso mesmo com pfctl -d
« on: March 15, 2017, 12:01:17 am »
Setei um PFS 2.3.2 na correria e agora nao to conseguindo mais acesso ao webgui, tive um problema desse no passado e tive que refazer a reinstalacao do zero para resolver.

Tentativas sem sucesso:
Tentei o pfctl -d
Tentei usar o Reset WebConfigurator no menu, tentei reset php tambem.
O lighttpd ta running
tentei matar o php killall -9 php; killall -9 lighttpd; /etc/rc.restart_webgui  Sem sucesso tambem.

Alguem teria alguma ultima tentativa antes de eu dar o factory reset?
 

9
Portuguese / Log Mailreport
« on: May 16, 2013, 01:59:35 pm »
Boa Tarde !

Tenho uma duvida em relação ao mailreport, eu estava efetuando testes nele e acrescentei o log lighttpd... imaginava que talvez daria para eu enviar o relatorio do lightsquid por email... mas enfim, não deu certo..

Quando olhei o email vi esse log, e me preucupei com os avisos Warning.... nem imagino o que seja, será que pode prejudicar o funcionamento?

Code: [Select]
Current report: Relatório PFSense

Log output: lighttpd.error (lighttpd.error.log)
2013-05-15 16:07:49: (connections.c.137) (warning) close: 27 Connection reset by peer
2013-05-15 16:40:45: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1
2013-05-15 16:40:45: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1
2013-05-15 17:19:39: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1
2013-05-15 17:19:39: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1
2013-05-15 17:22:56: (connections.c.137) (warning) close: 18 Connection reset by peer
2013-05-15 17:23:03: (connections.c.137) (warning) close: 19 Connection reset by peer
2013-05-15 17:23:49: (connections.c.137) (warning) close: 15 Connection reset by peer
2013-05-15 17:39:42: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1
2013-05-15 17:39:42: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1
2013-05-15 18:46:42: (connections.c.305) SSL: 1 error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request
2013-05-15 19:19:10: (mod_fastcgi.c.2543) unexpected end-of-file (perhaps the fastcgi process died): pid: 48380 socket: unix:/tmp/php-fastcgi.socket-1
2013-05-15 19:19:10: (mod_fastcgi.c.3329) response not received, request sent: 866 on socket: unix:/tmp/php-fastcgi.socket-1 for /sgerror.php?url=403%20&a=192.168.0.176&n=&i=&s=default&t=blk_BL_adv&u=http://rad.msn.com/ADSAdClient31.dll?GetAd=&PG=IMBZTC, closing connection
2013-05-15 19:19:10: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1
2013-05-15 19:19:10: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1
2013-05-15 19:19:59: (connections.c.137) (warning) close: 19 Connection reset by peer
2013-05-15 19:21:54: (connections.c.137) (warning) close: 13 Connection reset by peer
2013-05-15 19:23:14: (connections.c.137) (warning) close: 14 Connection reset by peer
2013-05-15 19:23:38: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1
2013-05-15 19:23:38: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1
2013-05-15 19:25:45: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1
2013-05-15 19:25:45: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1
2013-05-15 19:28:45: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1
2013-05-15 19:28:45: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1
2013-05-15 19:30:35: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1
2013-05-15 19:30:35: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1
2013-05-15 19:33:14: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1
2013-05-15 19:33:14: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1
2013-05-15 19:33:49: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-0
2013-05-15 19:33:49: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 2
2013-05-15 19:33:55: (connections.c.137) (warning) close: 15 Connection reset by peer
2013-05-15 19:36:01: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1
2013-05-15 19:36:01: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1
2013-05-15 19:37:09: (connections.c.137) (warning) close: 14 Connection reset by peer
2013-05-15 19:37:52: (connections.c.137) (warning) close: 17 Connection reset by peer
2013-05-15 19:38:12: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1
2013-05-15 19:38:12: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1
2013-05-15 19:41:34: (mod_fastcgi.c.2543) unexpected end-of-file (perhaps the fastcgi process died): pid: 29345 socket: unix:/tmp/php-fastcgi.socket-1
2013-05-15 19:41:34: (mod_fastcgi.c.3329) response not received, request sent: 1015 on socket: unix:/tmp/php-fastcgi.socket-1 for /sgerror.php?url=403%20&a=192.168.0.205&n=&i=&s=default&t=blk_BL_movies&u=http://img.video.globo.com/180x101/2574324.jpg, closing connection
2013-05-15 19:41:34: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1
2013-05-15 19:41:34: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1
2013-05-15 19:44:10: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1
2013-05-15 19:44:10: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1
2013-05-15 19:46:21: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1
2013-05-15 19:46:21: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1
2013-05-15 19:48:54: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1
2013-05-15 19:48:54: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1
2013-05-15 20:10:59: (connections.c.137) (warning) close: 17 Connection reset by peer
2013-05-15 20:10:59: (connections.c.137) (warning) close: 19 Connection reset by peer

10
Portuguese / Monitorar cache do Squid com Navegador [TIMEOUT NO LOGIN]
« on: March 02, 2011, 12:38:19 pm »
Fiz o procedimento que tem no forum, mas não ta rolando, na hora que pede o usuario e senha, eu coloco ele demora e da TIMEOUT.

o usuario e senha é do web ou é do root?

11
Portuguese / É possivel Double Load Balance ?
« on: February 09, 2011, 11:47:34 am »
Boa Tarde.

Ja li diversos posts e ja googlei bastante o assunto, mas nao achei nada exatamente o que eu queria saber...

Tenho 1 PFS instalado na Matriz e tenho um Ubuntu na filial(onde vou por PFS tb)

Só que o seguinte, Hoje eu tenho 1 internet de cada lado, e tenho 1 REDE IP (VPN DE OPERADORA) interligando os dois, porém ele é ligado diretamente no switch.

Eu quero fazer um Load Balance no LINK VPN e um LOAD BALANCE na internet ficando assim:

MATRIZ
1 SPEEDY - LOAD BALANCE 1
1 VIRTUA - LOAD BALANCE 1
-
1 VPN TELEFONICA - LOAD BALANCE2
1 VPN EMBRATEL - LOAD BALANCE2


1. Gostaria de saber se isso é possivel com o PFSENSE?
2. Eu posso substituir os dois vpns por links comuns e eu fechar a vpn diretamente pelo openvpn do PFS?


3. Tem como deixar o SPEEDY BUSINESS para conexao de entrada, e deixar o virtua somente para navegar??
Agradeço desde ja.

Pages: [1]