Home

Handy TCP/IP servers (such as Webserver, remote shell, FTP) and utilities (Multicasting client and servers). And a poweful bridge utility tha support VXLAN bridging, EoUDP (Ethernet over UDP). Most of them are written in Perl script and by using Strawberry Perl for Windows, including the Perl executable, which doesn't require to install, so can be put in the USB flash and directly execute.

UBridge is an user space program that can be run on most kinds of Windows platforms (XP/Vista/Win 7/8/ Win servers). provided that the Windows support the Winpcap tool (for local NIC bridging).

UBridge support the standard VXLAN multicast transport, you can refer the following URL:
Bridge standalone Windows PC using UBridge to the VXLAN in VMware (Part 1)

It also supports the unicast mode (Head End Replication) as discussed under:

VXLAN on standalone Windows machine using head end replication feature of UBridge (Part 1)

Some other enhancements which includes VXLAN payload encryption, access/provider mode VTEPs that let you extend your VXLAN over the Internet behind PAT/NAT device. Pls refer to the following URL for detail:

Extend your VXLAN anywhere over the Internet by the UBridge tool (Part 1)

Project Admins:

• Kepler Lam

[Kepler Lam]

Ubridge program tutorial

To bridge between the Cisco router simulator (dynamips) interface with the H3C router simulator (CEN/LITO), you need to understand the UDP NetIO type for the interface configuration.

Under the dynamips, you can use UDP session to emulate a wire (hereafter I refer it as UDP wire) for connecting a pair of interfaces of two routers (can be serial or ethernet). On the two ends of the emulated wire, you need to select an UDP port number of the host that running the dynamips. Then under the corresponding router interface, configure it as a UDP NetIO type (can either use the command line or GNS GUI, please refer to the related document), you need to configure three parameters:

Local port #: IP address of the remote host running the peer router: Remote port #

Both routers need to use the UDP Netio.

Above method is also available for the CEN, the parameters are configured under the hardcfg.tcl of each router.

Basic UDP Bridge configuration

Although both the dynamips and CEN support the UDP wire, you will find that you cannot directly connect them using the UDP wire. Since the underlying implementation is different, thus I create this program to "convert" the signal difference between them.

In order to bridge the Cisco and H3C interface, create 2 different UDP wires, one wire between the Cisco Router to the UDP Bridge, the other between the H3C Router to the UDP Bridge.

So you require 4 different UDP port numbers, e.g. Cisco serail interface use 2012, UDP bridge to Cisco use 5212, H3C interface use 3012, UDP bridge to H3C use 5312.

Cisco configuration: udp:"2011:10.1.1.2:5211"
H3C configuration: -local 127.0.0.1 -lport 3012 -dest 10.1.1.2 -dport 5312

While for the UDP Bridge, you need to create 2 legs:

Cisco leg: C:S@5212:10.1.1.1:2012
H3C Leg: H:S@5312:10.1.1.3:3012

Here the 'C' stand for Cisco signal, 'H' for H3C signal. The 'S' stands for serial, you can use 'E' for bridging Ethernet interfaces.
Since the UDP bridge supports multiple interface pair (group), you need to put the 2 legs into a group, you can choose any group number. E.g. group 3, then the complete syntax for the above legs is 3#C:S@5212:10.1.1.1:2012 and 3#H:S@5312:10.1.1.3:3012.

Now you can start the UDP bridge with these 2 parameters as follows:

c:\iptools>ubdg 3#C:S@5212:10.1.1.1:2012 3#H:S@5312:10.1.1.3:3012

Useful hint: make sure the encapsulation of Cisco (which default uses HDLC) and H3C (which default uses PPP) match each other

Additional UDP Bridge configuration

As mentioned above, you can create more than one interface groups, for serial interface, its obvious that only 2 legs can be put into one group. However, for Ethernet interfaces, it can have more than 2 members in one group.

You can either specifiy the UDP legs as the command line parameters, or you can create a configuration file with each line one leg in the configuration file. E.g. If you want to bridge 2 serial interfaces in one group and 4 other Ethernet interfaces in another group, then create a configuration file ubdg.cfg with the following lines:

1#C:S@5212:127.0.0.1:2012
1#H:S@5312:127.0.0.1:3012
2#C:E@5413:127.0.0.1:2213
2#H:E@5513:127.0.0.1:3213
2#C:E@5423:127.0.0.1:2223
2#H:E@5523:127.0.0.1:3223

Execute the ubdg program as:

c:\iptools>ubdg -c ubdg.cfg

In fact, you can mix the usage of configuration file and command line parameters together, e.g.:

