How should a two nic gateway be routed (FreeBSD 10.2)?












0















I am trying to set up a freebsd router that sits between the cable/dsl modem and my lan machines. Here is the logical setup:



Cable/DSL modem connected to internet:



gateway 192.168.0.1


FreeBSD Router (with two nics):



em0 192.168.0.121
ue0 10.0.0.1


FreeBSD Lan Machine:



em0 10.0.0.2


It seems like the path from the lan to the wan should be 10.0.0.2->10.0.0.1->192.168.0.1->wan and that I should be able to ping a machine on the internet from the lan machine.



In summary, though:




  • The internet is accessible from the FreeBSD router.

  • The lan machine is acccessible from the FreeBSD router.

  • The FreeBSD router is accessible from the lan machine.

  • The internet is not accessible from the lan machine.


Here are the /etc/rc.conf entries on the router:



ifconfig_ue0="inet 10.0.0.1 netmask 255.255.255.0"
ifconfig_em0="inet 192.168.0.121 netmask 255.255.255.0"
gateway_enable="YES"
defaultrouter="192.168.0.1"


Here are the /etc/rc.conf entries on the lan machine:



ifconfig_em0="inet 10.0.0.2 netmask 255.255.255.0"
defaultrouter="10.0.0.1"


Here are the routing table entries from the FreeBSD router (loki):



netstat -r            
Routing tables

Internet:
Destination Gateway Flags Netif Expire
default 192.168.0.1 UGS em0
10.0.0.0/24 link#3 U ue0
10.0.0.1 link#3 UHS lo0
127.0.0.1 link#2 UH lo0
192.168.0.0/24 link#1 U em0
192.168.0.121 link#1 UHS lo0


Here are the routing table entries from the lan machine (freebird):



netstat -r
Routing tables

Internet:
Destination Gateway Flags Netif Expire
default 10.0.0.1 UGS em0
10.0.0.0 link#1 U em0
10.0.0.2 link#1 UHS lo0
freebird link#2 UH lo0


netstat on the lan machine is sloooowwwww.



Does this information appear correct for the setup, or is there an apparent problem??










share|improve this question























  • how configurable is your adsl router? can you set it to use just dumb bridging mode and the run pppoe on your freebsd box? that will be a lot simpler and a lot less problematic because then everthing is done on the freebsd box (and its external NIC, em0 i think, has the public internet address).

    – cas
    Nov 5 '15 at 3:41











  • @cas I don't think I can set up bridge mode on the adsl router. It's from the cable company and they have it pretty locked down.

    – decuser
    Nov 5 '15 at 5:00











  • if netstat is slow, it's almost certainly because it is trying to resolve hostnames for the IP addresses - and can't because the lan machine can't access the internet. try netstat -rn to test. it doesnt solve your problem, but i recommend running a local dns resolver (e.g. unbound) on your freebsd gw and configuring all the lan machines (perhaps via dhcp) to use it.

    – cas
    Nov 5 '15 at 5:43








  • 1





    have you configured your freebsd box to do NAT? or, better yet, configured the ADSL router to NAT all traffic from the LAN port, not just traffic with 192.168.0/24 src addresses? See freebsd.org/doc/handbook/firewalls-ipfw.html for info about ipfw and NAT

    – cas
    Nov 5 '15 at 5:46













  • @cas is it possible to manually configure dns for the lan machine to point to the gateway for dns resolution? and no I haven't configured NAT on the freebsd box and I don't know what you mean by having the adsl router NAT all traffic from the LAN port.

    – decuser
    Nov 5 '15 at 7:28
















0















I am trying to set up a freebsd router that sits between the cable/dsl modem and my lan machines. Here is the logical setup:



Cable/DSL modem connected to internet:



gateway 192.168.0.1


FreeBSD Router (with two nics):



em0 192.168.0.121
ue0 10.0.0.1


FreeBSD Lan Machine:



em0 10.0.0.2


It seems like the path from the lan to the wan should be 10.0.0.2->10.0.0.1->192.168.0.1->wan and that I should be able to ping a machine on the internet from the lan machine.



In summary, though:




  • The internet is accessible from the FreeBSD router.

  • The lan machine is acccessible from the FreeBSD router.

  • The FreeBSD router is accessible from the lan machine.

  • The internet is not accessible from the lan machine.


Here are the /etc/rc.conf entries on the router:



ifconfig_ue0="inet 10.0.0.1 netmask 255.255.255.0"
ifconfig_em0="inet 192.168.0.121 netmask 255.255.255.0"
gateway_enable="YES"
defaultrouter="192.168.0.1"


