On Mon, Mar 28, 2022 at 3:11 PM Jack Craig <jack.craig.ap...@gmail.com> wrote:
> On Mon, Mar 28, 2022 at 7:22 AM Go Canes <letsgonhlcan...@gmail.com> wrote:
>> I've been reluctant to contribute as well, due to not really
>> understanding the setup. But given the Cable Modem was replaced, I've
>> been wondering if this is as simple as the prior modem being in
>> "bridge mode" - i.e. passing all traffic without usingg NAT or routing
>
>
> i had thought of using the firewalls of both the ATT rtr & NH firewalls
> passing through
> http & https. also i thought bridge mode wsa a security risk???
*Anything* exposed to the internet suffers the security risk
(including your web server). If the NH (Nighthawk, I am assuming) is
running in "firewall" mode, putting the Cable Modem in bridge mode
moves the risk from the Cable Modem to the Nighthawk. IMHO, *you*
control the updates to the Nighthawk, so you can make sure it is
up-to-date. Your ISP may or may not keep the Cable Modem up-to-date.
Since you have two firewall/NAT routers (if I have understood things
correctly), you might consider connecting all the Internet exposed
systems to the Cable Modem (assuming it has multiple ports), and put
your private systems behind the Nighthawk.
Crude diagram of what I am suggesting that may or may not survive
formatting.....:
ISP - Cable Modem -| - Web Server
| - something else that needs to be
publicly accessible
| - Nighthawk -|- laptop
| - desktop
(and I have no idea if this fits in with how your ISP has your IP
subnet configured - I am starting with a clean slate.)
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
