Access internal Owncloud Server from LAN and WAN with the same address



  • Dear all,

    I installed an Owncloud-Server (192.168.255.101) in my DMZ.

    I created an no-ip.org-Account an got an dynDNS name for my IT - it's working.

    The Owncloud Port should be NATed from 44443 to 443 to I want to reach my Owncloud  via this address https://xxx-no-ip.org:44443/owncloud from the LAN and from the Internet.

    What have I got to do, that this is working?

    I tried some things, but they are not working. :-( –> have a look on the screen shots.

    Many many thanks for you help!!!

    Regards
    hackel





  • Rebel Alliance Global Moderator

    "The Owncloud Port should be NATed from 44443 to 443 to"

    Well that is not what you have setup at all..  And why did you not just let your port forward do your firewall rule for you which is the default?  This is really click click.  What do you have in that owncloud alias?  For an IP?

    Why are you changing the port on the nat?  Why not just forward 443 or have owncloud listen on 44443?  This way its simple to have the same link both on the outside or inside with simple host over ride where you set xxx-no-ip.org on the inside to resolve to 192.168.255.101 and if your elsewhere on the internet it would resolve to what your public is and get forwarded in.



  • Many thanks for your answer.
    I had and zyxel firewall before and I can access the ownlcoud via this URL from the internet and from the LAN.

    https://xxxxxx.no-ip.org:44443/owncloud

    Is this also possible with pfsense?

    If you, can you please tell me how (step-by-step)

    many many thanks for you answer.

    Regards
    hackel.



  • Hello all,

    NAT is working.
    I can reach the owncloud over port 44443 from internal network and the name (https://xxxxxx.no-ip.org:44443/owncloud/).

    I added my local server IP in the DNS Resolver.

    The only problem is, to reach the owncloud from the internet.
    If have no idea, why it is not working.

    I added the new screenshots from the NAT rule and firewall rule.
    Hope someone find the mistake.

    Thank you very much for your support!

    Regards
    hackel





  • Rebel Alliance Global Moderator

    And again your forwarding 44443 to 443??  Why are you doing this  That just makes your url difficult..  Why do you have a port forward on your lan interface?  To change the port from 44443 to 443??

    Does your pfsense actually have a public IP on its wan, or is it behind nat?  Do a simple sniff on pfsense wan - and check with something like canyouseeme.org if the traffic to this 44443 port is getting there from the internet.



  • Hello Johnpoz,

    thank you for your answer.
    And again your forwarding 44443 to 443??  Why are you doing this  That just makes your url difficult.
    I don't whats us ownlcoud on the standard port because of attacks.

    That just makes your url difficult..
    Thats not a problem for me.

    Why do you have a port forward on your lan interface?  To change the port from 44443 to 443??
    Correct, I will reach the Server internal as external with the same URL.

    Does your pfsense actually have a public IP on its wan, or is it behind nat?
    If you mean, If I use an dyndns service, YES.

    Do a simple sniff on pfsense wan - and check with something like canyouseeme.org if the traffic to this 44443 port is getting there from the internet.
    I tried the check for 44443 and it failed.
    Something is still not working :-(

    Thanks you for trying to help me!!!!!

    Regards.
    hackel


  • Rebel Alliance Global Moderator

    What IP does pfsense have on wan 10.x.x.x, 192.168.x.x, 172.16-31.x.x ?  Or something else - ie a real public IP?  If you have a private address on your wan then your behind a nat, and you have to foward that port on the device in front of pfsense to pfsense wan IP or pfsense can not forward what it doesn't get.

    You need to SNIFF on you wan, and see if the packets get there – not just check to see if they show open..

    So under diag, do a packet capture for that port..  Do you see it hit pfsense..  Clearly its not going to be open for me I have not listening on it or forwarding it, pfsense just drops it.. But you can see that the traffic got there and pfsense if setup to do something would.  If it never gets there - nothing pfsense can do.




  • I got an official IP on the WAN interface (62.157.140.xxx).

    This is the result from the packet capture.

    19:34:27.773089 IP 107.20.89.142.42710 > 91.58.xxx.xxx.44443: tcp 0
    19:34:28.771618 IP 107.20.89.142.42710 > 91.58.xxx.xxx.44443: tcp 0
    19:34:30.782082 IP 107.20.89.142.42710 > 91.58.xxx.xxx.44443: tcp 0
    19:34:34.792186 IP 107.20.89.142.42710 > 91.58.xxx.xxx.44443: tcp 0

    Any idea?

    Thanks for you answer.



  • Can anyone help me?  :-[

    It would be very very nice.



  • Make your owncloud instance listen on port 44443 directly to save on NAT translation. Way easier.



  • Your WAN Port Forward shows destination "DMZ net".  It should be "WAN net" or, better still, "WAN address" - i.e., your public IP.


  • Rebel Alliance Global Moderator

    True your forward needs to be to your actual server running owncloud not a network.