1 |
tks for the help.. I was really thinking about give dummy interface a try |
2 |
but instead I did solved my problem using an lo alias like this: |
3 |
|
4 |
ifconfig lo:0 192.168.1.2 broadcast 192.168.1.2 netmask 255.255.255.255 |
5 |
|
6 |
supposing that eth0 is on the same network ;) |
7 |
|
8 |
what is funny is that on all LVS guides I'd read, they just mention the |
9 |
sequence: |
10 |
modprobe tun |
11 |
ifconfig tun0 x.x.x.x |
12 |
|
13 |
no one talk about initiate the tun device or to use some other software to |
14 |
do that. |
15 |
|
16 |
tks, |
17 |
|
18 |
claudinei matos |
19 |
|
20 |
On 7/8/06, Hans-Werner Hilse <hilse@×××.de> wrote: |
21 |
> |
22 |
> Hi, |
23 |
> |
24 |
> On Fri, 7 Jul 2006 19:04:41 -0300 |
25 |
> "Claudinei Matos" <claudineimatos@×××××.com> wrote: |
26 |
> |
27 |
> > I'm trying to use tun/tap to assign some ip to my server (since I'll |
28 |
> need it |
29 |
> > to my LVS solution) and I think it's a trivial task to put tun to work, |
30 |
> but |
31 |
> > I'm trying in 3 different machines (with 2 different kernels) and in |
32 |
> both |
33 |
> > they when I try to ifconfig tun0 I get the follow message: |
34 |
> > tun0: error fetching interface information: Device not found |
35 |
> > |
36 |
> > Well, I'd try to look if is something wrong with my kernel configuration |
37 |
> but |
38 |
> > is everything ok since it just need tun/tap support to be compiled (I |
39 |
> did |
40 |
> > tried both module and built-in). |
41 |
> > |
42 |
> > /dev/net/tun is a valid character device with 10, 200 (major/minor) |
43 |
> |
44 |
> ...and, is at first all you get by enabling TUN support in the kernel. |
45 |
> See /usr/src/linux/Documentation/networking/tuntap.txt for more |
46 |
> information about the ioctl() you have to issue in order to register a |
47 |
> tun network device (TUNSETIFF). The docs have a code example, too. |
48 |
> |
49 |
> Oh, and I think OpenVPN has inbuilt functionality to create or remove |
50 |
> tun network devices (independent from OpenVPNs other functionality). |
51 |
> |
52 |
> I've not completely understood what your usage scenario was, but maybe |
53 |
> a dummy network device is enough? |
54 |
> |
55 |
> -hwh |
56 |
> -- |
57 |
> gentoo-user@g.o mailing list |
58 |
> |