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

Routing and Directly Connected Interface

Scheduled Pinned Locked Moved Routing and Multi WAN
3 Posts 3 Posters 1.3k Views
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.
  • M
    mebdnaconet
    last edited by May 16, 2013, 11:58 AM

    I'm using version 2.0.3.  I have a LAN interfaces with a single, directly-connected 10.5.200.0/23 subnet.  I have a second LAN interface that routes to 300+ networks, including 10.x.x.x subnets.  Can I route 10.0.0.0/8 out the second LAN interface without causing problems on the 10.5.200.x interface?  Is it good practice to do so?

    –Mike

    1 Reply Last reply Reply Quote 0
    • S
      SeventhSon
      last edited by May 16, 2013, 5:25 PM

      You can, directly connected takes precedence over static or routes from routing protocols.
      I do it all the time, without problem, don't know if it's best practice, might depend on who you ask :D

      1 Reply Last reply Reply Quote 0
      • J
        jimp Rebel Alliance Developer Netgate
        last edited by May 20, 2013, 3:19 PM

        While it is best to avoid such overlaps, more specific routes do get considered first as SeventhSon mentioned. It should work fine.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        1 out of 3
        • First post
          1/3
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
          This community forum collects and processes your personal information.
          consent.not_received