Quantcast
Channel: All EdgeRouter posts
Viewing all 60861 articles
Browse latest View live
↧

Re: Routing issues

October 10, 2016, 8:04 pm
$
0
0

Maybe this will help

$ ipcalc 172.28.0.0/30                                                                                                                                                           
Address:   172.28.0.0           10101100.00011100.00000000.000000 00                                                                                                                            
Netmask:   255.255.255.252 = 30 11111111.11111111.11111111.111111 00                                                                                                                            
Wildcard:  0.0.0.3              00000000.00000000.00000000.000000 11                                                                                                                            
=>                                                                                                                                                                                              
Network:   172.28.0.0/30        10101100.00011100.00000000.000000 00                                                                                                                            HostMin:   172.28.0.1           10101100.00011100.00000000.000000 01                                                                                                                            HostMax:   172.28.0.2           10101100.00011100.00000000.000000 10                                                                                                                            
Broadcast: 172.28.0.3           10101100.00011100.00000000.000000 11                                                                                                                            
Hosts/Net: 2                     Class B, Private Internet

172.28.0.224 does not fall into the subnet range

↧
Search

Re: We have 3 days to get Dual Stack IPV6 running on an ER8Pro on the Frontier ISP

October 10, 2016, 8:32 pm
$
0
0

Do your know how they're provisioning IPv6 (dhcpv6-pd, 6rd, ds-lite, etc.)?

↧
↧

Re: WAN dropped, DHCP renew fixes it

October 10, 2016, 8:44 pm
$
0
0

I have the same problem on 1.9.0 on Frontier. Terrible problem. Have an open support request referencing this thread. I put in your cron script we shall see.

↧

Re: ER-PoE constant high CPU since 1.8.0

October 10, 2016, 9:18 pm
$
0
0
sorvani wrote:

The only thing repeating in /var/log/messages is two OpenVPN tunnels attempting to reconnect once a minute.

Try adding persist-tun option to each openvpn interface:

set interfaces openvpn vtun0 openvpn-option --persist-tun

This option will force OpenVPN interface to remain in system even if there is no traffic going through.

↧

Re: 1WAN used instead of combination of other WAN (Load Balancing)

October 10, 2016, 9:35 pm
$
0
0

 

Im do it form scatch, and i realised originally switch0 have ip instead of eth4... so, now i change my vlan to switch0 instead eht4. do i need do cli command for load balance again.

 

switch0 is kinda virtual, how do i set it in cli? but its not working

 

