Re: network mystery!!??

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 4/4/22 12:07, Jack Craig wrote:


On Mon, Apr 4, 2022 at 12:54 AM Samuel Sieb <samuel@xxxxxxxx <mailto:samuel@xxxxxxxx>> wrote:



    If you connect the Nighthawk to the BGW210 using one of the LAN
    ports on
    the Nighthawk, everything would be on the 192.168.1.x subnet and you
    could use the same SSID on both devices.  You would need to disable the
    DHCP server on the Nighthawk and most likely need to give the Nighthawk
    a static IP address on the LAN because they usually don't support
    getting it from DHCP.

*
*
*this approach makes sense.*

*so to implement this change,
*
*1. update networkmanager to assign 108.220.213.121 to the server(currently 10.0.0.101) and plug it into the att rtr*

You can't use that IP address unless you make some major changes to the config on the ATT router. And if those changes aren't made correctly, you would lose all internet access. I hope you aren't paying extra for the subnet vs a single static address.

You need to give a static 192.168.1.x address to the server. Make sure that the static addresses you are using are outside the range of the DHCP server.

*2. disable dhcp on nh rtr*

yes

*3. enable wifi for 2.4 & 5mhz on the att rtr*

I thought you were already using it. You can use the same SSID on both routers after this rearrangement.

*4. set up a static ip for nh rtr on the 192.168.1.0*

yes.  Make sure you're setting the LAN address, not the WAN address.

*5. plug nh rtr into the att rtr leaving switch attached to the nh rtr*

The switch can be plugged into either router, since it's all one subnet now. The NH WAN port should not be connected to anything.

Once this is all done, you can configure a port forward on the ATT router to access the web server.
_______________________________________________
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



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux