Navigation

    Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search

    cannot show config after reboot host OS

    TNSR
    2
    9
    173
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • V
      vah1280 last edited by

      when I change interface IP on TNSR router and reboot host OS, I cannot show running config as picture below, any one help me?
      402455ff-f171-4f00-b797-11c99daea8b3-image.png

      Derelict 1 Reply Last reply Reply Quote 0
      • Derelict
        Derelict LAYER 8 Netgate @vah1280 last edited by

        @vah1280 Something in your configuration is preventing the clixon_backend service from starting.

        See if anything stands out in /var/log/messages

        V 1 Reply Last reply Reply Quote 1
        • V
          vah1280 @Derelict last edited by

          @derelict this is my log file, but I don't know why
          b35aef5e-7c90-48c5-9c91-80951036a6e3-image.png

          Derelict 1 Reply Last reply Reply Quote 0
          • Derelict
            Derelict LAYER 8 Netgate @vah1280 last edited by

            @vah1280 Never seen that before. But it looks like you might have managed to get interfaces in there twice or something. Not sure how one would get to that state without manually editing the config file.

            If you want, paste in (please don'e screen shot) the text found in /var/tnsr/startup_db.

            V 1 Reply Last reply Reply Quote 0
            • V
              vah1280 @Derelict last edited by

              @derelict this is starup_db file pls check for me, many thanks

              <config>
   <dataplane-config xmlns="urn:netgate:xml:yang:netgate-dataplane">
      <dpdk>
         <dev>
            <id>0000:13:00.0</id>
            <name>gi1188</name>
         </dev>
         <dev>
            <id>0000:1b:00.0</id>
            <name>gi100</name>
         </dev>
         <uio-driver>igb_uio</uio-driver>
      </dpdk>
      <nat>
         <nat-mode>endpoint-dependent</nat-mode>
      </nat>
   </dataplane-config>
   <interfaces-config xmlns="urn:netgate:xml:yang:netgate-interface">
      <interface>
         <name>gi100</name>
         <enabled>true</enabled>
         <nat-interface>inside</nat-interface>
         <ipv4>
            <address>
               <ip>192.168.10.1/24</ip>
            </address>
         </ipv4>
      </interface>
      <interface>
         <name>gi1188</name>
         <enabled>true</enabled>
         <nat-interface>outside</nat-interface>
         <ipv4>
            <address>
               <ip>192.168.96.6/30</ip>
            </address>
         </ipv4>
      </interface>
   </interfaces-config>
   <nat-config xmlns="urn:netgate:xml:yang:netgate-nat">
      <global-options>
         <nat44>
            <forwarding-enabled>true</forwarding-enabled>
         </nat44>
      </global-options>
      <dynamic>
         <pool-table>
            <pool-entry>
               <first-address>202.60.109.9</first-address>
               <last-address>202.60.109.14</last-address>
            </pool-entry>
         </pool-table>
      </dynamic>
   </nat-config>
   <route-table-config xmlns="urn:netgate:xml:yang:netgate-route-table">
      <static-routes>
         <route-table>
            <name>ipv4-VRF:0</name>
            <address-family>ipv4</address-family>
            <ipv4-routes>
               <route>
                  <destination-prefix>0.0.0.0/0</destination-prefix>
                  <next-hop>
                     <hop>
                        <hop-id>0</hop-id>
                        <ipv4-address>203.209.181.41</ipv4-address>
                     </hop>
                  </next-hop>
               </route>
               <route>
                  <destination-prefix>10.10.10.0/24</destination-prefix>
                  <next-hop>
                     <hop>
                        <hop-id>0</hop-id>
                        <ipv4-address>192.168.10.2</ipv4-address>
                     </hop>
                  </next-hop>
               </route>
               <route>
                  <destination-prefix>100.64.0.0/10</destination-prefix>
                  <next-hop>
                     <hop>
                        <hop-id>0</hop-id>
                        <ipv4-address>192.168.10.2</ipv4-address>
                     </hop>
                  </next-hop>
               </route>
            </ipv4-routes>
         </route-table>
      </static-routes>
   </route-table-config>
   <nacm xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-acm">
      <enable-nacm>true</enable-nacm>
      <read-default>deny</read-default>
      <write-default>deny</write-default>
      <exec-default>deny</exec-default>
      <groups>
         <group>
            <name>admin</name>
            <user-name>root</user-name>
            <user-name>tnsr</user-name>
         </group>
      </groups>
      <rule-list>
         <name>admin-rules</name>
         <group>admin</group>
         <rule>
            <name>permit-all</name>
            <module-name>*</module-name>
            <access-operations>*</access-operations>
            <action>permit</action>
         </rule>
      </rule-list>
   </nacm>
   <modules-state xmlns="urn:ietf:params:xml:ns:yang:ietf-yang-library">
      <module-set-id>20.10</module-set-id>
      <module>
         <name>clixon-lib</name>
         <revision>2020-04-23</revision>
         <namespace>http://clicon.org/lib</namespace>
      </module>
      <module>
         <name>ietf-inet-types</name>
         <revision>2013-07-15</revision>
         <namespace>urn:ietf:params:xml:ns:yang:ietf-inet-types</namespace>
      </module>
      <module>
         <name>ietf-ipfix-psamp</name>
         <revision>2012-09-05</revision>
         <namespace>urn:ietf:params:xml:ns:yang:ietf-ipfix-psamp</namespace>
      </module>
      <module>
         <name>ietf-netconf</name>
         <revision>2011-06-01</revision>
         <namespace>urn:ietf:params:xml:ns:netconf:base:1.0</namespace>
      </module>
      <module>
         <name>ietf-netconf-acm</name>
         <revision>2018-02-14</revision>
         <namespace>urn:ietf:params:xml:ns:yang:ietf-netconf-acm</namespace>
      </module>
      <module>
         <name>ietf-restconf</name>
         <revision>2017-01-26</revision>
         <namespace>urn:ietf:params:xml:ns:yang:ietf-restconf</namespace>
      </module>
      <module>
         <name>ietf-yang-library</name>
         <revision>2016-06-21</revision>
         <namespace>urn:ietf:params:xml:ns:yang:ietf-yang-library</namespace>
      </module>
      <module>
         <name>ietf-yang-types</name>
         <revision>2013-07-15</revision>
         <namespace>urn:ietf:params:xml:ns:yang:ietf-yang-types</namespace>
      </module>
      <module>
         <name>netgate-acl</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-acl</namespace>
      </module>
      <module>
         <name>netgate-bfd</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-bfd</namespace>
      </module>
      <module>
         <name>netgate-bgp</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-bgp</namespace>
      </module>
      <module>
         <name>netgate-common</name>
         <revision>2020-11-01</revision>
         <namespace>urn:netgate:xml:yang:netgate-common</namespace>
      </module>
      <module>
         <name>netgate-dataplane</name>
         <revision>2020-11-01</revision>
         <namespace>urn:netgate:xml:yang:netgate-dataplane</namespace>
      </module>
      <module>
         <name>netgate-frr</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-frr</namespace>
      </module>
      <module>
         <name>netgate-frr-types</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-frr-types</namespace>
      </module>
      <module>
         <name>netgate-gre</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-gre</namespace>
      </module>
      <module>
         <name>netgate-host</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-host</namespace>
      </module>
      <module>
         <name>netgate-host-interface</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-hostif</namespace>
      </module>
      <module>
         <name>netgate-http</name>
         <revision>2020-06-15</revision>
         <namespace>urn:ietf:params:xml:ns:yang:netgate-http</namespace>
      </module>
      <module>
         <name>netgate-interface</name>
         <revision>2020-10-01</revision>
         <namespace>urn:netgate:xml:yang:netgate-interface</namespace>
      </module>
      <module>
         <name>netgate-interface-extensions</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-ifext</namespace>
      </module>
      <module>
         <name>netgate-ip</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-ip</namespace>
      </module>
      <module>
         <name>netgate-ipfix</name>
         <revision>2020-10-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-ipfix</namespace>
      </module>
      <module>
         <name>netgate-ipsec</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-ipsec</namespace>
      </module>
      <module>
         <name>netgate-kea</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-kea</namespace>
      </module>
      <module>
         <name>netgate-lldp</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-lldp</namespace>
      </module>
      <module>
         <name>netgate-macip</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-macip</namespace>
      </module>
      <module>
         <name>netgate-map</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-map</namespace>
      </module>
      <module>
         <name>netgate-master</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-master</namespace>
      </module>
      <module>
         <name>netgate-nat</name>
         <revision>2020-10-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-nat</namespace>
      </module>
      <module>
         <name>netgate-neighbor</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-neighbor</namespace>
      </module>
      <module>
         <name>netgate-ntp</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-ntp</namespace>
      </module>
      <module>
         <name>netgate-ospf</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-ospf</namespace>
      </module>
      <module>
         <name>netgate-ospf6</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-ospf6</namespace>
      </module>
      <module>
         <name>netgate-package</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-package</namespace>
      </module>
      <module>
         <name>netgate-pki</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-pki</namespace>
      </module>
      <module>
         <name>netgate-rip</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-rip</namespace>
      </module>
      <module>
         <name>netgate-route</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-route</namespace>
      </module>
      <module>
         <name>netgate-route-table</name>
         <revision>2020-07-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-route-table</namespace>
      </module>
      <module>
         <name>netgate-snmp</name>
         <revision>2020-06-15</revision>
         <namespace>https://netgate.com/ns/netgate-snmp</namespace>
      </module>
      <module>
         <name>netgate-span</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-span</namespace>
      </module>
      <module>
         <name>netgate-ssh-server</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-ssh-server</namespace>
      </module>
      <module>
         <name>netgate-sysctl</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-sysctl</namespace>
      </module>
      <module>
         <name>netgate-system</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-system</namespace>
      </module>
      <module>
         <name>netgate-trace</name>
         <revision>2020-05-20</revision>
         <namespace>urn:netgate:xml:yang:netgate-trace</namespace>
      </module>
      <module>
         <name>netgate-unbound</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-unbound</namespace>
      </module>
      <module>
         <name>netgate-vpp-graph</name>
         <revision>2020-05-02</revision>
         <namespace>urn:netgate:xml:yang:netgate-vpp-graph</namespace>
      </module>
      <module>
         <name>netgate-vpp-prometheus</name>
         <revision>2020-09-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-vpp-prometheus</namespace>
      </module>
      <module>
         <name>netgate-vrrp</name>
         <revision>2020-06-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-vrrp</namespace>
      </module>
      <module>
         <name>netgate-vxlan</name>
         <revision>2020-10-15</revision>
         <namespace>urn:netgate:xml:yang:netgate-vxlan</namespace>
      </module>
   </modules-state>
</config>
              Derelict 1 Reply Last reply Reply Quote 0
              • Derelict
                Derelict LAYER 8 Netgate @vah1280 last edited by

                @vah1280 My hunch is it is the fact that your NAT pool does not have an address on the outside interface.

                I also do not see how you expect to have a route destination for 0.0.0.0/0 as 203.209.181.41 when there is no way to route to that on any interface.

                I would delete that route pool and replace it with 192.168.96.6 and delete the default route and see if vpp starts then. Since VPP doesn't start you will need to either reconfigure it from scratch or hand-edit /var/tnsr/startup_db.

                V 1 Reply Last reply Reply Quote 1
                • V
                  vah1280 @Derelict last edited by

                  @derelict thanks for your help.

                  Derelict 1 Reply Last reply Reply Quote 0
                  • Derelict
                    Derelict LAYER 8 Netgate @vah1280 last edited by

                    @vah1280 Did you get it working?

                    V 1 Reply Last reply Reply Quote 0
                    • V
                      vah1280 @Derelict last edited by vah1280

                      @derelict yes, it worked.
                      I changed gw to 192.168.96.5
                      Many thanks

                      1 Reply Last reply Reply Quote 1
                      • First post
                        Last post

                      Products

                      • Platform Overview
                      • TNSR
                      • pfSense
                      • Appliances

                      Services

                      • Training
                      • Professional Services

                      Support

                      • Subscription Plans
                      • Contact Support
                      • Product Lifecycle
                      • Documentation

                      News

                      • Media Coverage
                      • Press
                      • Events

                      Resources

                      • Blog
                      • FAQ
                      • Find a Partner
                      • Resource Library
                      • Security Information

                      Company

                      • About Us
                      • Careers
                      • Partners
                      • Contact Us
                      • Legal
                      Our Mission

                      We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

                      Subscribe to our Newsletter

                      Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

                      © 2021 Rubicon Communications, LLC | Privacy Policy