I'll do my best to clarify it for you. What specifically are you trying to understand about LAN?
I'll do my best to clarify it for you. What specifically are you trying to understand about LAN?
Hello, I’m not entirely sure about what I’ve accomplished yet. The LAN is finally operational. The first image shows the setup before, and the second depicts the present state. I have one satellite dish connected to a Ubiquiti POE-24-24W device, which now also links to the new switch I purchased (TP-LINK TL-SF1005D). From this switch, I have Ethernet cables reaching several computers. My confusion arises here: when I ran the "arp -a" command, I saw two devices connected—192.168.1.7 and 192.168.1.10—and also a strange address: 192.168.1.254. I thought the little box functioned as a router, but it seems to be just a power supply or protection for my satellite dish. Could this address belong to the switch itself? If I configure the network with a subnet mask of 255.255.0.0 and a default gateway of 192.168.0.0, the devices should communicate internally but not access the internet. With a subnet mask of 255.255.255.0 and a gateway at 192.168.1.254, both devices could share the LAN and also reach the internet. I wasn’t aware I could achieve this using just a switch. Sorry for the lengthy explanation, but I have another question... Earlier, I asked my ISP to assign me a public IP address like 62.???.???.?21, which would be routed to 192.168.1.7. I did this because some games experienced multiplayer problems due to NAT and port forwarding. Will this still work in the current switch setup?
The default gateway refers to the IP address that routes traffic to other networks when no specific route exists. The 192.168.0.0 indicates the subnet range, but it doesn't describe a physical device—it's just an address used for communication.
I noticed that 192.168.0.0 isn't a valid address for your network devices...that explains why they have LAN connectivity but not WAN access. They can transmit PDUs to the switch, yet it can't determine the correct destination for subnets. The default gateway should be set to 192.168.0.254, as that seems to be your router given your LAN setup. The Ubiquiti POE-24-24W functions as a power injector using Power-Over-Ethernet; it powers a device on the "Out" port but doesn't handle routing or switching, so no IP should be assigned. Have you tried accessing 192.168.0.254 to check for any GUI? From what I understand, your satellite likely includes a built-in router, or another device between the switch and the satellite isn't listed in your diagram (unless another device on your LAN is acting as a router—which would be unusual). Regarding your public IP reaching 192.168.1.7, you'd need to configure port forwarding on your router's default gateway to route traffic to that device. It's unclear if this will resolve the issue.
Are you certain it's a satellite dish rather than a microwave dish? I haven’t heard of a satellite dish utilizing PoE... Given your injector is from Ubiquiti, it’s likely a Ubiquiti dish. The person managing the remote clearly controls .254. https://www.ubnt.com/products/#airfiber—probably one of these units. You need a gateway to connect to the internet, plus a router or gateway outside your local network. I suspect whatever is on the other end of that dish hosts .254. Your PoE injector and switch aren’t gateways. 255.255.0.0 covers a wide range of IP addresses, and it worked only because you set the correct gateway (192.168.1.254). I’m not sure why you chose that subnet, but it’s probably unnecessary. Stick with a gateway at 192.168.1.254 and a subnet of 255.255.255.0. It’s odd you’re not using DHCP—I’d think .254 would automatically assign IPs.
You're probably still connected through a NAT setup. If your ISP provides an IP address, you'll need to set up your firewall or change your computer's IP manually. Neither option looks right. Also, static IPs are expensive these days—are you dealing with a local provider?
Avoiding DHCP might happen because devices are linked directly, and your ISP could only provide one IP address, expecting you to rely on a router for sharing. This isn’t ideal since private IPs usually prevent gaming or other network activities. It would be useful to observe how things change if a router were involved or if just one client connects through it to see the actual IP assignment.