Balancea Excelente, pero no logro abrir los puertos
Hola buenos dias, perdon si este tema ya ha sido planteado, la verdad soy bastante nuevo en el foro ( y en ubiquiti) he buscado mucho antes de presentar esta situacion, tengo un router edge x con el mismo he realizado el balanceo de 3 lineas wan (2 adsl de 10 mb y 2 mb de subida, y un servicio dedicado de 4mb) hasta este punto, el balanceo es correcto, lo he realizado a traves del wizard, el problema se me plantea a la hora de querer abrir los puertos del router para que pasen al mikrotik que tengo para control de clientes, dado que todos los puertos que anteriormente tenia abiertos sin ningun problema, ahora estan cerrados ,,, y lo unico que he logrado hasta el momento es ver mi router edge cuando pongo mi ip publica en el navegador
firewall { all-ping enable
broadcast-ping disable
group {
network-group PRIVATE_NETS {
network 192.168.0.0/16
network 172.16.0.0/12
network 10.0.0.0/8
}
}
ipv6-receive-redirects disable
ipv6-src-route disable
ip-src-route disable
log-martians disable
modify balance {
rule 10 {
action modify
description "do NOT load balance lan to lan"
destination {
group {
network-group PRIVATE_NETS
}
}
modify {
table main
}
}
rule 20 {
action modify
description "do NOT load balance destination public address"
destination {
group {
address-group ADDRv4_eth0
}
}
modify {
table main
}
}
rule 30 {
action modify
description "do NOT load balance destination public address"
destination {
group {
address-group ADDRv4_eth1
}
}
modify {
table main
}
}
rule 40 {
action modify
description "do NOT load balance destination public address"
destination {
group {
address-group ADDRv4_eth2
}
}
modify {
table main
}
}
rule 70 {
action modify
modify {
lb-group G
}
}
}
name WAN_IN {
default-action accept
description "WAN to internal"
rule 10 {
action accept
description "Allow established/related"
state {
established enable
related enable
}
}
rule 20 {
action accept
description scriptcase
destination {
port 8090
}
log disable
protocol tcp
}
rule 30 {
action accept
description "Drop invalid state"
log disable
protocol tcp_udp
}
}
name WAN_LOCAL {
default-action drop
description "WAN to router"
rule 10 {
action accept
description "Allow established/related"
state {
established enable
related enable
}
}
rule 20 {
action accept
description "Drop invalid state"
log disable
protocol tcp_udp
}
}
receive-redirects disable
send-redirects enable
source-validation disable
syn-cookies enable
}
interfaces {
ethernet eth0 {
address xxxxx/29
description WAN
duplex auto
firewall {
in {
name WAN_IN
}
local {
name WAN_LOCAL
}
}
speed auto
}
ethernet eth1 {
address xxxxx/24
description "WAN 2"
duplex auto
firewall {
in {
name WAN_IN
}
local {
name WAN_LOCAL
}
}
speed auto
}
ethernet eth2 {
address xxxxx/24
description "WAN 3"
duplex auto
firewall {
in {
name WAN_IN
}
local {
name WAN_LOCAL
}
}
speed auto
}
ethernet eth3 {
duplex auto
speed auto
}
ethernet eth4 {
duplex auto
speed auto
}
loopback lo {
}
switch switch0 {
address xxxxx/24
description Local
firewall {
in {
modify balance
}
}
switch-port {
interface eth4 {
}
}
}
}
load-balance {
group G {
interface eth0 {
}
interface eth1 {
}
interface eth2 {
}
}
}
port-forward {
auto-firewall enable
hairpin-nat enable
lan-interface eth4
rule 1 {
description ""
forward-to {
address 192.168.168.2
port 8090
}
original-port 8090
protocol tcp_udp
}
wan-interface eth0
}
protocols {
static {
route 0.0.0.0/0 {
next-hop xxxxx {
}
next-hop 192.168.1.1 {
}
next-hop 192.168.2.1 {
}
}
}
}
service {
dns {
forwarding {
cache-size 150
listen-on switch0
}
}
gui {
https-port 443
}
nat {
rule 1 {
description prueba
destination {
group {
address-group ADDRv4_eth0
}
port 8090
}
inbound-interface eth0
inside-address {
address 192.168.168.2
port 8090
}
log disable
protocol tcp
type destination
}
rule 5000 {
description "masquerade for WAN"
outbound-interface eth0
type masquerade
}
rule 5002 {
description "masquerade for WAN 2"
outbound-interface eth1
type masquerade
}
rule 5004 {
description "masquerade for WAN 3"
outbound-interface eth2
type masquerade
}
}
ssh {
port 22
protocol-version v2
}
}
system {
conntrack {
expect-table-size 4096
hash-size 4096
table-size 32768
tcp {
half-open-connections 512
loose enable
max-retrans 3
}
}
host-name ubnt
login {
user ubnt {
authentication {
encrypted-password ****************
}
level admin
}
}
name-server 8.8.8.8
ntp {
server 0.ubnt.pool.ntp.org {
}
server 1.ubnt.pool.ntp.org {
}
server 2.ubnt.pool.ntp.org {
}
server 3.ubnt.pool.ntp.org {
}
}
syslog {
global {
facility all {
level notice
}
facility protocols {
level debug
}
}
}
time-zone UTC
}
Etiquetado:
Inicia Sesión o Regístrate para dejar un comentario.
Comentarios
Revisa:
https://help.ubnt.com/hc/en-us/articles/205145990-EdgeRouter-Dual-WAN-Load-Balance-Feature
https://community.ubnt.com/t5/forums/searchpage/tab/message?filter=location&q=loadbalance+port+forward&location=forum-board%3AEdgeMAX&page=2&sort_by=-topicPostDate&collapse_discussion=true
Antes que nada,,, muchas gracias por la respuesta,,, te cuento que lo hice,.,, inclusive saque el mikrotik de juego para probar e intente abrir los puertos solo balanceando y teniendo el routeredge conectado directo a una pc,,, y tampoco los abre =S