Bridging Linux and Windows

Having a Linux desktop on a Windows company carry many hassles, standardization on proprietary — Microsoft software will affect you in ways you can’t possibly imagine. The whole M$ crap was too much to work around through web interfaces so I have eventually to go to virtualization. The virtualization should have take care of everything, if you can’t run a crappy OS like windows at least use it like an app through emulation right? Well not so yet.So we had this thing called Microsoft Communicator, which is like a offspring of MSN Live Messenger. The MSC is utter crap, basically it’s annoying and on top of that is very picky on the communications bits. The interconnectivity with the servers is very weak and dumb and it requires a real IP so the exchange can go back and forth.Having this combined with the pressure from management I decided to take drastic steps and nuke the hard drive. Before nuking it I did a backup which wasn’t very attended since the backup was done to a Fat32 drive which tops at 4GB. This made my backup useless in the end.In the end after a bunch of data lost and stuff I got to get MSC going on a native windows install. I also found out that the server had my wrong email ID which made my torture last even longer. After a week and half of failures and a nuke hard drive, communicator worked. However the challenge was to get back to linux and that’s where the process started.After having a virtual OS set up with outlook, BMC, and Secure client working perfectly, I have to come to the conclusion that all these applications are smart enough to survive NAT networking however MSC will require some credential exchange which lead me to believe that having a real IP would be the best choice to. However on the VirtualBox page there was little documentation on bridging. There was the user manual but even that document wasn’t very thorough and sequential.Reading on the VirtualBox forum I found a VirtualBox guide for Ubuntu which help me out to have the connectivity setup and in the end MSC got connected.The process was not hard but it was long, first problem that I had in the past was finding the right package for the right tools. The tutorial talk about a brctl and tunctl, however these were on two different packages: bridge-tools and tunctl.The other problem that I have was handling all the instructions in the correct fashion. First I have something like scattered commands between one and the other. The next thing is the code for:brctl addbr br0ifconfig eth0 0.0.0.0 promiscbrctl addif br0 eth0dhclient br0tunctl -t tap1 -u my_userbrctl addif br0 tap1ifconfig tap1 up

Advertisements