|
|
I have a tun device setup on a Linux machine (server):
tun_ovpn Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.8.0.1 P-t-P:10.8.0.2 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:418 errors:0 dropped:0 overruns:0 frame:0
TX packets:430 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:28628 (27.9 KiB) TX bytes:29528 (28.8 KiB)
And on a client:
tun_ovpn Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.8.0.6 P-t-P:10.8.0.5 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:415 errors:0 dropped:0 overruns:0 frame:0
TX packets:426 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:28140 (27.4 KiB) TX bytes:29172 (28.4 KiB)
What if I do this on the server:
ifconfig tun_ovpn:1 10.8.0.1 pointopoint 10.8.0.6
Which then creates this:
tun_ovpn: Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.8.0.1 P-t-P:10.8.0.6 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
Is this kosher? Will my computer catch fire?
I'm doing this as a hack to allow quagga/ospfd correctly figure out the
peer in a point-to-point setup. It seems to play nice, but I just wanted
to make sure that setting up the virtual interface on a virtual
interface is reasonably safe.
______________________
OpenVPN mailing lists
https://lists.sourceforge.net/lists/listinfo/openvpn-users
|