> This freebsd server in an internal lan server, IP 192.168.1.254.
> 192.168.1.212 is gateway on internet.
[...]
tap --> tun
solved :-)
Pol
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To un
Hi all :-)
This freebsd server in an internal lan server, IP 192.168.1.254.
192.168.1.212 is gateway on internet.
I've an easy config:
DestinationGatewayFlagsRefs Use Netif Expire
default192.168.1.212 UGS 031807em0
10.20.10.0/24
On Wednesday 27 of April 2011 01:15:09, Ryan Coleman wrote:
> Maciej,
> Here you go:
> Ryan-Colemans-MacBook-Pro:~ ryanjcole$ netstat -rn
> Routing tables
> Internet:
> DestinationGatewayFlagsRefs Use Netif
> Expire default10.0.1.1 UGSc
On Apr 26, 2011, at 9:07 AM, Diego Arias wrote:
>
> If you need to route LAN - TO - LAN just enable the client-to-client. Its a
> Security Feature of OpenVPN
>
> http://www.secure-computing.net/wiki/index.php/OpenVPN/Routing
>
I've done th
On Apr 26, 2011, at 3:50 PM, Ryan Coleman wrote:
> On Apr 26, 2011, at 9:53 AM, Maciej Milewski wrote:
>
>> On Tuesday 26 of April 2011 15:45:22, Ryan Coleman wrote:
>>> I have a bridge set up, pingable... but can't ping the em1 (192.168.46.2)
>> from the remote machine.
>> ...
>>> push "route
On Apr 26, 2011, at 9:53 AM, Maciej Milewski wrote:
> On Tuesday 26 of April 2011 15:45:22, Ryan Coleman wrote:
>> I have a bridge set up, pingable... but can't ping the em1 (192.168.46.2)
> from the remote machine.
> ...
>> push "route 192.168.47.0 255.255.255.0"
>
> Have you tried adding the r
On Tuesday 26 of April 2011 15:45:22, Ryan Coleman wrote:
> I have a bridge set up, pingable... but can't ping the em1 (192.168.46.2)
from the remote machine.
...
> push "route 192.168.47.0 255.255.255.0"
Have you tried adding the route to 192.168.46.0/24 subnet into the vpn client?
You want to
y one guide - and am routing
> everything from 192.168.47.0/24 to 0.0.0.0/32 (I'm not well versed on this
> specific area but that seems like it should be 0/0, right?)
>
> Relevant rc.conf:
> defaultrouter="192.168.46.254"
> hostname="nbserver1.a
On Apr 26, 2011, at 8:32 AM, Nathan Vidican wrote:
> On Mon, Apr 25, 2011 at 10:36 PM, Ryan Coleman wrote:
>>
>> I've got an OpenVPN connection working to my remote server, but I want to
>> route the traffic to the local LAN.
>>
>> I have a bridge set up, pingable... but can't ping the em1 (1
On Mon, Apr 25, 2011 at 10:36 PM, Ryan Coleman wrote:
>
> I've got an OpenVPN connection working to my remote server, but I want to
> route the traffic to the local LAN.
>
> I have a bridge set up, pingable... but can't ping the em1 (192.168.46.2)
> from the remote machine.
>
> Server.conf:
> lo
On Tuesday 26 of April 2011 04:38:29, Ryan Coleman wrote:
> Also:
> [root@nbserver1 /usr/home/ryanc]# ifconfig
> em0: flags=8943 metric 0
> mtu 1500 options=98
> ether 00:14:22:15:dc:65
> inet 192.168.46.2 netmask 0xff00 broadcast 192.168.46.255
> media: Ethernet autosel
Also:
[root@nbserver1 /usr/home/ryanc]# ifconfig
em0: flags=8943 metric 0 mtu
1500
options=98
ether 00:14:22:15:dc:65
inet 192.168.46.2 netmask 0xff00 broadcast 192.168.46.255
media: Ethernet autoselect (1000baseT )
status: active
tap0: flags=8943 metric
I've got an OpenVPN connection working to my remote server, but I want to route
the traffic to the local LAN.
I have a bridge set up, pingable... but can't ping the em1 (192.168.46.2) from
the remote machine.
Server.conf:
local 192.168.46.2
port 1194
proto udp
dev tap
ca keys/cacert.pem
cert ke
link#1UC rl0
ff02::%rl1/32 link#2UC rl1
ff02::%lo0/32 ::1 UC lo0
The output of netstat -rn after starting OpenVPN:
Routing tables
Internet:
Des
14 matches
Mail list logo
