• Edgerouter: modify config

    IT Discussion
    4
    0 Votes
    4 Posts
    474 Views
    JaredBuschJ

    9cff8a60-526c-41c4-8594-c6b35d178f29-image.png

  • EdgeRouter 4: setting up L2TP server

    IT Discussion
    13
    1 Votes
    13 Posts
    1k Views
    FATeknollogeeF

    @Dashrender

    firewall { all-ping enable broadcast-ping disable group { address-group trusted_IPs { address 1.2.3.4 address 5.6.7.8 address 9.10.11.12 description "for remote GUI access" } } ipv6-name WANv6_IN { default-action drop description "WAN inbound traffic forwarded to LAN" enable-default-log rule 10 { action accept description "Allow established/related sessions" state { established enable related enable } } rule 20 { action drop description "Drop invalid state" state { invalid enable } } } ipv6-name WANv6_LOCAL { default-action drop description "WAN inbound traffic to the router" enable-default-log rule 10 { action accept description "Allow established/related sessions" state { established enable related enable } } rule 20 { action drop description "Drop invalid state" state { invalid enable } } rule 30 { action accept description "Allow IPv6 icmp" protocol ipv6-icmp } rule 40 { action accept description "allow dhcpv6" destination { port 546 } protocol udp source { port 547 } } } ipv6-receive-redirects disable ipv6-src-route disable ip-src-route disable log-martians enable 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 "remote GUI" destination { port 443 } log disable protocol tcp source { group { address-group trusted_IPs } } } rule 20 { action accept description "Allow established/related" state { established enable related enable } } rule 30 { action accept description ike destination { port 500 } log disable protocol udp state { invalid enable } } rule 40 { action accept description esp log disable protocol esp } rule 50 { action accept description nat-t destination { port 4500 } log disable protocol udp } rule 60 { action accept description l2tp destination { port 1701 } ipsec { match-ipsec } log disable protocol udp } } receive-redirects disable send-redirects enable source-validation disable syn-cookies enable } interfaces { ethernet eth0 { address 10.10.10.10/30 description Internet duplex auto firewall { in { ipv6-name WANv6_IN name WAN_IN } local { ipv6-name WANv6_LOCAL name WAN_LOCAL } } speed auto } ethernet eth1 { address 10.15.20.254/24 description "LAN 1" duplex auto speed auto } ethernet eth2 { address 192.168.2.254/24 description "LAN 2" duplex auto speed auto } ethernet eth3 { duplex auto speed auto } loopback lo { } } port-forward { auto-firewall enable hairpin-nat disable wan-interface eth0 } service { dhcp-server { disabled false hostfile-update disable shared-network-name LAN2 { authoritative enable subnet 192.168.2.0/24 { default-router 192.168.2.254 dns-server 192.168.2.254 lease 86400 start 192.168.2.38 { stop 192.168.2.43 } } } static-arp disable use-dnsmasq disable } dns { forwarding { cache-size 10000 listen-on eth1 listen-on eth2 name-server 1.1.1.1 name-server 9.9.9.9 } } gui { http-port 80 https-port 443 older-ciphers enable } nat { rule 5010 { description "masquerade for WAN" outbound-interface eth0 type masquerade } } ssh { port 22 protocol-version v2 } unms { connection wss:// } } system { domain-name ubnt gateway-address 10.10.10.1 host-name ER4 login { user ubnt { authentication { encrypted-password ubnt } level admin } } name-server 1.1.1.1 name-server 9.9.9.9 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 ipsec disable } syslog { global { facility all { level notice } facility protocols { level debug } } } time-zone UTC } vpn { ipsec { allow-access-to-local-interface disable auto-firewall-nat-exclude disable ipsec-interfaces { interface eth0 } } l2tp { remote-access { authentication { local-users { username hello { password 1234 } } mode local } client-ip-pool { start 192.168.100.100 stop 192.168.100.110 } dns-servers { server-1 1.1.1.1 server-2 9.9.9.9 } idle 1800 ipsec-settings { authentication { mode pre-shared-secret pre-shared-secret 1234 } ike-lifetime 3600 lifetime 3600 } mtu 1492 outside-address 10.10.10.10 } } }
  • 0 Votes
    82 Posts
    6k Views
    FATeknollogeeF

    Update: this is what I ended up with.
    Route based VPN using this guide as a template.

    Master site: 1x ER 12 + 1x ER 4
    Sites A, B, C & D :1x ER4 each location
    Colo: 1x ER4 & 1x pfSense (SM x10SDV-TLN4F+)

  • Edgerouter 4: constant disconnection's

    IT Discussion
    3
    0 Votes
    3 Posts
    402 Views
    JaredBuschJ

    I'm not sure what to look for since I don't have anything that has crashed

  • Edgerouter experts: UNMS to gui

    IT Discussion
    4
    0 Votes
    4 Posts
    736 Views
    scottalanmillerS

    @FATeknollogee said in Edgerouter experts: UNMS to gui:

    @JaredBusch said in Edgerouter experts: UNMS to gui:

    No. Why would you want that anyway? You have the terminal already. If you really need the GUI, drop a quick allow in the firewall rules for your current public IP.

    I like to have access to the GUI, I thought there was some "backdoor" way through UNMS.
    The firewall rule is good enough, thanks.

    It provides access to the CLI, but not to the GUI. If you want GUI access in that way, the trick is to make a remote proxy (a la Nginx) and do it that way, no need for UNMS.

  • 0 Votes
    40 Posts
    3k Views
    FATeknollogeeF

    The problem is this:
    On the Meraki side, let's say you have 5 (this can be any number greater than 1) firewalls.
    In Meraki speak, if all 5 are in the same "organization", S2S is a few clicks & AutoVPN takes over. No pre-shared secret, no keys.
    You turn on VPN, say yes to whatever subnets you want in the vpn & save.

    On the ER side, I have to create 5 peers to connect to the Meraki side.
    Meraki will only expose one connection for a 3rd party S2S & therein lies the problem.
    Not all the tunnels connect & there's no good way to fix it.