Now that my network mystery has been resolved, I thought I would explain my challenges.
for this to make sense I need to add a bit of backstory.
my problem started about 12 months ago, I had purchased an static IP block from AT&T and
the bandwidth package. it was fairly small but it worked with a pace 5238ac
modem Router from AT&T and it was working OK. it didn't have much in the way of
lan control; I wanted better Wi-Fi and better lan client control .
so I went out and bought
a nighthawk and started connecting it in a cascade to the
Internet where the nighthawk backed up the AT&T router .
come January this year I was looking at bandwidth short fall and decided to get an upgrade
I ordered the upgraded bandwidth package and it was installed in early February.
I ordered the upgraded bandwidth package and it was installed in early February.
when the AT&T tech did
that installation, he swapped out the pace router for the arris BGW210-700 router
and all hell broke loose.
For almost a month I had been trying to get that cascade working from the
For almost a month I had been trying to get that cascade working from the
BGW210-700 to the Nighthawk. I explored
Google, mfgr docs, i looked everywhere trying to find samples of how
to make it work.
from all I read it should have worked but I couldn't get it to
It was at this point that I decided to appeal to the users on the fedora
list and several gentlemen
were kind enough to help me clear the mist from my path as it were.
for a while we tried to get the cascading to work with no joy. I decided to bite the bullet pull
the nighthawk out of the loop and just live with the AT&T router
The next couple of weeks I moved old router lan clients to the new router topology.
The next couple of weeks I moved old router lan clients to the new router topology.
I got my lan clients moved over, I also got the static IP visible to the world but still I
could not connect the internet to my web server.
The last clue in the puzzle came from port examining from firewalls out to the Internet
The last clue in the puzzle came from port examining from firewalls out to the Internet
why was I not connecting??
I found this nifty tool in the world from some company called getsignal . it would look at
your ports from the outside and tell you their status. so I keyed in HTTP and Https ports and
sure enough from the Internet they were blocked
At this point all that remained was to use the port mapping and service creation on the
At this point all that remained was to use the port mapping and service creation on the
AT&T router to map the external wan side ports to the lan web server and it worked.
I renewed my letsencrypt certs and I am on down the road.
i even got my 'A' from my qualys ssl test! {Yeah}
Once again thanks to all that assisted me on this horrendous ride
but it's working now thank you again very much
On Mon, Apr 18, 2022 at 8:07 PM Ed Greshko <ed.greshko@xxxxxxxxxxx> wrote:
On 19/04/2022 07:28, Jack Craig wrote:
> this mystery has been resolved and my server is online.
Is the solution easy to describe?
--
Did 황준호 die?
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure