constant tun interface

[Sergey Zaharchenko]

On Tue, Jun 29, 2004 at 09:02:23AM +0400,
 Lev Klimin probably wrote:
> Hello!
> 
> I have little trouble. I have 4.10-release with ppp ant ipnat. On
> startup ipnat reload it's rules with interface tun0 in statments which
> is ppp's device. But before running ppp, there is no tun device in
> system
> [8:48:04][~]:garbage# ifconfig
> fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         inet 195.161.208.151 netmask 0xffffffc0 broadcast 195.161.208.191
>         ether 00:a0:c9:4b:09:29
>         media: Ethernet 10baseT/UTP <full-duplex>
>         status: active
> fxp1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         inet 172.16.0.9 netmask 0xfffffff8 broadcast 172.16.0.15
>         ether 00:a0:c9:b6:59:a1
>         media: Ethernet autoselect (100baseTX <full-duplex>)
>         status: active
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
>         inet 127.0.0.1 netmask 0xff000000 
> ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
> faith0: flags=8002<BROADCAST,MULTICAST> mtu 1500
> [8:48:09][~]:garbage# 
> 
> Because of lack of tun interface, further ipnat rules don't work. I
> can reload ipnat then ppp starting, and it's OK. Can I build my
> kernel to make tun interface on startup sach as ppp interface?

Maybe you could do some ifconfig(8) magic, but you definitely could use
ppp's built-in NAT (by inlcuding `nat enable yes' in the config file).
HTH,

-- 
DoubleF
Everything is worth precisely as much as a belch, the difference being
that a belch is more satisfying.
		-- Ingmar Bergman
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20040629/791429ca/attachment.bin