Results 1 to 2 of 2
Enjoy an ad free experience by logging in. Not a member yet? Register.
- Join Date
- Jun 2010
Two Nics setup with no bridging but still seem to bridge??
- Join Date
- Jun 2010
Ongoing problems with dual nics and duplicate ip address
Well I have the initial system up and running with a normal ip address on the interface that connects to the local network and a duplicate address, of the main server, on the interface that only connects to the portserver. I can now log into the main server with the portserver connected to either through the second interface or hooking it directly to the local network meaning to the portserver the change in interfaces doesn't matter anymore. I'm using an iptable entry to drop all inputs to the normal interface that try to go to the main server with an entry like this:
iptables -I INPUT -i eth0 -d 22.214.171.124 -j DROP
126.96.36.199 is the main server address and eth0 is the interface connected to the local network. This seems to stop any attempts from the local network to access the second interface, eth1, with the duplicate ip address of 188.8.131.52 through the first interface so I don't have problems with confusing anything on the localnet trying to log into the main server.
I also had to add a route using:
route add 184.108.40.206 gw 220.127.116.11
To link the second interface up to the portserver, 18.104.22.168.
All I have to do then is ssh into the main server and port forward the telnet port of the backup server to it. Well not quite, when I try to ssh into the main server from the backup server it is still confused and tries to go to the eth1 card and fails, this wont be a problem when I have the backup server at the remote store since it will be logging into our web address instead of the local 22.214.171.124. I just pointed a temp ssh to another machine on the local net like this:
ssh -L 126.96.36.199:23:188.8.131.52:23 184.108.40.206
So all seems to be well and good.....except...... We seem to be having speed issues with PCs running term emulators and I'm wondering if something is still leeking through the iptable or whatever that is confusing the local net between the main server and the backup server.