Here are the /etc/rc.conf entries on the lan machine:



ifconfig_em0="inet 10.0.0.2 netmask 255.255.255.0"
defaultrouter="10.0.0.1"


Here are the routing table entries from the FreeBSD router (loki):



netstat -r            
Routing tables

Internet:
Destination Gateway Flags Netif Expire
default 192.168.0.1 UGS em0
10.0.0.0/24 link#3 U ue0
10.0.0.1 link#3 UHS lo0
127.0.0.1 link#2 UH lo0
192.168.0.0/24 link#1 U em0
192.168.0.121 link#1 UHS lo0


Here are the routing table entries from the lan machine (freebird):



netstat -r
Routing tables

Internet:
Destination Gateway Flags Netif Expire
default 10.0.0.1 UGS em0
10.0.0.0 link#1 U em0
10.0.0.2 link#1 UHS lo0
freebird link#2 UH lo0


netstat on the lan machine is sloooowwwww.



Does this information appear correct for the setup, or is there an apparent problem??










share|improve this question























  • how configurable is your adsl router? can you set it to use just dumb bridging mode and the run pppoe on your freebsd box? that will be a lot simpler and a lot less problematic because then everthing is done on the freebsd box (and its external NIC, em0 i think, has the public internet address).

    – cas
    Nov 5 '15 at 3:41











  • @cas I don't think I can set up bridge mode on the adsl router. It's from the cable company and they have it pretty locked down.

    – decuser
    Nov 5 '15 at 5:00











  • if netstat is slow, it's almost certainly because it is trying to resolve hostnames for the IP addresses - and can't because the lan machine can't access the internet. try netstat -rn to test. it doesnt solve your problem, but i recommend running a local dns resolver (e.g. unbound) on your freebsd gw and configuring all the lan machines (perhaps via dhcp) to use it.

    – cas
    Nov 5 '15 at 5:43








  • 1





    have you configured your freebsd box to do NAT? or, better yet, configured the ADSL router to NAT all traffic from the LAN port, not just traffic with 192.168.0/24 src addresses? See freebsd.org/doc/handbook/firewalls-ipfw.html for info about ipfw and NAT

    – cas
    Nov 5 '15 at 5:46













  • @cas is it possible to manually configure dns for the lan machine to point to the gateway for dns resolution? and no I haven't configured NAT on the freebsd box and I don't know what you mean by having the adsl router NAT all traffic from the LAN port.

    – decuser
    Nov 5 '15 at 7:28














0












0








0








I am trying to set up a freebsd router that sits between the cable/dsl modem and my lan machines. Here is the logical setup:



Cable/DSL modem connected to internet:



gateway 192.168.0.1


FreeBSD Router (with two nics):



em0 192.168.0.121
ue0 10.0.0.1


FreeBSD Lan Machine:



em0 10.0.0.2


It seems like the path from the lan to the wan should be 10.0.0.2->10.0.0.1->192.168.0.1->wan and that I should be able to ping a machine on the internet from the lan machine.



In summary, though:




  • The internet is accessible from the FreeBSD router.

  • The lan machine is acccessible from the FreeBSD router.

  • The FreeBSD router is accessible from the lan machine.

  • The internet is not accessible from the lan machine.


Here are the /etc/rc.conf entries on the router:



ifconfig_ue0="inet 10.0.0.1 netmask 255.255.255.0"
ifconfig_em0="inet 192.168.0.121 netmask 255.255.255.0"
gateway_enable="YES"
defaultrouter="192.168.0.1"


Here are the /etc/rc.conf entries on the lan machine:



ifconfig_em0="inet 10.0.0.2 netmask 255.255.255.0"
defaultrouter="10.0.0.1"


Here are the routing table entries from the FreeBSD router (loki):



netstat -r            
Routing tables

Internet:
Destination Gateway Flags Netif Expire
default 192.168.0.1 UGS em0
10.0.0.0/24 link#3 U ue0
10.0.0.1 link#3 UHS lo0
127.0.0.1 link#2 UH lo0
192.168.0.0/24 link#1 U em0
192.168.0.121 link#1 UHS lo0


Here are the routing table entries from the lan machine (freebird):



netstat -r
Routing tables

Internet:
Destination Gateway Flags Netif Expire
default 10.0.0.1 UGS em0
10.0.0.0 link#1 U em0
10.0.0.2 link#1 UHS lo0
freebird link#2 UH lo0


netstat on the lan machine is sloooowwwww.



