Connecting your GNS3 labs to the real network
There is a nice video tutorial to get your GNS3 lab connected to your physical network.
However, it requires you to use a real network card with a fixed IP for doing that. This is not really handy if, llike me, you use GNS3 on a laptop whose connectivity is frequently switching between cable and wireless, and on different subnets.
I started to look for something more convenient like a virtual interface.
I first thought about declaring a virtual IP on eth0, but no way : briding is layer 2 (based on MAC address), you can’t add eth0:0 to a bridge.
Then I found the very handy dummy interface.
Load the module :
% sudo modprobe dummy % lsmod | grep dummy dummy 3192 0 % ifconfig dummy0 dummy0 Link encap:Ethernet HWaddr AE:89:91:BD:61:87 BROADCAST NOARP MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
To have the module loaded at boot time, do :
In debian :
% echo dummy >> /etc/modules
In openSUSE, edit this line in /etc/sysconfig/kernel :
MODULES_LOADED_ON_BOOT="dummy"
Then, you could go on with the tutorial linked above, replacing eth0 with dummy0, or use the script I made :
#!/bin/sh /bin/tunctl -t tap0 /sbin/ifconfig tap0 0.0.0.0 promisc up /sbin/ifconfig dummy0 0.0.0.0 promisc up /sbin/brctl addbr br0 /sbin/brctl addif br0 tap0 /sbin/brctl addif br0 dummy0 /sbin/ifconfig br0 10.10.10.99/24 up /path/to/GNS3-0.6-src/gns3
You may also insert this line if you want to interconnect your lab network with your other networks (it activates kernel’s IP forwarding) :
echo 1 > /proc/sys/net/ipv4/ip_forward
I saved it /usr/local/bin/gns and created a pretty shortcut for the application browser of Gnome :
% cat /usr/share/applications/gns3.desktop [Desktop Entry] X-SuSE-translate=true Encoding=UTF-8 Name=gns3 GenericName=Cisco routers emulator Exec=/usr/local/bin/gns-start Terminal=false Type=Application X-KDE-SubstituteUID=true Icon=gnome-window-manager Categories=GNOME;Network;
This shortcut will prompt you for the root password (unfortunately, when dealing with tap interface, GNS3 requires root access – security could be tighten with SELinux or AppArmor) and launch GNS3 with most of the network stuff prepared.
Just in case you want to clear that all quickly, there is the gns-stop script :
#!/bin/sh ifconfig br0 down brctl delif br0 tap0 brctl delif br0 eth0 brctl delbr br0 tunctl -d tap0
Related posts:
- Practicing Cisco networking with GNS3 and Dynamips
- Use Gnome-terminal with GNS3
- Ethernet duplex issues
- openSUSE 11.1
- FTP configuration issues
JC :: Mar.01.2009 :: Cisco, Linux, Network, openSUSE :: 2 Comments »
Why you need so lame way
) GNS is just a lame Graphical interface
and real thing that work for you and gns is a DYNAMIPS knowing this you can just put -p 0:NM-1FE-TX -s 0:0:gen_eth:eth0 or whatever interface you want
REMEMBER DYNAMIPS that is a real project that we must know and RESPECT
So what ?
GNS3 also deserves respect.
Believe me, having a frontend like GNS3 is nice when you want to test an architecture with more than a router and switch.
If you don’t like it, then pass your way.