Displaying 5 results from an estimated 5 matches for "netlink_dev".
2002 Jul 07
2
Metadata socket and net2str() error
...fconfig tap0 -arp
/etc/tinc/iwan/hosts/Client: (on both machines)
-----BEGIN RSA PUBLIC KEY-----
...
-----END RSA PUBLIC KEY-----
Address = 192.168.0.9
Subnet = 10.0.0.0/16
General
-------
For both machines I have added the following to /etc/modules:
netlink_dev
ethertap
and the following to /etc/modules.conf:
alias char-major-36 netlink_dev
alias tap0 ethertap
options tap0 -o tap0 unit=0
alias tap1 ethertap
options tap1 -o tap1 unit=1
(No details, except for the public keys and my external IP, have been
*intentionally* ;) left out...
2006 Jul 18
0
ip tunnel and kernel 2.6.17.6
hi all
i ran a few times in troubles with iproute an rtnetlink or netlink_dev
with newer kernels.
i.e. i can compile and recompile the kernel and iproute (all from
sources)... and as soon as i like to add a route to a tunnel:
ip route add 192.168.0.0/24 dev gre_tun
i get:
rtnetlink no such device.
ip link / ip addr is showing the tunnel (also ifconfig).
i assume, that the...
2000 Sep 10
2
tinc SECURITY INFORMATION - Unauthorized access to VPN
Although we (the authors of tinc) have done our best to make tinc as
secure as possible, an unfortunate combination of encryption and key
exchange techniques has created a hole in at least all versions of
tinc >= 0.3, including the current CVS version.
Exploit:
If somebody can intercept the meta protocol to a host that is running
a tinc daemon, it is possible to decrypt the passphrase, which
2000 Sep 10
2
tinc SECURITY INFORMATION - Unauthorized access to VPN
Although we (the authors of tinc) have done our best to make tinc as
secure as possible, an unfortunate combination of encryption and key
exchange techniques has created a hole in at least all versions of
tinc >= 0.3, including the current CVS version.
Exploit:
If somebody can intercept the meta protocol to a host that is running
a tinc daemon, it is possible to decrypt the passphrase, which
2001 May 08
4
tap1 problem
...ev/tap0 c 36 16
chown 0.0 /dev/tap0
The second tap1 device was created too:
mknod -m 600 /dev/tap1 c 36 17
chown 0.0 /dev/tap1
I am running a Linux 2.2.18 kernel, and the following lines have been
added to the /etc/modules.conf file:
alias tap0 ethertap
alias tap1 ethertap
alias char-major-36 netlink_dev
Now, when I run the following command:
/sbin/ifconfig tap0 hw ether fe:fd:00:00:00:00
It works without a problem.
However, when I try to get the other tap1 device working, and type:
/sbin/ifconfig tap1 hw ether fe:fd:00:00:00:00
This command gives the following error message:
SIOCS...