Changeset 170


Ignore:
Timestamp:
06/28/12 23:25:47 (12 years ago)
Author:
atzm
Message:
  • version bump
Location:
etherws/trunk
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • etherws/trunk/README.rst

    r162 r170  
    77========== 
    88For example, if you want to make virtual ethernet link for *VM1* and *VM2* 
    9 whose hypervisor's broadcast domains were split by router *R*:: 
     9whose hypervisor's broadcast domains were isolated by router *R*:: 
    1010 
    1111  +------------------+            +------------------+ 
     
    3232on *Hypervisor1*:: 
    3333 
    34   # etherws server 
     34  # etherws --device ethws0 server 
    3535  # brctl addbr br0 
    3636  # brctl addif br0 vnet0 
     
    4040on *Hypervisor2*:: 
    4141 
    42   # etherws client --uri ws://<Hypervisor1's IP address>/ 
     42  # etherws --device ethws0 client --uri ws://<Hypervisor1's IP address>/ 
    4343  # brctl addbr br0 
    4444  # brctl addif br0 vnet0 
     
    6161============= 
    6262etherws supports SSL/TLS connection. 
    63 If you want to encrypt the tunnel, then you can use following options. 
     63If you want to encrypt tunnels, then you can use following options. 
    6464 
    6565on *Hypervisor1*:: 
    6666 
    67   # etherws server --keyfile ssl.key --certfile ssl.crt 
     67  # etherws --device ethws0 server --keyfile ssl.key --certfile ssl.crt 
    6868 
    6969*ssl.key* is a server private key, and *ssl.crt* is a server certificate. 
     
    7575on *Hypervisor2*:: 
    7676 
    77   # etherws client --uri wss://<Hypervisor1's IP address>/ --cacerts ssl.crt 
     77  # etherws --device ethws0 client --uri wss://<Hypervisor1's IP address>/ --cacerts ssl.crt 
    7878 
    7979Here, URI scheme was just changed to *wss*, and CA certificate to verify 
     
    8484self-signed certificate and client uses another CA certificate. 
    8585 
    86 If you want to just encrypt the tunnel and do not need to verify 
     86If you want to just encrypt tunnels and do not need to verify 
    8787certificate, then you can use following option:: 
    8888 
    89   # etherws client --uri wss://<Hypervisor1's IP address>/ --insecure 
     89  # etherws --device ethws0 client --uri wss://<Hypervisor1's IP address>/ --insecure 
    9090 
    9191Note: see `<http://docs.python.org/library/ssl.html>`_ 
     
    108108To run server with this:: 
    109109 
    110   # etherws server --htpasswd filename 
     110  # etherws --device ethws0 server --htpasswd filename 
    111111 
    112112You also can test by following command:: 
     
    120120option or stdin:: 
    121121 
    122   # etherws client --uri ws://<address>/ --user username --passwd password 
    123   # etherws client --uri ws://<address>/ --user username 
     122  # etherws --device ethws0 client --uri ws://<address>/ --user username --passwd password 
     123  # etherws --device ethws0 client --uri ws://<address>/ --user username 
    124124  Password:  
    125125 
     
    129129support, because it is insecure in itself. 
    130130 
     131Complex Examples 
     132================ 
     133etherws has simple virtual Ethernet switch in itself and it can handle multiple 
     134TAP interfaces or WebSocket connections as virtual switch port:: 
     135 
     136  (A)# etherws --device ethws0 --device ethws1 --device ethws2 server 
     137  (B)# etherws --device ethws0 server 
     138  (C)# etherws --device ethws0 --device ethws1 client --uri ws://x.x.x.x/ 
     139  (D)# etherws --device ethws0 client --uri ws://x.x.x.x/ --uri ws://y.y.y.y/ 
     140 
     141This will create following network:: 
     142 
     143       (ethws0)  (ethws1)  (ethws2)             (ethws0) 
     144           |        |         |                    | 
     145     +-----+--------+---------+-----+     +--------+--------+ 
     146     |           server (A)         |     |   server (B)    | 
     147     |        (ws://x.x.x.x/)       |     | (ws://y.y.y.y/) | 
     148     +-----+------------------+-----+     +-----+-----------+ 
     149           |                  |                 | 
     150           |    (WebSocket)   |    +------------+ 
     151           |                  |    | 
     152   +-------+------+   +-------+----+--+ 
     153   |  client (C)  |   |   client (D)  | 
     154   +--+--------+--+   +-------+-------+ 
     155      |        |              | 
     156  (ethws0)  (ethws1)      (ethws0) 
     157 
     158Also you can use TAP interface which is created by etherws as 802.1Q VLAN 
     159interface using vconfig command and so on. 
     160 
    131161History 
    132162======= 
     1630.7 (2012-06-29 JST) 
     164  - switching support 
     165  - multiple ports support 
     166 
    1331670.6 (2012-06-16 JST) 
    134168  - improve performance 
  • etherws/trunk/setup.py

    r162 r170  
    3737setup( 
    3838    name='etherws', 
    39     version='0.6', 
     39    version='0.7', 
    4040    description='Ethernet over WebSocket tunneling server/client', 
    4141    long_description=longdesc, 
Note: See TracChangeset for help on using the changeset viewer.