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

[Resolved}Routing Question?

Scheduled Pinned Locked Moved Routing and Multi WAN
3 Posts 2 Posters 726 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.
  • B
    bodam
    last edited by May 14, 2015, 5:42 PM May 13, 2015, 11:13 PM

    Let me start off by saying that I run pfSense at home but I am not a network guy by trade.  I am having an annoying issue that I cannot figure out how to fix.

    Background:  I have a server at home running Owncloud.  I can connect to it successfully at home by using the internal IP (i.e. 192.168.1.xyz).  If I am external I can access it successfully at my WAN IP (172.248.x.x) or by my domain name (ex bodam.com (not really this one)).

    The problem I have is that my internal systems cannot connect to it using the external info when connected internally.  So, my laptop, or droid phone, for example, connect just fine to bodam.com when at Starbucks, the local library, etc. but at home only the internal IP works (192.168.1.xyz).  This makes it hard to set up the owncloud client so that it works at home and not-at-home.  I think it is simply a matter of forcing the request out of my network and back in via the WAN interface.  I just have no idea how to fix it.

    Thanks for your help in advance

    David

    1 Reply Last reply Reply Quote 0
    • T
      thermo
      last edited by May 13, 2015, 11:43 PM

      Add a dns override  to return the local ip when on your internal lan So Bodam.Com would resolve to 192.168.X. X

      1 Reply Last reply Reply Quote 0
      • B
        bodam
        last edited by May 14, 2015, 5:42 PM

        @thermo:

        Add a dns override  to return the local ip when on your internal lan So Bodam.Com would resolve to 192.168.X. X

        That's what I did.  This was one of those instances where it occurred to me 10 minutes after posting this.

        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