set interfaces switch0 firewall in modify balance
set interfaces vif 10 firewall in modify balance
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_pppoe0
}
}
modify {
table main
}
}
rule 30 {
action modify
description "do NOT load balance destination public address"
destination {
group {
address-group ADDRv4_pppoe1
}
}
modify {
table main
}
}
rule 40 {
action modify
description "do NOT load balance destination public address"
destination {
group {
address-group ADDRv4_pppoe2
}
}
modify {
table main
}
}
rule 50 {
action modify
description "do NOT load balance destination public address"
destination {
group {
address-group ADDRv4_pppoe3
}
}
modify {
table main
}
}
rule 70 {
action modify
modify {
lb-group G
}
}
}
name WAN_IN {
default-action drop
description "WAN to internal"
rule 10 {
action accept
description "Allow established/related"
state {
established enable
related enable
}
}
rule 20 {
action drop
description "Drop invalid state"
state {
invalid enable
}
}
}
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 drop
description "Drop invalid state"
state {
invalid enable
}
}
}
options {
mss-clamp {
mss 1412
}
}
receive-redirects disable
send-redirects enable
source-validation disable
syn-cookies enable
}
interfaces {
ethernet eth0 {
description WAN
duplex auto
poe {
output off
}
speed auto
vif 500 {
address dhcp
description "TM UniFi"
mtu 1500
pppoe 0 {
default-route auto
firewall {
in {
name WAN_IN
}
local {
name WAN_LOCAL
}
}
mtu 1492
name-server auto
password test1234
user-id kkloa@unifi
}
}
}
ethernet eth1 {
description "WAN 2"
duplex auto
poe {
output off
}
speed auto
vif 500 {
address dhcp
description "TM UniFi"
mtu 1500
pppoe 1 {
default-route auto
firewall {
in {
name WAN_IN
}
local {
name WAN_LOCAL
}
}
mtu 1492
name-server auto
password test1234
user-id artwork@unifibiz
}
}
}
ethernet eth2 {
description "WAN 3"
duplex auto
poe {
output off
}
speed auto
vif 624 {
address dhcp
description OHANA
mtu 1500
pppoe 2 {
default-route auto
firewall {
in {
name WAN_IN
}
local {
name WAN_LOCAL
}
}
mtu 1492
name-server auto
password test1234
user-id artprint@ohanafixed
}
}
}
ethernet eth3 {
description "WAN 4"
duplex auto
poe {
output off
}
speed auto
vif 624 {
address dhcp
description OHANA
mtu 1500
pppoe 3 {
default-route auto
firewall {
in {
name WAN_IN
}
local {
name WAN_LOCAL
}
}
mtu 1492
name-server auto
password test1234
user-id artworkandprint@ohanafixed
}
}
}
ethernet eth4 {
duplex auto
poe {
output off
}
speed auto
}
loopback lo {
}
switch switch0 {
address 192.168.3.1/24
description Local
firewall {
in {
modify balance
}
}
mtu 1500
switch-port {
interface eth4 {
}
vlan-aware disable
}
vif 10 {
address 192.168.10.1/24
description vlan10
mtu 1500
}
vif 20 {
address 192.168.20.1/24
description vlan20
mtu 1500
}
vif 30 {
address 192.168.30.1/24
description vlan30
mtu 1500
}
vif 40 {
address 192.168.40.1/24
description vlan40
mtu 1500
}
vif 50 {
address 192.168.50.1/24
description vlan50
mtu 1500
}
vif 60 {
address 192.168.60.1/24
description vlan60
mtu 1500
}
vif 70 {
address 192.168.70.1/24
description vlan70
mtu 1500
}
vif 80 {
address 192.168.80.1/24
description vlan80
mtu 1500
}
vif 90 {
address 192.168.90.1/24
description vlan90
mtu 1500
}
vif 100 {
address 192.168.100.1/24
description vlan100
mtu 1500
}
vif 110 {
address 192.168.110.1/24
description vlan110
mtu 1500
}
vif 130 {
address 192.168.130.1/24
description vlan130
mtu 1500
}
vif 131 {
address 192.168.131.1/24
description vlan131
mtu 1500
}
vif 140 {
address 192.168.140.1/24
description vlan140
mtu 1500
}
vif 141 {
address 192.168.141.1/24
description vlan141
mtu 1500
}
vif 142 {
address 192.168.142.1/24
description vlan142
mtu 1500
}
vif 143 {
address 192.168.143.1/24
description vlan143
mtu 1500
}
vif 144 {
address 192.168.144.1/24
description vlan144
mtu 1500
}
vif 145 {
address 192.198.145.1/24
description vlan145
mtu 1500
}
vif 146 {
address 192.168.146.1/24
description vlan146
mtu 1500
}
vif 150 {
address 192.168.150.1/24
description vlan150
mtu 1500
}
vif 151 {
address 192.168.151.1/24
description vlan151
mtu 1500
}
vif 160 {
address 192.168.160.1/24
description vlan160
mtu 1500
}
vif 161 {
address 192.168.161.1/24
description vlan161
mtu 1500
}
}
}
load-balance {
group G {
interface pppoe0 {
}
interface pppoe1 {
}
interface pppoe2 {
}
interface pppoe3 {
}
lb-local enable
}
}
port-forward {
auto-firewall enable
hairpin-nat enable
lan-interface eth4
lan-interface switch0
wan-interface pppoe0
}
service {
dhcp-server {
disabled false
hostfile-update disable
shared-network-name LAN {
authoritative enable
subnet 192.168.3.0/24 {
default-router 192.168.3.1
dns-server 192.168.3.1
lease 86400
start 192.168.3.38 {
stop 192.168.3.243
}
}
}
shared-network-name vlan10 {
authoritative disable
subnet 192.168.10.0/24 {
default-router 192.168.10.1
dns-server 192.168.10.1
dns-server 8.8.8.8
lease 86400
start 192.168.10.2 {
stop 192.168.10.254
}
}
}
shared-network-name vlan20 {
authoritative disable
subnet 192.168.20.0/24 {
default-router 192.168.20.1
dns-server 192.168.20.1
dns-server 8.8.8.8
lease 86400
start 192.168.20.2 {
stop 192.168.20.254
}
}
}
shared-network-name vlan30 {
authoritative disable
subnet 192.168.30.0/24 {
default-router 192.168.30.1
dns-server 192.168.30.1
dns-server 8.8.8.8
lease 86400
start 192.168.30.2 {
stop 192.168.30.254
}
}
}
shared-network-name vlan40 {
authoritative disable
subnet 192.168.40.0/24 {
default-router 192.168.40.1
dns-server 192.168.40.1
dns-server 8.8.8.8
lease 86400
start 192.168.40.2 {
stop 192.168.40.254
}
}
}
shared-network-name vlan50 {
authoritative disable
subnet 192.168.50.0/24 {
default-router 192.168.50.1
dns-server 192.168.50.1
dns-server 8.8.8.8
lease 86400
start 192.168.50.2 {
stop 192.168.50.254
}
}
}
shared-network-name vlan60 {
authoritative disable
subnet 192.168.60.0/24 {
default-router 192.168.60.1
dns-server 192.168.60.1
dns-server 8.8.8.8
lease 86400
start 192.168.60.2 {
stop 192.168.60.254
}
}
}
shared-network-name vlan70 {
authoritative disable
subnet 192.168.70.0/24 {
default-router 192.168.70.1
dns-server 192.168.70.1
dns-server 8.8.8.8
lease 86400
start 192.168.70.2 {
stop 192.168.70.254
}
}
}
shared-network-name vlan80 {
authoritative disable
subnet 192.168.80.0/24 {
default-router 192.168.80.1
dns-server 192.168.80.1
dns-server 8.8.8.8
lease 86400
start 192.168.80.2 {
stop 192.168.80.254
}
}
}
shared-network-name vlan90 {
authoritative disable
subnet 192.168.90.0/24 {
default-router 192.168.90.1
dns-server 192.168.90.1
dns-server 8.8.8.8
lease 86400
start 192.168.90.2 {
stop 192.168.90.254
}
}
}
shared-network-name vlan100 {
authoritative disable
subnet 192.168.100.0/24 {
default-router 192.168.100.1
dns-server 192.198.100.1
dns-server 8.8.8.8
lease 86400
start 192.168.100.2 {
stop 192.168.100.254
}
}
}
shared-network-name vlan110 {
authoritative disable
subnet 192.168.110.0/24 {
default-router 192.168.110.1
dns-server 192.168.110.1
dns-server 8.8.8.8
lease 86400
start 192.168.110.2 {
stop 192.168.110.254
}
}
}
shared-network-name vlan130 {
authoritative disable
subnet 192.168.130.0/24 {
default-router 192.168.130.1
dns-server 192.168.130.1
dns-server 8.8.8.8
lease 86400
start 192.168.130.2 {
stop 192.168.130.254
}
}
}
shared-network-name vlan131 {
authoritative disable
subnet 192.168.131.0/24 {
default-router 192.168.131.1
dns-server 192.168.131.1
dns-server 8.8.8.8
lease 86400
start 192.168.131.2 {
stop 192.168.131.254
}
}
}
shared-network-name vlan140 {
authoritative disable
subnet 192.168.140.0/24 {
default-router 192.168.140.1
dns-server 192.168.140.1
dns-server 8.8.8.8
lease 86400
start 192.168.140.2 {
stop 192.168.140.254
}
}
}
shared-network-name vlan141 {
authoritative disable
subnet 192.168.141.0/24 {
default-router 192.168.141.1
dns-server 192.168.141.1
dns-server 8.8.8.8
lease 86400
start 192.168.141.2 {
stop 192.168.141.254
}
}
}
shared-network-name vlan142 {
authoritative disable
subnet 192.168.142.0/24 {
default-router 192.168.142.1
dns-server 192.168.142.1
dns-server 8.8.8.8
lease 86400
start 192.168.142.2 {
stop 192.168.142.254
}
}
}
shared-network-name vlan143 {
authoritative disable
subnet 192.168.143.0/24 {
default-router 192.168.143.1
dns-server 192.168.143.1
dns-server 8.8.8.8
lease 86400
start 192.168.143.2 {
stop 192.168.143.254
}
}
}
shared-network-name vlan144 {
authoritative disable
subnet 192.168.144.0/24 {
default-router 192.168.144.1
dns-server 192.168.144.1
dns-server 8.8.8.8
lease 86400
start 192.168.144.2 {
stop 192.168.144.254
}
}
}
shared-network-name vlan145 {
authoritative disable
subnet 192.168.145.0/24 {
default-router 192.168.145.1
dns-server 192.168.145.1
dns-server 8.8.8.8
lease 86400
start 192.168.145.2 {
stop 192.168.145.254
}
}
}
shared-network-name vlan146 {
authoritative disable
subnet 192.168.146.0/24 {
default-router 192.168.146.1
dns-server 192.168.146.1
dns-server 8.8.8.8
lease 86400
start 192.168.146.2 {
stop 192.168.146.254
}
}
}
shared-network-name vlan150 {
authoritative disable
subnet 192.168.150.0/24 {
default-router 192.168.150.1
dns-server 192.168.150.1
dns-server 8.8.8.8
lease 86400
start 192.168.150.2 {
stop 192.168.150.254
}
}
}
shared-network-name vlan151 {
authoritative disable
subnet 192.168.151.0/24 {
default-router 192.168.151.1
dns-server 192.168.151.1
dns-server 8.8.8.8
lease 86400
start 192.168.151.2 {
stop 192.168.151.254
}
}
}
shared-network-name vlan160 {
authoritative disable
subnet 192.168.160.0/24 {
default-router 192.168.160.1
dns-server 192.168.160.1
dns-server 8.8.8.8
lease 86400
start 192.168.160.2 {
stop 192.168.160.254
}
}
}
shared-network-name vlan161 {
authoritative disable
subnet 192.168.161.0/24 {
default-router 192.168.161.1
dns-server 192.168.161.1
dns-server 8.8.8.8
lease 86400
start 192.168.161.2 {
stop 192.168.161.254
}
}
}
use-dnsmasq disable
}
dns {
forwarding {
cache-size 150
listen-on switch0
listen-on eth4
listen-on switch0.10
listen-on switch0.20
listen-on switch0.30
listen-on switch0.40
listen-on switch0.50
listen-on switch0.60
listen-on switch0.70
listen-on switch0.80
listen-on switch0.90
listen-on switch0.100
listen-on switch0.110
listen-on switch0.130
listen-on switch0.131
listen-on switch0.140
listen-on switch0.141
listen-on switch0.142
listen-on switch0.143
listen-on switch0.144
listen-on switch0.145
listen-on switch0.146
listen-on switch0.150
listen-on switch0.151
listen-on switch0.160
listen-on switch0.161
listen-on pppoe0
listen-on pppoe1
listen-on pppoe2
listen-on pppoe3
}
}
gui {
http-port 80
https-port 443
older-ciphers enable
}
nat {
rule 5000 {
description "masquerade for WAN"
outbound-interface pppoe0
type masquerade
}
rule 5002 {
description "masquerade for WAN 2"
outbound-interface pppoe1
type masquerade
}
rule 5004 {
description "masquerade for WAN 3"
outbound-interface pppoe2
type masquerade
}
rule 5006 {
description "masquerade for WAN 4"
outbound-interface pppoe3
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 $1$zKNoUbAo$gomzUbYvgyUMcD436Wo66.
}
level admin
}
}
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 {
}
}
offload {
hwnat disable
ipv4 {
forwarding enable
pppoe enable
}
}
syslog {
global {
facility all {
level notice
}
facility protocols {
level debug
}
}
}
time-zone UTC
traffic-analysis {
dpi disable
export enable
}
}


