On 5/20/2021 9:17 AM, Robert Grizilo wrote:
> Greetings,
>
> I've done this once long time ago but can't remeber how and unable to
> find some example
>
> I want to NAT inside same network.
>
> 192.168.1.2 = shorewall pc
> 192.168.1.3 = synology nas
>
> lan:192.168.1.2:5000 ->
Hello Alexander,
On Thu, May 20, 2021, at 7:33 AM, Alexander Stoll wrote:
> When you recieve only a /64 subnet, this gets gets realy complicated and
> depends on every involved software which has to support subnets smaller
> than /64.
> In this situation you may be better off with a NAT solution.
Am 20.05.2021 um 13:04 schrieb tha...@letterboxes.org:
So with this I end up with NAT'd IPv6. Which I thought you weren't
supposed to do.
yes, this is ugly and something to avoid when ever possible...
But I guess if I'm going to have private internal IPv6 addresses,
either static &/or
Hello,
> SNAT([2600:::::53]) [2600:::::]/64 enp2s0
>
> with that, you should now see the 'echo reply'.
Wow, that worked!
I just assumed that since I wasn't seeing DROP/REJECT of packets, that I didn't
have a problem like that. Never thought that the packets
Greetings,
I've done this once long time ago but can't remeber how and unable to find some
example
I want to NAT inside same network.
192.168.1.2 = shorewall pc
192.168.1.3 = synology nas
lan:192.168.1.2:5000 -> lan:192.168.3:5000
lan:192.168.1.2:5001 -> lan:192.168.3:5001