Does this information appear correct for the setup, or is there an apparent problem??










share|improve this question














I am trying to set up a freebsd router that sits between the cable/dsl modem and my lan machines. Here is the logical setup:



Cable/DSL modem connected to internet:



gateway 192.168.0.1


FreeBSD Router (with two nics):



em0 192.168.0.121
ue0 10.0.0.1


FreeBSD Lan Machine:



em0 10.0.0.2


It seems like the path from the lan to the wan should be 10.0.0.2->10.0.0.1->192.168.0.1->wan and that I should be able to ping a machine on the internet from the lan machine.



In summary, though:




  • The internet is accessible from the FreeBSD router.

  • The lan machine is acccessible from the FreeBSD router.

  • The FreeBSD router is accessible from the lan machine.

  • The internet is not accessible from the lan machine.


Here are the /etc/rc.conf entries on the router:



ifconfig_ue0="inet 10.0.0.1 netmask 255.255.255.0"
ifconfig_em0="inet 192.168.0.121 netmask 255.255.255.0"
gateway_enable="YES"
defaultrouter="192.168.0.1"


Here are the /etc/rc.conf entries on the lan machine:



ifconfig_em0="inet 10.0.0.2 netmask 255.255.255.0"
defaultrouter="10.0.0.1"


Here are the routing table entries from the FreeBSD router (loki):



netstat -r            
Routing tables

Internet:
Destination Gateway Flags Netif Expire
default 192.168.0.1 UGS em0
10.0.0.0/24 link#3 U ue0
10.0.0.1 link#3 UHS lo0
127.0.0.1 link#2 UH lo0
192.168.0.0/24 link#1 U em0
192.168.0.121 link#1 UHS lo0


Here are the routing table entries from the lan machine (freebird):



netstat -r
Routing tables

Internet:
Destination Gateway Flags Netif Expire
default 10.0.0.1 UGS em0
10.0.0.0 link#1 U em0
10.0.0.2 link#1 UHS lo0
freebird link#2 UH lo0


netstat on the lan machine is sloooowwwww.



Does this information appear correct for the setup, or is there an apparent problem??







networking freebsd routing






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 5 '15 at 2:53









decuserdecuser

16611




16611













  • how configurable is your adsl router? can you set it to use just dumb bridging mode and the run pppoe on your freebsd box? that will be a lot simpler and a lot less problematic because then everthing is done on the freebsd box (and its external NIC, em0 i think, has the public internet address).

    – cas
    Nov 5 '15 at 3:41











  • @cas I don't think I can set up bridge mode on the adsl router. It's from the cable company and they have it pretty locked down.

    – decuser
    Nov 5 '15 at 5:00











  • if netstat is slow, it's almost certainly because it is trying to resolve hostnames for the IP addresses - and can't because the lan machine can't access the internet. try netstat -rn to test. it doesnt solve your problem, but i recommend running a local dns resolver (e.g. unbound) on your freebsd gw and configuring all the lan machines (perhaps via dhcp) to use it.

    – cas
    Nov 5 '15 at 5:43








  • 1





    have you configured your freebsd box to do NAT? or, better yet, configured the ADSL router to NAT all traffic from the LAN port, not just traffic with 192.168.0/24 src addresses? See freebsd.org/doc/handbook/firewalls-ipfw.html for info about ipfw and NAT

    – cas
    Nov 5 '15 at 5:46













  • @cas is it possible to manually configure dns for the lan machine to point to the gateway for dns resolution? and no I haven't configured NAT on the freebsd box and I don't know what you mean by having the adsl router NAT all traffic from the LAN port.

    – decuser
    Nov 5 '15 at 7:28



















  • how configurable is your adsl router? can you set it to use just dumb bridging mode and the run pppoe on your freebsd box? that will be a lot simpler and a lot less problematic because then everthing is done on the freebsd box (and its external NIC, em0 i think, has the public internet address).

    – cas
    Nov 5 '15 at 3:41











  • @cas I don't think I can set up bridge mode on the adsl router. It's from the cable company and they have it pretty locked down.

    – decuser
    Nov 5 '15 at 5:00











  • if netstat is slow, it's almost certainly because it is trying to resolve hostnames for the IP addresses - and can't because the lan machine can't access the internet. try netstat -rn to test. it doesnt solve your problem, but i recommend running a local dns resolver (e.g. unbound) on your freebsd gw and configuring all the lan machines (perhaps via dhcp) to use it.

    – cas
    Nov 5 '15 at 5:43








  • 1





    have you configured your freebsd box to do NAT? or, better yet, configured the ADSL router to NAT all traffic from the LAN port, not just traffic with 192.168.0/24 src addresses? See freebsd.org/doc/handbook/firewalls-ipfw.html for info about ipfw and NAT

    – cas
    Nov 5 '15 at 5:46













  • @cas is it possible to manually configure dns for the lan machine to point to the gateway for dns resolution? and no I haven't configured NAT on the freebsd box and I don't know what you mean by having the adsl router NAT all traffic from the LAN port.

    – decuser
    Nov 5 '15 at 7:28

















