Am 18.05.2018 um 23:29 schrieb Andrea Venturoli:
…
Let's say I have a router connected to the Internet on one side and to
a LAN with private IPs on the other.
I want some clients from outside to be able to connect to a TCP
service on a machine on the LAN: they should connect to port X on the
fi
On Thu, 14 Jun 2018, at 16:01, Andrea Venturoli wrote:
> On 05/21/18 18:10, Andrea Venturoli wrote:
>
> > Thanks to anyone who answered.
> >
> > I'm currently trying net/bounce, as suggested by Eugene.
> > If that won't work properly, I'll sure give plugdaemon a shot.
>
> Just an update in case any
On Thu, Jun 14, 2018 at 9:01 AM, Andrea Venturoli wrote:
> On 05/21/18 18:10, Andrea Venturoli wrote:
>
> Thanks to anyone who answered.
>>
>> I'm currently trying net/bounce, as suggested by Eugene.
>> If that won't work properly, I'll sure give plugdaemon a shot.
>>
>
> Just an update in case a
On 05/21/18 18:10, Andrea Venturoli wrote:
Thanks to anyone who answered.
I'm currently trying net/bounce, as suggested by Eugene.
If that won't work properly, I'll sure give plugdaemon a shot.
Just an update in case anyone is interested...
Bounce is still dying occasionally; in some way it
On 05/21/18 13:16, Luciano Mannucci wrote:
On Fri, 18 May 2018 23:29:33 +0200
Andrea Venturoli wrote:
Does anyone have a good suggestion for a program similar to the above ones?
I require nothing fancy, I just want it to be reliable.
The oldest, the simplest, the most reliable (I'm still usin
On Fri, 18 May 2018 23:29:33 +0200
Andrea Venturoli wrote:
> Does anyone have a good suggestion for a program similar to the above ones?
> I require nothing fancy, I just want it to be reliable.
The oldest, the simplest, the most reliable (I'm still using it, and
it shoud be in the ports):
Peter
20.05.2018 0:26, Andrea Venturoli wrote:
>> Additional advantage of this approach is that
>> internal hosts will see real public IP address of connecting external host
>> instead of your own.
>
> This is exactly what I don't want, as, unfortunately, we have some devices
> which will refuse conne
On 05/19/18 00:08, Reshad Patuck wrote:
Hi,
If you are running pf or ipfw on your router you could use a forward
rule to forward connections that come in on a certain internet IP and
port to a select internal IP or port.
Thanks.
I'm in fact using ipfw, but already have quite a complex rule s
On 05/19/18 03:10, Eugene Grosbein wrote:
You don't need any additional software at all.
Just instruct FreeBSD kernel to do what you need, it will do that just fine.
Thanks.
In fact I've used ipfw nat in the past, but I'd rather use a userland
daemon: doing things at rule level makes it more
19.05.2018 4:29, Andrea Venturoli wrote:
> Let's say I have a router connected to the Internet on one side and to a LAN
> with private IPs on the other.
> I want some clients from outside to be able to connect to a TCP service on a
> machine on the LAN: they should connect to port X on the firew
Ipfw's internal nat will do this out of the box.
-- Karl
Original Message
From: m...@netfence.it
Sent: May 18, 2018 16:29
To: freebsd-net@freebsd.org
Subject: Proxy a TCP connection
Hello.
Let's say I have a router connected to the Internet on one side and to a
LAN with private IPs on the
Hi,
If you are running pf or ipfw on your router you could use a forward rule to
forward connections that come in on a certain internet IP and port to a select
internal IP or port.
If you don't have a firewall running and can install ports on your router have
a look at relayd, it should do wha
12 matches
Mail list logo
