Swith Port Forwarding
Hello,
I have a port forward setup on my Archer AX20 router. Currently the AX20 serves as the DHCP server, however I have upgraded to a dedicated router and the T1600-28TS swith will now function as the DHCP server.
I have once again setup the port forward on the new router, but I can't access the device that is supposed to be accessible via the port forward as the device is connected to the switch and the switch assigns the IP addresses.
How can I "transfer" the port forward via the switch?
The device targeted by the port forward is a Raspberry Pi which runs home assistant and this Raspberry Pi needs to see devices which connects to and receives IP addresses from the switch.
Any help would be appreciated.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @Charl99
Thanks for posting in our business forum.
You cannot port forward on a switch because it is not a NAT device. Do it on the router.
- Copy Link
- Report Inappropriate Content
“How can I "transfer" the port forward via the switch?”
In general, you cannot set up port forwarding on a switch. A typical switch just does not provide this function. That’s O.K. I don’t think you need it.
“ The raspberry Pi is getting the static IP 192.168.0.6 from the switch.”
I read this that you have created a DHCP reservation for your raspberry Pi on the switch’s DHCP server. It would be better if you have really configured it with a static IP address, instead of DHCP, but that's not the issue.
If the port forwarding is set up correctly on the router, i.e. it points to 192.168.0.6 and the correct port, that should work without any additional configuration. If it does not work, that IP address is simply not accessible on the given port from your router. There must be some other misconfiguration on your network.
Also, if you haven’t disabled the DHCP server on your router, you may try that. Having multiple DHCP servers on the network is a little tricky.
- Copy Link
- Report Inappropriate Content
Hi @Charl99
Thanks for posting in our business forum.
You cannot port forward on a switch because it is not a NAT device. Do it on the router.
- Copy Link
- Report Inappropriate Content
Hi @Clive_A,
Thank you for the response.
As mentioned above the port forward is setup on the router and the port forward is functioning as intended when the Raspberry Pi is connected to the router directly.
However my switch is connected to the router and then all the devices is connected to the switch. The switch is functioning as the DHCP server. The raspberry Pi is getting the static IP 192.168.0.6 from the switch.
When I try to access the Raspberry Pi from outside the network it is not accessible as the port forward is not being passed on to the switch. I want to know how to configure the switch so that the port forward is passed on via the switch.
- Copy Link
- Report Inappropriate Content
“How can I "transfer" the port forward via the switch?”
In general, you cannot set up port forwarding on a switch. A typical switch just does not provide this function. That’s O.K. I don’t think you need it.
“ The raspberry Pi is getting the static IP 192.168.0.6 from the switch.”
I read this that you have created a DHCP reservation for your raspberry Pi on the switch’s DHCP server. It would be better if you have really configured it with a static IP address, instead of DHCP, but that's not the issue.
If the port forwarding is set up correctly on the router, i.e. it points to 192.168.0.6 and the correct port, that should work without any additional configuration. If it does not work, that IP address is simply not accessible on the given port from your router. There must be some other misconfiguration on your network.
Also, if you haven’t disabled the DHCP server on your router, you may try that. Having multiple DHCP servers on the network is a little tricky.
- Copy Link
- Report Inappropriate Content
Hi @Charl99
This is doable theoretically. You gotta configure it this way.
in your DHCP settings on the switch, you are required to put the gateway IP address. You have to put the router IP there.
You can verify the access to the server by connecting a device to the router LAN port and put the IP:internal_port of the server and access it. If in the LAN, you can access it without an issue, then it should work on the WAN as well.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 726
Replies: 4
Voters 0
No one has voted for it yet.