Archive > 19.1 Legacy Series

WAN port forward to static host on LAN

(1/2) > >>

thoth:
In my NAT port forwarding rules I have:

A host that gets its IP address from DHCP:

--- Code: --- WAN TCP * * WAN address 2222 10.2.0.19 22 (SSH)

--- End code ---

And another with a static IP address:

--- Code: --- WAN TCP * * WAN address 2322 10.2.0.220 22 (SSH)

--- End code ---

I can ssh through the WAN to the first host by port 2222, but not the second host by 2322

Curiously from the first host I can ssh to the second host (behind the firewall) by port 22, so I am fairly certain that the second host has correctly set it's static IP.  The only difference that I can discern is that the first host is DHCP and the second is static.

amitis5:
I'm having this exact same issue.  First port forward rule works, none of the others do.s

thebraz:
Could you please try to deactivate DHCP and use only static IP?

I have this configuration and no problem at all port-forwarding on static addressed machines in LAN.

Best Wishes

thoth:
I need DHCP on this network, however, the range that DHCP uses does not conflict with the static IP I am using.

As an alternative I have added static mapping for many of the hosts which does seem to work. 

However, hosts that are set to static IP addresses within the OS are not routable.

Furthermore, when attempting the layer 2 metallb tutorial:

https://metallb.universe.tf/tutorial/layer2/

I can see in `k get svc` I do get a static IP address from the service:

```
k get svc nginx
NAME    TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)        AGE
nginx   LoadBalancer   10.106.58.106   10.2.0.86   80:30025/TCP   94m
```

But, again, anything with a static IP address not set by DHCP cannot be routed to.

thoth:
I've also enabled BGPv4 and tried both enabling and disabling OSPF, but I still do not seem to be able to get static hosts to have the same sort off peerage as the DHCP hosts in my network

Navigation

[0] Message Index

[#] Next page