/* Warning: Do not remove the following line. */
/* === vyatta-config-version: "config-management@1:conntrack@1:cron@1:dhcp-relay@1:dhcp-server@4:firewall@5:ipsec@5:nat@3:qos@1:quagga@2:system@4:ubnt-pptp@1:ubnt-util@1:vrrp@1:webgui@1:webproxy@1:zone-policy@1" === */
/* Release version: v1.9.0.4901118.160804.1131 */

 

↧
↧

Using an ER-8 and need 'Transparent DMZ' or 'Transparent Mode'

October 10, 2016, 10:10 pm
$
0
0

Hello everyone!

 

I need some assistance/advise from the UBNT Rock Stars around here.

 

I have a client whose Security/DVR setup appears to have been designed in the stone age. The vendor for the DVR equiptment is being very rigid and will not change or budge on the network config. The client has been with them forever and is not willing to force the issue. So it looks like I'm the one who gets to be flexible... or breakable.

 

Here's the deal - they have a /28 from the ISP and are using just about all of the 13 IPs running through a Fortinet in 'Transparent Mode'. The Fortinet died and I'm trying really, realy hard to get them into an ER-8.

 

The way it's set up now - 7 or 8 DVR machines (PCs) are all connected to a dumb switch and the switch is connected to the Fortinet. The DVRs are all set up with Static IP addresses using the ISPs Public IP address block. Example below:

 

