[Cialug] PfSense
Tom Sellers
tsellers2009 at gmail.com
Sat Apr 25 03:37:32 UTC 2020
Sorry so much time has passed with no response. It appears that I have
finally resolved this. Thanks for the
suggestion to use my cell phone! Although I don't normally use my phone to
browse the internet I never really
thought about the fact that I could use the phone after disconnecting the
wifi to access my server from outside
the house. Should have thought of that!
I think that the basic issue was that the graphic connection to the pfsense
box was taking place on the https port
and that prevented my connection rules from working as I expected. I used
a different port to connect to the pfsense
box and then I could connect to my webserver. I was able to connect using
my cell but would still like to do some
testing from outside at some point.
Thanks again for the suggestions that I received!
On Mon, Apr 20, 2020 at 6:49 PM Jared Brees <fromj2sitsme at msn.com> wrote:
> Do you have any WAN rules that just "allow" 80 or 443? ( something like
> https://192.168.0.1/firewall_rules.php?if=wan )
>
>
> https://docs.netgate.com/pfsense/en/latest/firewall/remote-firewall-administration.html
>
>
> Also, do you have a smartphone with cellular data? That'd be my go-to pick
> to try it "remotely".
>
> ________________________________
> From: Cialug <cialug-bounces at cialug.org> on behalf of Tom Sellers <
> tsellers2009 at gmail.com>
> Sent: Saturday, April 18, 2020 20:09
> To: Central Iowa Linux Users Group <cialug at cialug.org>
> Subject: Re: [Cialug] PfSense
>
> I had my daughter try to contact my web site address and it simply timed
> out for her. I don't have anywhere close by that I could connect to a wifi
> and try it from outside my home network.
>
> ------------------------------------------------------
> In regard to your suggestion the problem existed before.
> It responded the same way for me before I added those two entries. I
> suspect it must be something about the setup of the pfsense box.
>
> Like I said everything else works fine with one exception that I don't know
> if is related at all. I have been having issues with random wireless
> devices not being able to connect for periods of time but then connect
> fine. That seems to be more of an irritation than a big problem right now.
>
> Thanks for the suggestion though.
>
>
>
>
>
> On Sat, Apr 18, 2020 at 5:48 PM Jared Brees <fromj2sitsme at msn.com> wrote:
>
> > If you disable both rules, does external traffic still hit your pfSense
> > webGUI? If so, those rules aren't the issue - you've got another setting
> > elsewhere. If it just times out, one of those rules isn't setup right.
> > Enable one and see what happens.
> >
> > ________________________________
> > From: Cialug <cialug-bounces at cialug.org> on behalf of Scott Yates <
> > Scott at yatesframe.com>
> > Sent: Saturday, April 18, 2020 17:04
> > To: Central Iowa Linux Users Group <cialug at cialug.org>
> > Subject: Re: [Cialug] PfSense
> >
> > Huh, those rules look right to me. I am not sure what is going on there.
> >
> > On Sat, Apr 18, 2020 at 4:58 PM Tom Sellers <tsellers2009 at gmail.com>
> > wrote:
> >
> > > I already have rules for both http and https traffic
> > > [image: image.png]
> > >
> > > On Sat, Apr 18, 2020 at 4:20 PM Scott Yates <Scott at yatesframe.com>
> > wrote:
> > >
> > > > It sounds like you need to port forward your web traffic to your
> > internal
> > > > web server.
> > > > Go to the Firewall menu, then the NAT menu.
> > > > Then Add a rule that forwards the port you want to use, 80 for
> > > unencrypted
> > > > traffic, or 443 for https traffic.
> > > >
> > > >
> > > > On Sat, Apr 18, 2020 at 4:14 PM Tom Sellers <tsellers2009 at gmail.com>
> > > > wrote:
> > > >
> > > > > is anyone using this package that could answer some questions?
> > > > >
> > > > > I recently set up a computer with this and have not had any issues
> > > until
> > > > I
> > > > > tried using a dynamic dns provider which I have used successfully
> in
> > > the
> > > > > past. Now I am unable to do so.
> > > > >
> > > > > When I go to a link at the dynamic dns which resolves to my network
> > IP
> > > > > address it comes up with my pfsense login page. It should go to my
> > > > > internal web server.
> > > > > _______________________________________________
> > > > > Cialug mailing list
> > > > > Cialug at cialug.org
> > > > > https://www.cialug.org/cgi-bin/mailman/listinfo/cialug
> > > > >
> > > > _______________________________________________
> > > > Cialug mailing list
> > > > Cialug at cialug.org
> > > > https://www.cialug.org/cgi-bin/mailman/listinfo/cialug
> > > >
> > > _______________________________________________
> > > Cialug mailing list
> > > Cialug at cialug.org
> > > https://www.cialug.org/cgi-bin/mailman/listinfo/cialug
> > >
> > _______________________________________________
> > Cialug mailing list
> > Cialug at cialug.org
> > https://www.cialug.org/cgi-bin/mailman/listinfo/cialug
> > _______________________________________________
> > Cialug mailing list
> > Cialug at cialug.org
> > https://www.cialug.org/cgi-bin/mailman/listinfo/cialug
> >
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> https://www.cialug.org/cgi-bin/mailman/listinfo/cialug
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> https://www.cialug.org/cgi-bin/mailman/listinfo/cialug
>
More information about the Cialug
mailing list