Quantcast
Channel: Programmer's Town - Unix
Viewing all articles
Browse latest Browse all 227

//programmer2640.rssing.com/chan-67947766/article208-live.html

$
0
0

There is a gateway on freebsd with several .
1.2.3.4 - the main channel (real ip)
192.168.123.2 - the channel of the second provider (private ip)
10.0.0.1 - an internal network
And still heels  and VPN are lifted.
It is necessary  ports
1.2.3.4:80-> 10.0.0.11:80
1.2.3.4:443-> 10.0.0.11:443
192.168.123.2:1234-> 10.0.0.18:3389
Asked the administrator it to make. It made something and faded in holiday.
Made partially.  80 and 443 basically, works, but does not work at stopping from a network of the second provider - most likely, it is connected by that packets there forcedly through the second interface go, without a difference the request whence came.
And  192.168.123.2:1234 at all does not work.
The Adminsky rights at me are, but in   I understand nothing.
The list corrected a firewall big and terrible therefore I will not quote.
Council how rules  taking into account my tasks should look is necessary.
Present rules are, seemingly, registered in files natd*.conf - them there a little, seemingly, that for each interface.
Rules look as
redirect_port tcp 10.0.0.18:3389 3102
But it is not enough of it for operation.


Viewing all articles
Browse latest Browse all 227

Latest Images

Trending Articles



Latest Images