ISP Gateway: 50.1.1.1

Fortinet: 50.1.1.2

DVR1: 50.1.1.3

DVR2: 50.1.1.4

etc, etc, etc.

There is NO 'internal' network. Everything is static, and using the public IPs.

 

Their security company can then use the public IPs and connect directly to the DVR they need and do whatever it s they do. They've had this setup in place forever, and like I said, are unwilling to make netowrk changes because thier vendor is not being flexible (or in this centtury for that matter).

 

Trust me, I know the multitude of reasons why this isn't a good idea, not secure, yada, yada. I'm trying ot help out an elderly office building owner and get him out of a jam. I remember back in the day connecting a dumb switch directly to a Covad wireless T1 router and setting up machines in the 'DMZ' and it worked great! IT looks like they don't build circuits like that any more and you can't just connect a dumb stich to the ISPs router any more ( I tried).

 

So, to my question... Is there a configureation for the ER-8 that will allow me to keep this guys current setup? I know it's been called 'Transparent Mode' or 'Transparent DMZ' depending on the vendor, but i haven't been able to find much on the forums. I found some older stuff that stated it was not avaialable YET, but those posts were 2-3 years old now.

 

Any help you can give, is greatly appreciated!

 

-Rob

↧

Re: Destination NAT rules

October 10, 2016, 10:24 pm
$
0
0

