From: Lonnie Cumberland <lonnie@neenet.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] eth0 problems
Date: Sat, 28 Aug 2004 22:33:31 -0400 [thread overview]
Message-ID: <4131407B.3090209@neenet.com> (raw)
In-Reply-To: <200408282153.02612.menola@sbcglobal.net>
Is there a way for me to tell if the TUN module has been compiled into
this kernel?
I looked at the src for the kernel via the "make menuconfig" and it
showed the TUN/TAP device as a Module. Also the module exists in the
/lib/modules directory.
how can I load the tun module?
Thanks,
Lonnie
Joe Menola wrote:
>On Sat August 28 2004 7:55 pm, Lonnie Cumberland wrote:
>
>
>>I just looked at the kernel sources for my 2.6.3-7mdk kernel and
>>TUN/TAP has already been compiled in as a module.
>>
>>Although there is no /dev/net/tun0 listed or /dev/tun0 as well
>>
>>
>
>/dev/net/tun0 wont exist until module "tun" is loaded.
>
>If you wish to setup a tun device, I've created a small and raw howto for my
>own use on what works for me. Should give you a decent start...
>
>
>
>First off, kernel needs tun networking support compiled in and module loaded.
>
>"eth0" =host device connected to lan
>"/etc/rc.d/init.d" = path to init scripts
>adjust as needed
>
> Setup Masquerade
>
>Run in terminal as root:
> # iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
> #/etc/rc.d/init.d/iptables save
>
> Sanity check
> #/etc/rc.d/init.d/iptables start
> #/etc/rc.d/init.d/iptables status
>
>Rule "Chain POSTROUTING (policy ACCEPT)"
> should contain:
> "MASQUERADE all -- anywhere anywhere"
>
> Create Ifup scripts
>
>1- Create file: /etc/qemu-ifup
>
>#!/bin/sh
>sudo /sbin/ifconfig $1 <ip address>
>sudo /etc/qemu-iptables
>#end
>
>2- #chmod 777 /etc/qemu-ifup
>
>3- Create file /etc/qemu-iptables
>
>#!/bin/sh
>/etc/rc.d/init.d/iptables stop
>echo "1" >&/proc/sys/net/ipv4/ip_forward
>/etc/rc.d/init.d/iptables start
>#/usr/sbin/dhcpd -q tun0
>#end
>
>4- #chmod 777 /etc/qemu-iptables
><<<<<<<<<<
>
>
>
>_______________________________________________
>Qemu-devel mailing list
>Qemu-devel@nongnu.org
>http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
>
>
>
next prev parent reply other threads:[~2004-08-29 3:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-28 21:54 [Qemu-devel] eth0 problems Lonnie Cumberland
2004-08-28 23:13 ` Joe Menola
2004-08-28 23:04 ` Lonnie Cumberland
2004-08-29 0:18 ` Joe Menola
2004-08-29 0:33 ` Jim C. Brown
2004-08-29 0:43 ` Joe Menola
2004-08-29 1:03 ` Jim C. Brown
2004-08-29 0:55 ` Lonnie Cumberland
2004-08-29 1:54 ` Mark Williamson
2004-08-29 2:53 ` Joe Menola
2004-08-29 2:33 ` Lonnie Cumberland [this message]
2004-08-29 5:39 ` Joe Menola
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4131407B.3090209@neenet.com \
--to=lonnie@neenet.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).