how configurable is your adsl router? can you set it to use just dumb bridging mode and the run pppoe on your freebsd box? that will be a lot simpler and a lot less problematic because then everthing is done on the freebsd box (and its external NIC, em0 i think, has the public internet address).

– cas
Nov 5 '15 at 3:41





how configurable is your adsl router? can you set it to use just dumb bridging mode and the run pppoe on your freebsd box? that will be a lot simpler and a lot less problematic because then everthing is done on the freebsd box (and its external NIC, em0 i think, has the public internet address).

– cas
Nov 5 '15 at 3:41













@cas I don't think I can set up bridge mode on the adsl router. It's from the cable company and they have it pretty locked down.

– decuser
Nov 5 '15 at 5:00





@cas I don't think I can set up bridge mode on the adsl router. It's from the cable company and they have it pretty locked down.

– decuser
Nov 5 '15 at 5:00













if netstat is slow, it's almost certainly because it is trying to resolve hostnames for the IP addresses - and can't because the lan machine can't access the internet. try netstat -rn to test. it doesnt solve your problem, but i recommend running a local dns resolver (e.g. unbound) on your freebsd gw and configuring all the lan machines (perhaps via dhcp) to use it.

– cas
Nov 5 '15 at 5:43







if netstat is slow, it's almost certainly because it is trying to resolve hostnames for the IP addresses - and can't because the lan machine can't access the internet. try netstat -rn to test. it doesnt solve your problem, but i recommend running a local dns resolver (e.g. unbound) on your freebsd gw and configuring all the lan machines (perhaps via dhcp) to use it.

– cas
Nov 5 '15 at 5:43






1




1





have you configured your freebsd box to do NAT? or, better yet, configured the ADSL router to NAT all traffic from the LAN port, not just traffic with 192.168.0/24 src addresses? See freebsd.org/doc/handbook/firewalls-ipfw.html for info about ipfw and NAT

– cas
Nov 5 '15 at 5:46







have you configured your freebsd box to do NAT? or, better yet, configured the ADSL router to NAT all traffic from the LAN port, not just traffic with 192.168.0/24 src addresses? See freebsd.org/doc/handbook/firewalls-ipfw.html for info about ipfw and NAT

– cas
Nov 5 '15 at 5:46















@cas is it possible to manually configure dns for the lan machine to point to the gateway for dns resolution? and no I haven't configured NAT on the freebsd box and I don't know what you mean by having the adsl router NAT all traffic from the LAN port.

– decuser
Nov 5 '15 at 7:28





@cas is it possible to manually configure dns for the lan machine to point to the gateway for dns resolution? and no I haven't configured NAT on the freebsd box and I don't know what you mean by having the adsl router NAT all traffic from the LAN port.

– decuser
Nov 5 '15 at 7:28










3 Answers
3






active

oldest

votes


















2














I think you need to add a static route on your modem, to route all incoming traffic for 10.0.0.0/8 to 192.168.0.121.



I am rather assuming that NAT is being done in the modem here.