c:\iptools>ubdg -c ubdg.cfg 3#C:S@5211:127.0.0.1:2011 3#C:S@5221:127.0.0.1:2021

Bridge to the physical interface

Since the CEN can only use Winpcap 3.0, its not compatible to Winpcap 4.0 (though Lito improve to be able to run without Winpcap 3.0, yet it cannot bridge to physical interface without winpcap 3.0). But dynamips use Winpcap 4.0. In order to let the H3C Ethernet interface to bridge with the physical interface, starting on version 0.3.0 you can use the UDP bridge program to bridge with the local NIC interface.

you just need to create a group with 2 legs, one leg to the PC’s local NIC, while the other leg is to the H3C’s Ethernet interface. Then put them in a group (example 5 this time). Just like the following diagram:

E.g.

To connect the UBridge with LITO, you need to select 2 different UDP port number, one for UBridge (e.g.5513), one for the LITO (e.g.3213).
For the LITO configuration, open the corresponding router hardware configuration file hardcfg.tcl under the router’s subfolder. Find an unused Ethernet interface, configure the following line:
AddEthNew -speed 1000 Level3 -canswitch -slot 0 -subslot 0 -local 127.0.0.1 -lport 3213 -dest 127.0.0.1 -dport 5513
For the UBridge H3C leg, the parameter is:
5#H:E@5513:127.0.0.1:3213
For the PC’s local NIC, same as the case of “Ethernet over UDP tunnel” discuss below, you can create the leg without the Winpcap nameL
5#W:E
So execute UBridge as:
C:> ubdg 5#W:E 5#H:E@5513:127.0.0.1:3213

---

Enjoy testing
Document created: Oct 29,2013.
Author: Kepler Lam
Certified Cisco System Instructor
Certified H3C Instructor
Certified Juniper Instructor
Certified EC-council Instructor

[Kepler Lam]

Just publish the new release of 0.3.0, the UBridge tools has been integrated with the Winpcap to greatly strength its function.
Now you can use it to bridge the physical interface of your Windows PC to a UDP session. What does it means?

One of the application is to use it as a light weight VPN tunnel to bridge the loopback interfaces of 2 Windows PCs, so as to put them into same subnet (layer 2 adjacency), without changing your network configuration. Another application is to bridge the VMs inside your Windows PC to the VMs of another PC.

Let me use the following diagram to illustrate the configuration:

First make sure that the two PC can reach each other by the physical interface connected to the IP network. Then configure another seperate interface to have another IP address (on same subnet of the 2 PCs). You can use another physical interface (you can't use the interface that form the tunnel for this version, coming version will not have this restriction), or other logical interface, like MS loopback interface (if you don't know how to create it, just google around to find the way) or VMnet interface (but be careful when using VMnet interface, if you using the same VMnet # on both PC, the mac address will be the same, you should avoid such configuration. Say e.g. if one PC can use VMnet1, the other can use VMnet2).

The concept is to create two legs in one single group (e.g. use group 3) with one legs connected to the PC's interface that being bridged (require Winpcap), while the other leg using UDP to connect to another UDP leg. You need to choose the UDP port # for each PC. For the above PC1 use port # 5001 while PC2 use 5002.
To create the UDP need, you can use Cisco Ethernet type, the syntax for PC1 is:
3#C:E@5001:192.168.2.1:5002
While PC2, you can use same group number or other group number (say 2), then the syntax is:
2#C:E@5002:192.168.1.1:5001

While for the interface that to be bridged (the loopback interface in the example), you need to figure out the Winpcap ID of it, if you already install GNS3, you can use the network device list utility. If not, just omit the corresponding parameter, UBrdige will prompt you to choose. This leg type is Winpcap (W), Ethernet type (E), E.g. if the name of the loopback interface is \Device\NPF_{5F97CBE5-7D16-48FB-BC77-0E0DE084F049}, then the connection leg will have the syntax:
3#W:E@\Device\NPF_{5F97CBE5-7D16-48FB-BC77-0E0DE084F049}
or just use
3#W:E

Now invoke the UBridge with the above 2 parameters:

ubdg 3#C:E@5001:192.168.2.1:5002 3#W:E@\Device\NPF_{5F97CBE5-7D16-48FB-BC77-0E0DE084F049}

Similarly, for PC2, you may like to omit the interface ID and execute UBridge as:
ubdg 2#C:E@5002:192.168.1.1:5001 2#W:E

Now you should able to ping between the loopback interface of the 2 PCs

Similarly, if you are using VMware workstation, another usage is to bridge the VMs inside your Windows PC to the VMs of another PC, like the diagram below:

The configuration is the same as the EoUDP tunnel, except that the local PC’s NIC is the VMnet interface.