suppose your wan ip=111.111.111.111

A new packet with destination address 111.111.111.111 dest-port 1234 enters WAN interface.

Option1

Without matching dNAT rule, no dNAT takes place. This makes the ER WAN interface the destination , and the WAN_LOCAL firewall ruleset is used to filter the packet.

Option2

With matching dNAT rule, destination IP is translated into internal IP 192.168.0.100.  This is not an local IP address of the ER, so the ER will use WAN_IN firewall ruleset (if applied).  So this dNAT rule itself is already a sort of filter.

 

 

 

Now the hypothetical case....of a new packet with destination address 192.168.0.100 entering the WAN interface.  (of course, such a packet will never make it  to you on the internet)

There is no dNAT for that address (dNAT rules use the 111.111.111.111 address), so normal routing takes place.  192.168.0.100 is on LAN, not the ER itself, so the packet is filtered by WAN_IN.  If no WAN_IN is in place, the packet is free to go

 

↧

Re: WAN Failover / LTE Modem

October 10, 2016, 10:26 pm
$
0
0

Post your config?

 

Are you getting a private IP address from the gateway?  Do you have a way to switch it from router to bridge mode?

↧
Search

Re: Can EdgeRouter do IPv6 passthrough to work around Comcast BCI SMCD3G issues?

October 10, 2016, 10:37 pm
↧
↧

Re: isolation wifi AP

October 10, 2016, 10:43 pm
$
0
0

still nobody for my subsidiary quesiton?

 

 

First my subsidiary question: I have reset my configuration to have a clean upgrade to 1.9 . I have noted that I can't communicate with my plex server from my mobile devices in direct line. And not because the AP are in router mode but apparently because I need to open the port 32400 in NAT destination configuration to reroute resquests between eth1 and swtich.  I know it because when I did it, it directly updates my plex connection and informed me to the direct link to the plex server. So it is a new feature since 1.85 or 1.9.0 ? or is it a glitch ? Or is it always been like that and I've simply not well configured before?

↧

Re: Using an ER-8 and need 'Transparent DMZ' or 'Transparent Mode'

October 11, 2016, 12:12 am
$
0
0

