Go Back   DaemonForums > OpenBSD > OpenBSD General

OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below.

Thread Tools Display Modes
  #1   (View Single Post)  
Old 13th July 2013
openbsdfreshman openbsdfreshman is offline
New User
Join Date: Jul 2013
Posts: 2
Default PPPX vs TUN

NPPD.conf man page marks the use of two interfaces, pppx and tun.

After reading and re-reading the man pages for both tun, pppx and npppd.conf, why would I use pppx over tun?

Is one better than the other? Is one more secure over the other? I realize that pppx uses pipex to accelerate tunneling traffic, does tun?

The examples at the end of the npppd.conf manpage shows one example for pppx use and one for tun but doesn't state why one was used over the other.
Reply With Quote
  #2   (View Single Post)  
Old 13th July 2013
jggimi's Avatar
jggimi jggimi is online now
More noise than signal
Join Date: May 2008
Location: USA
Posts: 6,387

Hello, and welcome!

The tun(4) driver is only used for userland access into the kernel network stack. Each access path requires a separate tun device, and they usually need to be preconfigured. The default install provides only /dev/tun0 through /dev/tun3, you will need to use MAKEDEV(8) if you have more than four tun devices.

The pppx(4) driver is multiplexed, and all pppx devices created are addressable via /dev/pppx0.


In summary, pppx(4) is a better fit for simultaneous dynamic use as an access path in a VPN solution, such as might be used with npppd(8). The tun(4) driver is a better fit for preconfigured network connections in a VPN solution, such as what might be used with net/openvpn.
Reply With Quote

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT. The time now is 11:43 AM.

Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2018, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick