Re: confusion with natd
From: Juhani Tali (juhani_at_kernel.ee)
Date: 10/01/04
- Previous message: Mikhail P.: "confusion with natd"
- In reply to: Mikhail P.: "confusion with natd"
- Next in thread: Mikhail P.: "Re: confusion with natd"
- Reply: Mikhail P.: "Re: confusion with natd"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 01 Oct 2004 09:51:49 +0300 To: miha@ghuug.org
Mikhail P. wrote:
> HOST_A:
> FreeBSD, serves as gateway (NAT) for LAN (192.168.0.0/24)
> has two NICs:
> rl0 - internal (192.168.0.1)
> rl1 - external (connected to DSL modem), runs natd (natd -n rl1)
> net.inet.ip.forwarding=1
> openvpn from ports
>
> HOST_B:
> FreeBSD, remote host, single NIC, public IP.
> net.inet.ip.forwarding=1
> openvpn from ports
I would set it up like so:
This one in host B
> natd -interface rl1
And this in host A
> natd -port 8568 -interface tun0
You need to translate all the 192.168.0.x to tunnel's address and you
cannot do it in host B, because it has no direct connection to 192.168.0.x.
Another solution is with routing, so host B has direct access to the
192.168.0.x network.
> I have been pulling hair off my poor head for few hours on this issue, but did
> not come to solution, so I'm looking for advises.
Juhani Tali
_______________________________________________
freebsd-isp@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isp
To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"
- Previous message: Mikhail P.: "confusion with natd"
- In reply to: Mikhail P.: "confusion with natd"
- Next in thread: Mikhail P.: "Re: confusion with natd"
- Reply: Mikhail P.: "Re: confusion with natd"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|