Bridging Segments

Associate
Joined
1 Aug 2003
Posts
1,053
I work for a company that is stuck out in the sticks, BT managed to destroy our connection with the exchange and said we'd be out for over a week.

We were able to jack into our neighbour's network but....

Their segment is 192.168.1.x ours is 192.168.0.x

We can connect to the internet only if we join their segment which means that, firstly we'd intrude and secondly that I'd have to change all our settings and names.

My best idea at the moment is some form of bridging. We have a debian server and if I had one NIC connected to theirs and one to ours I could cunningly do something there - the one problem is I'd have to read a few manuals to know exactly what to do. Can anyone give useful ideas or instructions or at least tell me a rough direction to head in?

Thanks
 
This should be possible using static NAT assignment via iptables... you have traffic coming in eth0 (192.168.0.x) which gets mapped to 192.168.1.x and then forwarded out through eth1.

There's a useful guide on setting up iptables here... http://www.linuxtopia.org/Linux_Firewall_iptables/index.html

However, I'm afraid I'm not able to be of much use, as I've not had to set this up myself... it's just something I've looked into.
 
I came up with a solution eventually;

I changed the subnet masque of all the computers on my segment to 255.255.0.0 and we were able to access both sides quite happily :)

It was a little more complicated than it sounds and probably not the best way to do it but it's up and running and we have an internet connection.

Thanks GarethDW, I'm reading through the things you directed me to so I should be less of a rube next time. If anyone else has similar problems and wants to do it the nerdy way the best thing I could see was using tinc under Linux
 
Back
Top Bottom