share|improve this answer































    0














    This would be solution in pf firewall, in case NAT-ing is not done in modem.
    However, NAT-ing can be done in pppd or pppoe, as you state you're using DSL.



    Edit /etc/pf.conf:



    external_iface="em0"  # your WAN facing interface
    internal_iface="ue0" # your LAN facing interface

    set skip on lo0 # skip filtering on loopback
    nat on $external_iface from $internal_iface:network to any -> ( $external_iface:0)

    block in on $external_iface

    pass in quick on $internal_iface from $internal_iface:network to any keep state

    pass out on $external_iface


    Regarding DNS, you can setup a local_unbound on Frebsd box, set it to listen on 192.168.0.1, then either push this configuration over dhcpd to your clients on LAN, or manually editing /etc/resolv.conf like:



    echo 'nameserver 192.168.0.1' > /etc/resolv.conf





    share|improve this answer































      0














      You need to set up NAT in your FreeBSD Router machine and need to NAT(With port translation) your 10.0.0.0/8 networks to 192.168.0.121/32 IP address. Otherwise your LAN machine can not access internet






      share|improve this answer








      New contributor




      Bishnu Prasad Gautam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.




















        Your Answer








        StackExchange.ready(function() {
        var channelOptions = {
        tags: "".split(" "),
        id: "106"
        };
        initTagRenderer("".split(" "), "".split(" "), channelOptions);

        StackExchange.using("externalEditor", function() {
        // Have to fire editor after snippets, if snippets enabled
        if (StackExchange.settings.snippets.snippetsEnabled) {
        StackExchange.using("snippets", function() {
        createEditor();
        });
        }
        else {
        createEditor();
        }
        });

        function createEditor() {
        StackExchange.prepareEditor({
        heartbeatType: 'answer',
        autoActivateHeartbeat: false,
        convertImagesToLinks: false,
        noModals: true,
        showLowRepImageUploadWarning: true,
        reputationToPostImages: null,
        bindNavPrevention: true,
        postfix: "",
        imageUploader: {
        brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
        contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
        allowUrls: true
        },
        onDemand: true,
        discardSelector: ".discard-answer"
        ,immediatelyShowMarkdownHelp:true
        });


        }
        });














        draft saved

        draft discarded


















        StackExchange.ready(
        function () {
        StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f240907%2fhow-should-a-two-nic-gateway-be-routed-freebsd-10-2%23new-answer', 'question_page');
        }
        );

        Post as a guest















        Required, but never shown

























        3 Answers
        3






        active

        oldest

        votes








        3 Answers
        3






        active

        oldest

        votes









        active

        oldest

        votes






        active

        oldest

        votes









        2














        I think you need to add a static route on your modem, to route all incoming traffic for 10.0.0.0/8 to 192.168.0.121.



        I am rather assuming that NAT is being done in the modem here.






        share|improve this answer




























          2














          I think you need to add a static route on your modem, to route all incoming traffic for 10.0.0.0/8 to 192.168.0.121.



          I am rather assuming that NAT is being done in the modem here.






          share|improve this answer


























            2












            2








            2







            I think you need to add a static route on your modem, to route all incoming traffic for 10.0.0.0/8 to 192.168.0.121.



            I am rather assuming that NAT is being done in the modem here.






            share|improve this answer













            I think you need to add a static route on your modem, to route all incoming traffic for 10.0.0.0/8 to 192.168.0.121.



            I am rather assuming that NAT is being done in the modem here.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Jul 9 '17 at 17:48









            Bob EagerBob Eager

            1,9161421




            1,9161421

























                0














                This would be solution in pf firewall, in case NAT-ing is not done in modem.
                However, NAT-ing can be done in pppd or pppoe, as you state you're using DSL.



                Edit /etc/pf.conf:



                external_iface="em0"  # your WAN facing interface
                internal_iface="ue0" # your LAN facing interface

                set skip on lo0 # skip filtering on loopback
                nat on $external_iface from $internal_iface:network to any -> ( $external_iface:0)

                block in on $external_iface

                pass in quick on $internal_iface from $internal_iface:network to any keep state

                pass out on $external_iface


                Regarding DNS, you can setup a local_unbound on Frebsd box, set it to listen on 192.168.0.1, then either push this configuration over dhcpd to your clients on LAN, or manually editing /etc/resolv.conf like:



                echo 'nameserver 192.168.0.1' > /etc/resolv.conf





                share|improve this answer




























                  0














                  This would be solution in pf firewall, in case NAT-ing is not done in modem.
                  However, NAT-ing can be done in pppd or pppoe, as you state you're using DSL.



                  Edit /etc/pf.conf:



                  external_iface="em0"  # your WAN facing interface
                  internal_iface="ue0" # your LAN facing interface

                  set skip on lo0 # skip filtering on loopback
                  nat on $external_iface from $internal_iface:network to any -> ( $external_iface:0)

                  block in on $external_iface

                  pass in quick on $internal_iface from $internal_iface:network to any keep state

                  pass out on $external_iface


                  Regarding DNS, you can setup a local_unbound on Frebsd box, set it to listen on 192.168.0.1, then either push this configuration over dhcpd to your clients on LAN, or manually editing /etc/resolv.conf like:



                  echo 'nameserver 192.168.0.1' > /etc/resolv.conf





                  share|improve this answer


























                    0












                    0








                    0







                    This would be solution in pf firewall, in case NAT-ing is not done in modem.
                    However, NAT-ing can be done in pppd or pppoe, as you state you're using DSL.



                    Edit /etc/pf.conf:



                    external_iface="em0"  # your WAN facing interface
                    internal_iface="ue0" # your LAN facing interface

                    set skip on lo0 # skip filtering on loopback
                    nat on $external_iface from $internal_iface:network to any -> ( $external_iface:0)

                    block in on $external_iface

                    pass in quick on $internal_iface from $internal_iface:network to any keep state

                    pass out on $external_iface


                    Regarding DNS, you can setup a local_unbound on Frebsd box, set it to listen on 192.168.0.1, then either push this configuration over dhcpd to your clients on LAN, or manually editing /etc/resolv.conf like:



                    echo 'nameserver 192.168.0.1' > /etc/resolv.conf





                    share|improve this answer













                    This would be solution in pf firewall, in case NAT-ing is not done in modem.
                    However, NAT-ing can be done in pppd or pppoe, as you state you're using DSL.



                    Edit /etc/pf.conf:



                    external_iface="em0"  # your WAN facing interface
                    internal_iface="ue0" # your LAN facing interface

                    set skip on lo0 # skip filtering on loopback
                    nat on $external_iface from $internal_iface:network to any -> ( $external_iface:0)

                    block in on $external_iface

                    pass in quick on $internal_iface from $internal_iface:network to any keep state

                    pass out on $external_iface


                    Regarding DNS, you can setup a local_unbound on Frebsd box, set it to listen on 192.168.0.1, then either push this configuration over dhcpd to your clients on LAN, or manually editing /etc/resolv.conf like:



                    echo 'nameserver 192.168.0.1' > /etc/resolv.conf






                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Jul 16 '18 at 9:17









                    fugitivefugitive

                    795420




                    795420























                        0














                        You need to set up NAT in your FreeBSD Router machine and need to NAT(With port translation) your 10.0.0.0/8 networks to 192.168.0.121/32 IP address. Otherwise your LAN machine can not access internet






                        share|improve this answer








                        New contributor




                        Bishnu Prasad Gautam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                        Check out our Code of Conduct.

























                          0














                          You need to set up NAT in your FreeBSD Router machine and need to NAT(With port translation) your 10.0.0.0/8 networks to 192.168.0.121/32 IP address. Otherwise your LAN machine can not access internet






                          share|improve this answer








                          New contributor




                          Bishnu Prasad Gautam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.























                            0












                            0








                            0







                            You need to set up NAT in your FreeBSD Router machine and need to NAT(With port translation) your 10.0.0.0/8 networks to 192.168.0.121/32 IP address. Otherwise your LAN machine can not access internet






                            share|improve this answer








                            New contributor




                            Bishnu Prasad Gautam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.










                            You need to set up NAT in your FreeBSD Router machine and need to NAT(With port translation) your 10.0.0.0/8 networks to 192.168.0.121/32 IP address. Otherwise your LAN machine can not access internet







                            share|improve this answer








                            New contributor




                            Bishnu Prasad Gautam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.









                            share|improve this answer



                            share|improve this answer






                            New contributor




                            Bishnu Prasad Gautam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.









                            answered 25 mins ago









                            Bishnu Prasad GautamBishnu Prasad Gautam

                            1




                            1




                            New contributor




                            Bishnu Prasad Gautam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.





                            New contributor





                            Bishnu Prasad Gautam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.






                            Bishnu Prasad Gautam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.






























                                draft saved

                                draft discarded




















































                                Thanks for contributing an answer to Unix & Linux Stack Exchange!


                                • Please be sure to answer the question. Provide details and share your research!

                                But avoid



                                • Asking for help, clarification, or responding to other answers.

                                • Making statements based on opinion; back them up with references or personal experience.


                                To learn more, see our tips on writing great answers.




                                draft saved


                                draft discarded














                                StackExchange.ready(
                                function () {
                                StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f240907%2fhow-should-a-two-nic-gateway-be-routed-freebsd-10-2%23new-answer', 'question_page');
                                }
                                );

                                Post as a guest















                                Required, but never shown





















































                                Required, but never shown














                                Required, but never shown












                                Required, but never shown







                                Required, but never shown

































                                Required, but never shown














                                Required, but never shown












                                Required, but never shown







                                Required, but never shown







                                Popular posts from this blog

                                Accessing regular linux commands in Huawei's Dopra Linux

                                Can't connect RFCOMM socket: Host is down

                                Kernel panic - not syncing: Fatal Exception in Interrupt