Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revisionBoth sides next revision
docs:user-guide:network:dmz-based-bridge-mode [2018/02/20 19:59] – ↷ Page moved from docs:user-guide:dmz-based-bridge-mode to docs:user-guide:network:dmz-based-bridge-mode bobafetthotmaildocs:guide-user:network:wan:dmz-based-bridge-mode [2020/10/30 17:46] – moved dns to wan interface trendy
Line 1: Line 1:
-===== Poor Man's Bridge Mode =====+====== Poor Man's Bridge Mode ======
 When you don't have hardware that can do true bridging due to various reasons (many 3G/4G and quite a few DSL or fibre lines don't allow this, especially if there is also VoiP telephone lines involved), you can still do a poor man's bridge mode to have most services that need to be on the Internet facing router to work.\\ When you don't have hardware that can do true bridging due to various reasons (many 3G/4G and quite a few DSL or fibre lines don't allow this, especially if there is also VoiP telephone lines involved), you can still do a poor man's bridge mode to have most services that need to be on the Internet facing router to work.\\
 Dynamic DNS services are (currently) an exception to this as the LEDE router will only know the internal IP of the gateway, but not your true public IP given by the ISP. There are command line tools (bind-dig but also others) in LEDE repository that can allow the LEDE router to get the public IP given by the ISP (with the command dig +short myip.opendns.com @resolver1.opendns.com ), but for now the Dynamic DNS package isn't set to use them.  Dynamic DNS services are (currently) an exception to this as the LEDE router will only know the internal IP of the gateway, but not your true public IP given by the ISP. There are command line tools (bind-dig but also others) in LEDE repository that can allow the LEDE router to get the public IP given by the ISP (with the command dig +short myip.opendns.com @resolver1.opendns.com ), but for now the Dynamic DNS package isn't set to use them. 
Line 19: Line 19:
     * The router LAN interface should be      * The router LAN interface should be 
       * IP 192.168.1.1        * IP 192.168.1.1 
-      * netmask 255.255.255.0 +      * netmask 255.255.255.0\\ \\
-      * DNS server IP 8.8.8.8 (or your favourite DNS server IP) \\ \\+
   - the WAN port of your router should be set as a static IP in the same subnet of the gateway   - the WAN port of your router should be set as a static IP in the same subnet of the gateway
     * Example: the router's WAN interface      * Example: the router's WAN interface 
       * IP 192.168.2.2        * IP 192.168.2.2 
       * netmask 255.255.255.0       * netmask 255.255.255.0
 +      * DNS server IP 8.8.8.8 (or your favourite DNS server IP)
       * gateway IP 192.168.2.1\\ \\       * gateway IP 192.168.2.1\\ \\
   - set any port forwarding you need on the router device\\ \\   - set any port forwarding you need on the router device\\ \\
Line 31: Line 31:
  
 This tutorial above follows the steps defined by Steven Frosty in [[http://forum.vividwireless.com.au/forum/faqs-lte/faq-lte-bridge-mode-supported|FAQ -- LTE -- is Bridge Mode supported]] This tutorial above follows the steps defined by Steven Frosty in [[http://forum.vividwireless.com.au/forum/faqs-lte/faq-lte-bridge-mode-supported|FAQ -- LTE -- is Bridge Mode supported]]
 +
 +Firewall bridge mode support in OpenWrt is provided by the [[packages:pkgdata:kmod-br-netfilter|kmod-br-netfilter]] module.
  
 The following is an example UCI configuration in a LEDE device configured as detailed above. The following is an example UCI configuration in a LEDE device configured as detailed above.
Line 49: Line 51:
 network.lan.ip6assign='60' network.lan.ip6assign='60'
 network.lan.ipaddr='192.168.1.1' network.lan.ipaddr='192.168.1.1'
-network.lan.dns='8.8.8.8' 
 network.wan=interface network.wan=interface
 network.wan.ifname='eth0.2' network.wan.ifname='eth0.2'
Line 58: Line 59:
 network.wan.netmask='255.255.255.0' network.wan.netmask='255.255.255.0'
 network.wan.gateway='192.168.2.1' network.wan.gateway='192.168.2.1'
 +network.wan.dns='8.8.8.8'
 network.wan6=interface network.wan6=interface
 network.wan6.ifname='eth0.2' network.wan6.ifname='eth0.2'
 network.wan6.proto='dhcpv6'</code> network.wan6.proto='dhcpv6'</code>
  
  • Last modified: 2021/07/24 05:38
  • by someothertime