parent
8d90ec664b
commit
791a80bc8d
@ -1,17 +1,17 @@
|
|||||||
-----BEGIN PGP SIGNATURE-----
|
-----BEGIN PGP SIGNATURE-----
|
||||||
|
|
||||||
iQJNBAABCgA3FiEEm8dazQnvu0U1Gdmc9s+lqZ57WVcFAmCWxPgZHGd6YW11ZGlv
|
iQJNBAABCgA3FiEEm8dazQnvu0U1Gdmc9s+lqZ57WVcFAmCWykoZHGd6YW11ZGlv
|
||||||
QGxpYnJlbWV4Lm9yZy5teAAKCRD2z6WpnntZVxwuD/9I+cGoN2zbg1BaqNJ16TqA
|
QGxpYnJlbWV4Lm9yZy5teAAKCRD2z6WpnntZV9S2D/9LGUjWjVUaFB6rw9el+n6C
|
||||||
6wDxzr5T0BFan7XY5ulUGYLAeyyOjnH/DgwaufW3MThkWUuDLsal+vYFvZAM417Y
|
rVcQeOZNjLpQc9yIDTtVFV9aQYZNOPWJUx9A+w19Tjpi4Q2Ge5W6fQnnwPy++AQl
|
||||||
jvt0P0asTOS0R/tLLX+8mmIILM2L616b7LhgeBzX9+bXYYd5mDeWGfs73E87Jtad
|
nLgoAEJ5FNeU1uszLJ7Ozf/yDELXYQuLoWtY/j9SPZY4beI5bUv2PoY8m/SK0t9y
|
||||||
fIdEd4MIczkSnYA2W13nQDUay8Ig+x9t7PYhjkzmGSE0rG0ECcQvpxyUt/0xRrWf
|
PSp2k6h99cPSgOno8l6gUFGV6meJr8SnnytA9ArRRNxMdZ9xwdGN0fGNX6kspANV
|
||||||
Eqqkj9f6PSGX3CXKN95grOGzxCfogLPUrxjyufSSx5aJkGRTHci7zNEnzTnWcOxf
|
g7VAUbQmylEL4CrHhyulafZg5zLjdozxsoAZt3A50DKmUR+qxxhaj+EveInhsxa2
|
||||||
mmBFzdfx2u9U7JhkgAnZTTsHMJ08yRn3Ds1U8C74J0tgs5NtyMpc8PBEk2O7w07p
|
9ms+wofDkKE5m6AfxCbf5G6YIwYjdWcVQ1ySztivkwMxHaTApR84E1h5hgF0IqfL
|
||||||
PrP3FcvPgnwdj9kRcmqyJGr4XijopzyXJZ4scUXwZvdmJel+gfvC3Eu215yTCBKn
|
GHLKVGgfNCL6Y/4WshQ2auK/rEClm3m2Sw9YVfQbxI9PiGOcY1xgb4M/9zUYKwQR
|
||||||
jpxFeYRGKERdYIeqkNlHQfMrAQbJzlIFxchihHRZpwaUYHoi4Hl96HFV+YaZePRb
|
cMtKmSWn2TcMZYDNCtl1ckSEftKPpRxOyopJgKR8gb5vk7lbqOD7sO3WiLlfPTKT
|
||||||
oBww+qdJl8pFAd9TxB2gWednHd0IZ7ZmCcJwGpFbRSVhfIA+9C+aaynFLVhblmoX
|
Rvj49Pv6NoyHuQUQFnqGEO5VFnWOBWqeDH4cZ90PLnuF/wNW+vLdIqHJieEzQchI
|
||||||
ctqyWvTdLIe+7ISFbPmN4A/b7VFoziysE3TO76JA11A1ScsyMgfZcdclcUhty0vB
|
DZOXML8RAzOJNuCe4KypLc02GSr39X2bt7J1CFSkyyTT9bJNEKbYROx0+gesaRs8
|
||||||
20kyX6waMslN3FEahrAw1PMCn62v+iFnuiufA/DK2nHnjEZlGcbsvlF8tT5+/PU4
|
Y0GWM5fWsjp63qBTlOxjiGQUtPvGfH4qIt9U/Ue3GfS02kTUvTpZ37oEvcoNTg9P
|
||||||
gNsteaFdw60rx4ob0ZhVRQ==
|
xaTzmhnurUNrALoJfCU6yg==
|
||||||
=Liap
|
=AnOF
|
||||||
-----END PGP SIGNATURE-----
|
-----END PGP SIGNATURE-----
|
||||||
|
Binary file not shown.
@ -1,17 +1,17 @@
|
|||||||
-----BEGIN PGP SIGNATURE-----
|
-----BEGIN PGP SIGNATURE-----
|
||||||
|
|
||||||
iQJNBAABCgA3FiEEm8dazQnvu0U1Gdmc9s+lqZ57WVcFAmCWxPgZHGd6YW11ZGlv
|
iQJNBAABCgA3FiEEm8dazQnvu0U1Gdmc9s+lqZ57WVcFAmCWykoZHGd6YW11ZGlv
|
||||||
QGxpYnJlbWV4Lm9yZy5teAAKCRD2z6WpnntZV7ViD/9KFPDO0FEq6DAPpjIrP48c
|
QGxpYnJlbWV4Lm9yZy5teAAKCRD2z6WpnntZV06ND/4tCq/Dhr9BVaylTFvm706y
|
||||||
HGkK8azkKty0v5jNkaQWVIMF8UpeVneeqlsFEr04whW1fpaVk4Ru6ntTKswumICl
|
hCdeIyD9NuaSPwk3Zc1RC+MoiJ9yfwoK0p44HneWJRHcCBfRKXwdkbw+zEj9/6o7
|
||||||
m+Srt59N/AyhN/BtGxTZJxBgVP/0Tj5B6KL087BJ/zUAoNfSL0GppKif+JaahSKT
|
O0YCaBgR2tasychDEazRXFg31YRVKkKJzNUWFomMyBo9SlJd85H4kpKEk3gYaH8V
|
||||||
1vwda8dyJ5aHGZqZC0N8435TVE4z/9YbbfSPgABIXvqIHdHQiWvnDLGc8nbnsQI5
|
c0h8wmHKrDOyMN0r3Gu1JBhEe2TSMRilssGz6VjNZ1tZDUiQkwXovY9KBx4KZn8G
|
||||||
//SqV6RyJTGCBNHhIERfCqCf/3CW8rUBMxzj3KxIRQ9zBjKBttpn2eDt1id6XfdX
|
2Ht+TG/SlVzcdo9XIwFS5oomhN7qHhQMxeSXEe+Rs4W0lBLcWnDnVSygtDhoRfj7
|
||||||
OSVZzq4i6VPC/EJ+c88nagU7lK5NbIZc30JzJXdIkVJUOTmqzLzXy5iu7ywWAkez
|
auEF7lnuvSWdpYFbi2DnxVvYbGgq7OsxUZUVfsxHvif+y3yQjXXBau/zS+oPqwqX
|
||||||
ROBppnhLwoXQ/aT+AHCpakYfOc8MYq/Yl3f2U6VsxrfccC0MkjnWLbZA6gMH6VgP
|
NLb6lUkNBgylL9CLQ6RnhFEQRf0il/F2TqpXfHH6q+kqavXyd/oFA3DfKylLFwnT
|
||||||
9nGd8nfpw4r4H2fvkP1ESyZAqqcqtka0Fh7Y+HTx1zUL/+z8mLBdMLPZkYxeqR9A
|
owuZOx5RFeMx6qVHgGWWbTtduSwJnPIDZBgcWJCUzl2Cu4yU0dX8wswXVgLz+ns/
|
||||||
uIpMd87Ob3g5mets9nHO0aBdkHaOcYYFUFs6pUGrJCy3sM5/U6+Kaj37KfGWgF15
|
TB7CjWZ+kI2Sz4fxc215oG2HCOucooq25/4e4Y5V0cAekBntOwJ72GxziYLefn5p
|
||||||
2fFim9iN510L4yW4Z1zzoRVmYGW68/PVTHd3KFnI1LF8vnRkY1b9nCZYLgxfoGRo
|
TW6lkHNQSkaRI2wFT+VyVFl8/C2ePNChbn19D7CgD/v2nXrhDhV6/ijK7Cxo2Nu9
|
||||||
tTF2iDCJkYuZLTprR1piyuGHBpG8iLTNqd9uIiUdF4Kf+QKT2dRN9N27CAAr6hR5
|
XClmFMUeuPf9FDFTneGmFMBbPtmMhGkeMSAWfQInzz2gjui2I1zH1PCnOTj5ikzt
|
||||||
HbSBsF2vE1Cv+JkqF30Gyw==
|
CtNdW/6LEByL13jO11VTjA==
|
||||||
=USM6
|
=XNVH
|
||||||
-----END PGP SIGNATURE-----
|
-----END PGP SIGNATURE-----
|
||||||
|
Binary file not shown.
Binary file not shown.
Binary file not shown.
@ -0,0 +1,284 @@
|
|||||||
|
=============================================================================
|
||||||
|
This HOWTO originally appeared on:
|
||||||
|
http://lists.gnu.org/archive/html/qemu-devel/2004-10/msg00067.html
|
||||||
|
=============================================================================
|
||||||
|
|
||||||
|
Using VDE with Qemu HOWTO
|
||||||
|
by Jim Brown
|
||||||
|
5 Oct 2004
|
||||||
|
Version 0.2
|
||||||
|
|
||||||
|
-----------------------------------------------------------------------------
|
||||||
|
|
||||||
|
Introduction
|
||||||
|
Copyright
|
||||||
|
What is qemu?
|
||||||
|
What is VDE?
|
||||||
|
|
||||||
|
Configuring and Installing VDE
|
||||||
|
Installation
|
||||||
|
vdeq & vdeqemu
|
||||||
|
|
||||||
|
User-mode networking
|
||||||
|
How to enable user-mode networking
|
||||||
|
Firewall configuration
|
||||||
|
|
||||||
|
Slirp (rootless) networking
|
||||||
|
What is slirp networking?
|
||||||
|
How to enable slirp networking?
|
||||||
|
|
||||||
|
Setting up qemu
|
||||||
|
How to set up the guest OS
|
||||||
|
|
||||||
|
Credits
|
||||||
|
|
||||||
|
-----------------------------------------------------------------------------
|
||||||
|
|
||||||
|
Introduction
|
||||||
|
|
||||||
|
Copyright
|
||||||
|
|
||||||
|
Copyright (c) 2004 Jim Brown.
|
||||||
|
Permission is granted to copy, distribute and/or modify this document
|
||||||
|
under the terms of the GNU Free Documentation License, Version 1.2
|
||||||
|
or any later version published by the Free Software Foundation;
|
||||||
|
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
|
||||||
|
Texts. A copy of the license is available at http://www.gnu.org/licenses/fdl.txt
|
||||||
|
|
||||||
|
What is qemu?
|
||||||
|
|
||||||
|
Qemu is a FAST! processor emulator by Fabrice Bellard, available at
|
||||||
|
http://fabrice.bellard.free.fr/qemu/. It is capable of emulationg the x86 and
|
||||||
|
PowerPC processors with support for other processors on the way. The original
|
||||||
|
purpose of qemu was to allow running x86-specific Linux applications, such as
|
||||||
|
WINE or DosEmu, on non-x86 systems. However, qemu has expanded into becoming
|
||||||
|
a full-fledged emulator. On the x86 side, it is capable of running Linux,
|
||||||
|
MS-DOS, Windows 95/98/Me, Windows NT/2k, Windows XP, Solaris, OpenBSD, and
|
||||||
|
FreeBSD. See http://fabrice.bellard.free.fr/qemu/ossupport.html for the full
|
||||||
|
listing.
|
||||||
|
|
||||||
|
This howto assumes that you have already installed and set up qemu.
|
||||||
|
|
||||||
|
What is VDE?
|
||||||
|
|
||||||
|
VDE is short for Virtual Distributed Ethernet. VDE, written by
|
||||||
|
Renzo Davoli, is based off of uml_switch by Jeff Dike. It is available at
|
||||||
|
http://sourceforge.net/projects/vde/. It has many uses, the main one providing
|
||||||
|
support for networking with emulated computers. (Not just qemu, but support
|
||||||
|
for user-mode linux and Bochs also exists). VDE must be set up and installed by
|
||||||
|
root, but the programs which use it do not need root privligies.
|
||||||
|
|
||||||
|
This howto will walk you through the simple process of installing
|
||||||
|
VDE and setting up qemu to use it.
|
||||||
|
|
||||||
|
-----------------------------------------------------------------------------
|
||||||
|
|
||||||
|
Configuring and Installing VDE
|
||||||
|
|
||||||
|
Installation
|
||||||
|
|
||||||
|
You may obtain the source code at http://sourceforge.net/projects/vde/.
|
||||||
|
The version of VDE which I used was 1.4.1, but this HOWTO should apply to all
|
||||||
|
versions.
|
||||||
|
|
||||||
|
Once you have downloaded the source code, extract it. I assume you
|
||||||
|
will have extracted it to /space/vde. Go into that directory, and simply type
|
||||||
|
"make" followed by "make install". Now you should have vde_switch in /usr/bin.
|
||||||
|
|
||||||
|
vdeq & vdeqemu
|
||||||
|
|
||||||
|
Now cd into the qemu directory. Type "make". This will build vdeq.
|
||||||
|
Qemu on its own only supports full networking with tuntap, which requires
|
||||||
|
root priviliges or an exposed /dev/net/tun. There is a -user-net option, but
|
||||||
|
that is not as useful as full networking. In order for qemu to use VDE, it must
|
||||||
|
be passed the file descriptor for a tun device. Futhermore the tun device itself
|
||||||
|
must already be configured to use VDE. vdeq sets this up and passes it to qemu
|
||||||
|
via the -tun-fd switch.
|
||||||
|
|
||||||
|
There is no "make install". Instead, you just manually copy vdeq to
|
||||||
|
/usr/bin. It might also be helpful to copy or link vdeq to vdeqemu. vdeq
|
||||||
|
requires that the location of the qemu binary be passes to it as the first
|
||||||
|
command line parameter, but vdeqemu only needs the options you want to pass to
|
||||||
|
qemu. vdeqemu will locate the qemu binary itself (this requires that you install
|
||||||
|
qemu system-wide or have the qemu directory in your PATH).
|
||||||
|
|
||||||
|
For example if you have:
|
||||||
|
vdeq qemu -hda /mnt/myimage -m 64 -boot a
|
||||||
|
|
||||||
|
you can shorten this into
|
||||||
|
|
||||||
|
vdeqemu -hda /mnt/myimage -m 64 -boot a
|
||||||
|
|
||||||
|
-----------------------------------------------------------------------------
|
||||||
|
|
||||||
|
User-mode Networking
|
||||||
|
|
||||||
|
How to enable user-mode networking
|
||||||
|
|
||||||
|
The following commands will need to be run as root:
|
||||||
|
|
||||||
|
# vde_switch -tap tap0 -daemon
|
||||||
|
|
||||||
|
If you need to run a sniffer, just in case you want to analyze the traffic,
|
||||||
|
you can also run it like this:
|
||||||
|
|
||||||
|
# vde_switch -hub -tap tap0 -daemon
|
||||||
|
|
||||||
|
(The -hub option is not available for version 1.4.1 of VDE, you will need a
|
||||||
|
later version. I don't know what the minimal version is but 1.5.1 does support
|
||||||
|
this option.)
|
||||||
|
|
||||||
|
Then you must run this:
|
||||||
|
|
||||||
|
# ifconfig tap0 <ip>
|
||||||
|
# chmod 755 /tmp/vde.ctl
|
||||||
|
|
||||||
|
The vde_switch command will run VDE in the background. The -tap tap0
|
||||||
|
parameter tells VDE to set up the device tap0 using tuntap. -daemon runs
|
||||||
|
vde_switch in the background. -hub tells VDE to broadcast the message to all
|
||||||
|
segment, just like real hub that you use on real network.
|
||||||
|
|
||||||
|
<ip> is the ip address of the gateway you want to use for the guest
|
||||||
|
OS(es). For example:
|
||||||
|
|
||||||
|
# ifconfig tap0 192.168.254.254
|
||||||
|
|
||||||
|
will make 192.168.254.254 the gateway between guest and host, and your
|
||||||
|
guest OS(es) will belong to the subnet 192.168.254.0 with a netmask of 255.255.255.0
|
||||||
|
and an ip address of 192.168.254.XXX (where you get to pick the XXX). You must have
|
||||||
|
the IP of the qemu guest and the IP of the gateway on the same subnet! While it
|
||||||
|
may be possible to have them on separate subnets, it will certainly be harder
|
||||||
|
to configure (and you won't like the way your routing tables will look either).
|
||||||
|
|
||||||
|
[Sidebar: The "gateway" is actually the host OS itself on the tap0 interface.
|
||||||
|
The host on the tap0 interface, aka 192.168.254.254, routes between the guest
|
||||||
|
OS and the host's eth0 interface (which on is the real network). The host on the
|
||||||
|
eth0 interface (ex. 192.168.0.2) can then route between the tap0 interface and
|
||||||
|
the real network / the internet.]
|
||||||
|
|
||||||
|
(Note that you might be required to do this:
|
||||||
|
|
||||||
|
# ifconfig tap0 192.168.254.254 netmask 255.255.255.0
|
||||||
|
|
||||||
|
Normally ifconfig should pick the correct netmask for you, but if it doesn't
|
||||||
|
for some reason then you will have to specify it manually. See ifconfig(8) for
|
||||||
|
details.
|
||||||
|
|
||||||
|
)
|
||||||
|
|
||||||
|
Note that you must run this before you run your firewall. I found it helpful
|
||||||
|
to put this into a script, and have the script load before the firewall does.
|
||||||
|
|
||||||
|
Firewall configuration
|
||||||
|
|
||||||
|
You will need to enable masquerading between tap0 and your local area
|
||||||
|
network (for example, eth0). You will also need to enable masquerading between
|
||||||
|
tap0 and ppp0 if you use a dialup connection to the internet. The commands
|
||||||
|
|
||||||
|
# echo "1" > /proc/sys/net/ipv4/ip_forward
|
||||||
|
# iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
|
||||||
|
# iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE
|
||||||
|
|
||||||
|
will allow you to enable this manually.
|
||||||
|
|
||||||
|
-----------------------------------------------------------------------------
|
||||||
|
|
||||||
|
Slirp networking
|
||||||
|
|
||||||
|
What is slirp networking?
|
||||||
|
|
||||||
|
Slirp was an early program that existed before the masses knew of the internet.
|
||||||
|
Back then, those who knew of it could access it only in one way: through a
|
||||||
|
Unix shell account (or other such terminal account). This meant that one had to
|
||||||
|
do all the things they wanted to in that terminal window. Back then, there were
|
||||||
|
two dial up protocols: PPP and SLIP. PPP is now the standard but back then SLIP
|
||||||
|
was more common (as it was cheaper).
|
||||||
|
|
||||||
|
Slirp was designed to turn those shell accounts into SLIP connections. It worked
|
||||||
|
by converting SLIP packets into socket connections. What you had to do was to
|
||||||
|
run slirp on the computer you had the shell account on, and then connect your
|
||||||
|
SLIP driver/dialer to the terminal slirp was running on (normally this
|
||||||
|
'terminal' was in fact a modem). Slirp would then interpret the data that SLIP
|
||||||
|
sent and transfer the data between the user's computer and the internet. To
|
||||||
|
the user, it looked like they were actually connected directly to the internet
|
||||||
|
through a firewall.
|
||||||
|
|
||||||
|
Slirp is not used today (to the best of my knowledge) but the innovative idea it
|
||||||
|
had is used by both qemu and vde. Instead of converting SLIP packets however,
|
||||||
|
they convert ethernet packets. qemu's slirp networking is similar to vde's
|
||||||
|
but it is simpler to use and also limited to a single qemu instance (you can
|
||||||
|
not link multiple guest OSes together on the same network with slirp networking
|
||||||
|
unless you use VDE).
|
||||||
|
|
||||||
|
How to enable slirp networking?
|
||||||
|
|
||||||
|
This is very similar to TUNTAP networking in the previous section, but the
|
||||||
|
commands are slightly different. In addition, you do not need to set up
|
||||||
|
routing or firewall rules.
|
||||||
|
|
||||||
|
First off, you load vde_switch (no parameters are required for this case,
|
||||||
|
although you can pass the -unix parameter if you want to use a different
|
||||||
|
socket - required if you already have tuntap networking on the default
|
||||||
|
socket).
|
||||||
|
|
||||||
|
vde_switch
|
||||||
|
|
||||||
|
or
|
||||||
|
|
||||||
|
vde_switch -unix /tmp/unx.ctl
|
||||||
|
|
||||||
|
The latter is required if you are running both slirp and tuntap or multiple
|
||||||
|
slirp networks (for that matter, if you are running multiple tuntap networks).
|
||||||
|
More on that later.
|
||||||
|
|
||||||
|
Now you need the slirpvde command. slirpvde is the utilitry that provides the
|
||||||
|
slirp functionality - it intercepts ethernet packets on the network and
|
||||||
|
forwards them through the real network via emulation. To use it, you want
|
||||||
|
to do this:
|
||||||
|
|
||||||
|
slirpvde -s /tmp/unx.ctl -n 192.168.2.0 -d
|
||||||
|
|
||||||
|
The -s tells slirpvde that vde_switch is running on /tmp/unx.ctl [this switch
|
||||||
|
can be omitted if you called vde_switch by itself]. The -d switch tells
|
||||||
|
slirpvde to emulate a DHCP server. This is not required but it allows for
|
||||||
|
automatic configuration of the guest OS (it is basicly the same as qemu's
|
||||||
|
builtin DHCP server). Depending on your needs, you may be better off running
|
||||||
|
a real DHCP server in one of the guest OSes.
|
||||||
|
|
||||||
|
The last option, -n, tells slirpvde
|
||||||
|
what subnet the network should be on (this is also used by the DHCP server to
|
||||||
|
figure out what ip addresses to assign). The gateway ip when using slirpvde
|
||||||
|
is X.X.X.2 (where X.X.X equals the first 3 parts of the subnet you passed to
|
||||||
|
it via -n, in this example 192.168.2) and the default DNS server is X.X.X.3
|
||||||
|
|
||||||
|
You can not change the gateway ip to something other than .2 and the DNS ip
|
||||||
|
to something other than .3 unless you change the source in slirpvde and
|
||||||
|
recompile.
|
||||||
|
|
||||||
|
-----------------------------------------------------------------------------
|
||||||
|
|
||||||
|
Setting up qemu
|
||||||
|
|
||||||
|
How to set up the guest OS
|
||||||
|
|
||||||
|
Set up the guest OS so that the default route is through the gateway
|
||||||
|
ip, <ip> (for example 192.168.254.254). Also set up the subnet and netmask
|
||||||
|
parameters as appropriate (for example 192.168.254.0 and 255.255.255.0).
|
||||||
|
The guest OS should see the ethernet device and be able to use it to access
|
||||||
|
the gateway. (Caveat: I haven't been able to do this for MS-DOS, and for Minix
|
||||||
|
2.0.4 I had to apply a patch to qemu since Minix is broken. Uodate: Minix 2.0.4
|
||||||
|
is still broken but a patch has been released to fix it. Using this patch,
|
||||||
|
Minix works on a vanilla qemu.) Also don't forget to set up the IP of the guest
|
||||||
|
OS itself (for example 192.168.254.1).
|
||||||
|
|
||||||
|
-----------------------------------------------------------------------------
|
||||||
|
|
||||||
|
Credits
|
||||||
|
|
||||||
|
This HOWTO relied heavily on the documentation that Renzo wrote for
|
||||||
|
vde-1.4.1.
|
||||||
|
Thanks to Mulyadi Santosa for helping with the first revision of
|
||||||
|
this document, and to Renzo for his input. (P.S. Will add info for ale4net
|
||||||
|
and slirpvde as soon as I figure out how to use it ;)
|
||||||
|
|
||||||
|
|
@ -1,17 +1,17 @@
|
|||||||
-----BEGIN PGP SIGNATURE-----
|
-----BEGIN PGP SIGNATURE-----
|
||||||
|
|
||||||
iQJNBAABCgA3FiEEm8dazQnvu0U1Gdmc9s+lqZ57WVcFAl7J8z0ZHGd6YW11ZGlv
|
iQJNBAABCgA3FiEEm8dazQnvu0U1Gdmc9s+lqZ57WVcFAmCWykoZHGd6YW11ZGlv
|
||||||
QGxpYnJlbWV4Lm9yZy5teAAKCRD2z6WpnntZVxMeD/96kJvAxNz8WLIbAj2MGPgj
|
QGxpYnJlbWV4Lm9yZy5teAAKCRD2z6WpnntZV/qzD/wKleGt9t9nZiolas5NEcfV
|
||||||
1tgY8QbSVVeHeUEuYB9sV1vw1d/RIO8c6mbVmO8VINbbiyhtOD0KNPCuk7wUuIin
|
pkwSMO6szX/ComGDgifQiWzJszapoZUhNSPMj90CmDMmXOSuc3ctwDF0RMt4w3hZ
|
||||||
lSK5OUtqv4/vhdJnItQNHrTa0pikPvhwMmg16+HWEPVj98tQ5fWS6n/i3M3klZU2
|
+NJodiwOUMyf6XrozP/AqTYIjamF+gXEVCDh0hKYabUtZPWsFwBu6gV/duvwid+F
|
||||||
mMNqMvLSjBRXJJSZKvFrTsVNxGJO++Mdg4vRjiUt3Zw4MGdoLzkt3a8iV0Bqvlgo
|
MZ0nLyEDJo8s+P+q0eR1axM0xSqCLlHoBjLes+5FHzOm2fh+kgwLgB21qOhNY0G6
|
||||||
szTR06wRDn7iqZVT15/92LbU0F+quQyxVCHX/ImlBDJbvzKOifO5/pZqKc+25bEz
|
VZ4pAzUeYqHKwUvHkHygRqAgqjJjA6p5BNc2zl5ABi/bS76lSZJJ+Lt3NihSKhDC
|
||||||
KYPia6lejt2oBKMeNVLUgELhwCOq6gkj7nWFTxV9PhCQ35CsJZUd4/yR8iJeLwSb
|
iO7kkvEnzKy4dvpt9Sj9NtN6JT/NmxA5Kn1KlMt1G2ipl2f0Xbvb1gnUuNSmIeNb
|
||||||
qthPWACJIrMdvRWbs6gl0A8QP7LUY3VOfVcTpRkHmzrNgH0Ya4dSHhGxl96zQ500
|
mklijtWVhMprr6+2PrYd2YwXXzvrqP4G1ZCjvTJ9RA63c9+RckDeIo7dfrOr8IAp
|
||||||
kLSF59v1avjC+XgIUfwuhmzalG+ex2lSsds1bcum37PhQf9HNque+7taRZnf82F6
|
CxngU791hktfX094uwW/iHODO6YMJoBsLDQJlxH1BioJC8KidxRgeuyST96CsfeX
|
||||||
IN7S7Vl5EsYRDxyaLQ5eB+Rw+qRhDbkgYJFrMinzQjeexloODIG6vSCyQuJ+kQxL
|
m+zP/avgN4h6O+C/gLT6jXGL17r4TF/VGjZb3EiLQGGxIzuhdU2JmFnA3lwu+ZPY
|
||||||
0nw1aqIq97/y8aozodj5UI4sbyEOq3sJxspewLU+QjYWbeqVM9mFdzxp4hVaQSCj
|
zOVHrENHCqlrynRckzAm0Ui1k7VOoeuL7RDRcAepJFxHcOvUeluvkU/Sx/8aigIF
|
||||||
hHCchFTTIGCTwm/2wtKR3naMtia13+fG/4LGEpe8Rf4WC3jaj6LuNShHKRip+dW4
|
Z6sXZkXKV5dW7mXbYepKCM1/P+LzDEmK3ecfO8VMrC2PGmEdtMgpt8N39XA3fWhl
|
||||||
Vx+oefh/coLYW6oNMhBAiQ==
|
eRRta1mUpyFG0x9KBEDC0Q==
|
||||||
=2XkN
|
=bYb2
|
||||||
-----END PGP SIGNATURE-----
|
-----END PGP SIGNATURE-----
|
||||||
|
@ -1 +1 @@
|
|||||||
2c98ce79f27034eb98785cfed4e59bdc vde-2.3.2-x86_64-1lem.tgz
|
ce63d20ab5959b6a98d30d37f448bbab vde-2.3.2-x86_64-1lem.tgz
|
||||||
|
Loading…
Reference in new issue