What do you want the EdgeRouter to do in this case? Firewalling? Or? If there's nothing fancy being done on the Fortinet, you could replace it with a dumb switch...

 

Assuming you do want to do something smart, proxy arp mode might be a way to do it? EdgeRouters are L3 devices, so they can't do much as a L2 firewall if that's what you were after, but with proxy arp and some creative routes you might be able to achieve it.

↧

Problem accessing website and servers from inside

October 11, 2016, 12:56 am
$
0
0

New on UBNT

 

I have problems to access our websites located on DMZ from LAN, from the outside it works fine but from the inside we always come to the router interface.

 

We have 5 public iP on the WAN interface, 4 of them are NATed to internal servers.

Everything else works fine, I have tryed the hairpin NAT but there was no differance. probably did something wrong...

 

Any suggestions of what i have missed here?

↧

Re: dnsmasq and CNAME

October 11, 2016, 1:01 am
$
0
0

 all possibilities are listed in my previous post. pls read carefully the Dnsmasq's manpage excerpt I included there. The next thing I would try is putting the same content in /etc/hosts. But as I said before since DHCP isn't handled by dnsmasq by default in EdgeOS. None of the possibilies said in the manpage might work as a result.

 

Worth trying some of those. It's quick test anyway. Good luck.

↧
↧

Re: Problem accessing website and servers from inside

October 11, 2016, 1:16 am
$
0
0

Since you're doing your own port forwarding by DNAT rules, the hairpin NAT and other settings in Port Forward gui tab/CLI will not have effect.

 

Read this LINK on how to manually create port forward and hairpin NAT rules. You're missing the same port forwarding DNAT rules on your LAN interface as well as a SNAT aka Masquerade rule for the LAN interface.

↧

Re: NAT bypassing Firewall rules

October 11, 2016, 1:42 am
$
0
0

Blocking illegal source IPs on WAN is fairly common. My list was incomplete though (was posting from my mobile)

 

 posted a more complete list in another thread:

UBNT-stig wrote:

 

irewall {
    group {
        network-group BOGONS {
            description "Invalid WAN networks"
            network 10.0.0.0/8
            network 100.64.0.0/10
            network 127.0.0.0/8
            network 169.254.0.0/16
            network 172.16.0.0/12
            network 192.0.0.0/24
            network 192.0.2.0/24
            network 192.168.0.0/16
            network 198.18.0.0/15
            network 198.51.100.0/24
            network 203.0.113.0/24
            network 224.0.0.0/3
        }
    }

 

 

Bogon IP addresses are used by hackers to confuse or even intrude a system.. Packets with a source IP from the above list hitting WAN is considered illegal and many firewalls out there block them on first sight and don't even bother to check for further matching/default drop.

 

↧
Search

Firewall group - Security Updates outdated

October 11, 2016, 1:49 am
$
0
0

I was planning on using EdgeOS firewall group "Security Updates" to throttle the speed of windows updates on our network,but it seems that Windows 10 updates are not tagged as security updates, but rather as Web File Transfer. Is there any planned FW update on improving this group? 

 

Btw, I already disabled the "Updates from other PCs" as I want them from Microsoft directly and should be seen by the EdgeOS as such - "Security Updates"

↧

Re: Problem accessing website and servers from inside

October 11, 2016, 1:58 am
$
0
0

Thank you for the quick answer!

 

But that did not work for me...

I duplicated the DNAT rule and changed the interface to eth2 and created a SNAT Masqurade with both SRC and DST address to 192.168.2.0/24.

I dont get any packet to these NAT rules, I tryed to move them up but no go.

↧
↧

Multiple DHCP IPs on WAN

October 11, 2016, 2:04 am
$
0
0

Greetings, is it somehow possible to pull two DHCP IPs to the same physical interface?

 

Something like this, but the router won't allow it.

 

Thanks ....

 

 

 

2016-10-11_03-59-01.jpg

↧

Re: NAT bypassing Firewall rules

October 11, 2016, 3:06 am
$
0
0

But that means I'd have to check every packet to NOT be a bogon which is overhead and I hate overhead ;(

I'd like to know the attack vector tho, since I don't quite understand it yet.

↧

Re: Not able to ping guest network from router(LOCAL)

October 11, 2016, 3:07 am
↧
Viewing all 60861 articles
Browse latest View live
Search