Can access web server externally, but not from LANs.
-
This post is deleted! -
This post is deleted! -
I guess you can remove (== red) these :
As you already have a - or 2 - incoming VPN connections, I advise you to remove blow up every NAT rule.
If needed, you have access to everything from the outside, using VPN. -
@PITS_King said in Can access web server externally, but not from LANs.:
is illegally blocking inbound SMTP on 25,
No I don't think it can be considered illegal, as Gertjan stated pretty much all residential connections block this and even if they didn't as Gertjan also correctly goes over wouldn't do you any good, other then sending to maybe some smaller domains. All the major player will not accept mail from you anyway.
Many home isp connections clearly state in their TOS that you are not to run servers.. So they can just not allow those ports since its in their TOS that your not suppose to do it, which you agreed to when you signed up be it you read them or not.
Even open - your isp not going to allow you edit your PTR for your IP, and when that doesn't match the name your mail server gives when trying to send mail, would also be denied - your just some want a be spammer in their minds.. Since any real mail server would follow all the RFCs in running a mail server, etc.
The software your running is designed to be run on a public connection... And then sure if you were running those services they would have to be open on your firewall.. But you would want or really need those open on a HOME connection..
If I get a few minutes here today, will draw up a basic connection drawing and we can work from there on getting your services working locally. And then how to get the services you do want/need to provide to the internet that make sense and can be done realistically..
But also as @Gertjan correctly mentions - if you want to play with some of this stuff and serving up to the public you prob better off doing that on VPS somewhere then off your local "home" connection be it mail or other services.
Lets start with your local stuff working and accessing your local resources be a fqdn you want to use.. So if that is the case you could remove ALL of those port forwards.. Port forwards are only required for access externally not for lan to other lan access.
-
This post is deleted! -
What is the source address of the client you are testing from?
What is real IP address on the server you are trying to connect to?
What port are you trying to connect to?
How are you testing?
What is the result?
How many FQDNs to the WAN address are we talking about?
Please limit your answer to one port on one server only. Fix that and you'll probably know how to fix them all.
-
This post is deleted! -
What did you do with the Redirect IPv4 Gateway - Force all client-generated IPv4 traffic through the tunnel checkbox in the server configuration?
If unchecked (or if you have set the equivalent of Don't pull routes in the client configuration) what are the Local Networks defined in your OpenVPN server.
One issue at a time please. Please provide as much detail as possible. You have the benefit of being able to choose the first one / prioritize.
-
This post is deleted! -
This post is deleted! -
If you have Redirect IPv4 Gateway checked AND you are not telling the client not to pull routes, you do not need any custom options to push any routes. You will get two routes on the client into the tunnel 0.0.0.0/1 and 128.0.0.0/1. That covers all IPv4 addresses without clobbering the client's default route. The netmask is longer (/1 is longer than /0) so those routes are preferred in the routing table over 0.0.0.0/0.
With that in place, connect to the VPN and attempt a connection (a single connection like to http://10.0.1.4:10000/ (or https or whatever it is supposed to be).
What, exactly, happens.
Then go to Diagnostics > Packet Capture and set the following:
Interface: The interface the server is on. The 10.0.1.0/24 interface
Host: 10.0.10.0/24
Port: 10000
Count: 100000Start
Test connecting to 10.0.1.4:10000 and let it fail
Stop the capture. What do you see?
If you see nothing, move the packet capture to the OpenVPN interface and do the same thing. What do you see?
-
An aside: you should not be using Custom Options to push routes. You would use the Local Networks form field that would become visible if you unchecked Redirect IPv4 Gateway
-
@PITS_King said in Can access web server externally, but not from LANs.:
Yes, it was ruled by Congress that it is illegal for an ISP to block ANY port.
You do understand they repealed net neutrality right ;)
The mail server running on the Virtualmin server is only handling contact forms on a publicly visible website.
Then you have ZERO use for an inbound 25 port..
Internal connectivity has ZERO to do with any port forwards.. So yeah you can forget all of those.. And have arleady stated all you have to do for internal - your firewall rules already allow all traffic, so you issue of connectivity between your vlans comes down to name resolution or host firewall.
-
This post is deleted! -
@PITS_King said in Can access web server externally, but not from LANs.:
Just to confirm, should I replace the 3 LAN addresses I defined in IPv4 Local Network(s) to 0.0.0.0/1 and 128.0.0.0/1 to have everything working 100%?
It depends on what you want. There is no one answer. It's up to you.
If it's working, no.
If you want to push routes to the other side that tell them to send all traffic to you, check Redirect IPv4 Gateway.
If you want to send all traffic out the OpenVPN tunnel, then that would be a Remote Network on your side instead of a Local Network Local networks push routes to clients so they send traffic to you. Remote networks add kernel routes to the local routing table that get traffic into OpenVPN to send out a tunnel.
-
This post is deleted! -
@PITS_King said in Can access web server externally, but not from LANs.:
Then, on to getting Snort and Suricata back up and running! :-)
So you have your internal working... I sure wouldn't start playing with those until you do, and you sure and the F do not need both.
