<html><head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000">Not sure if my original
question made it out to the list but after talking to a few people at
work, I figured out how I can connect to my fileserver from outside
using one ISP or the other....<br>
<br>
Original post below but the quick summary is I currently have two
internet connections at home and I was trying to figure out how to allow
inbound connections using either ISP. I have port forwarding rules on
both routers but I could only connect via the new ISP but connections
using the old ISP were failing to connect probably because my fileserver
is configured to send to a specific gateway regardless of how the
connection came in.<br>
<br>
My original modem/router has internal IP 192.168.1.1 and all devices
are configured to use .1 as gateway.<br>
New modem/router was assigned IP 192.168.1.1 and the old modem/router
was reassigned 192.168.1.2<br>
Given the IP of my remote machine: <a class="moz-txt-link-abbreviated" href="http://www.xxx.yyy.zzz">www.xxx.yyy.zzz</a><br>
<br>
[root@myhome ~] ip route add <a class="moz-txt-link-abbreviated" href="http://www.xxx.yyy.zzz">www.xxx.yyy.zzz</a> via 192.168.1.2 <br>
[root@myhome ~]# ip route<br>
<a class="moz-txt-link-abbreviated" href="http://www.xxx.yyyy.zzz">www.xxx.yyyy.zzz</a> via 192.168.1.2 dev eth0 <br>
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.20
metric 5 <br>
169.254.0.0/16 dev eth0 scope link metric 5 <br>
default via 192.168.1.1 dev eth0 metric 5 <br>
<br>
then from that remote machine:<br>
<br>
ssh -p <my secret port> myalthome.dyndns.org<br>
<br>
or from another computer at work:<br>
<br>
ssh -p <my secret port> mynormalhost.dyndns.org<br>
<br>
I now have two connections that came in using different routes.<br>
<br>
Here are the partial traceroutes showing the routes:<br>
<br>
[root@homeserver ~]# traceroute <my desktop at work><br>
traceroute to <my desktop at work> (xxx.xxx.xxx.xxx), 30 hops max,
60 byte packets<br>
1 * * * <-- lookes like new router doesn't respond to ping<br>
2 xxx-xxx-xxx-xxx.socal.res.rr.com (104.xxx.xxx.1) 41.164 ms 41.199
ms 41.501 ms<br>
3 tge0-9-0-20.mnrvca7101h.socal.rr.com (76.167.29.97) 27.130 ms
27.973 ms 28.093 ms<br>
...<br>
11 dc-lax-agg1--lax-agg6-10ge.cenic.net (137.164.46.104) 31.069 ms
31.004 ms 28.944 ms<br>
12 dc-caltech-1--lax-agg1.cenic.net (137.164.3.58) 41.774 ms 47.018
ms 44.575 ms<br>
...<br>
<br>
[root@homeserver ~]# traceroute <other computer at work><br>
traceroute to <other computer at work> (yyy.yyy.yyy.yyy), 30 hops
max, 60 byte packets<br>
1 dsl-router (192.168.1.2) 6.747 ms 6.662 ms 6.595 ms<br>
2 yy-y-yy-yy.dsl.dynamic.fusionbroadband.com (50.yyy.yyy.1) 18.691
ms 19.689 ms 24.174 ms<br>
...<br>
10 ntt-los-nettos-usc.ln.net (165.254.21.242) 23.453 ms 24.096 ms
24.702 ms<br>
11 cit2-vlan2003.ln.net (130.152.181.60) 52.983 ms 54.779 ms 55.932
ms<br>
...<br>
<br>
traceroute's from the two work computers to my normal and alternate
hosts at dyndns.org show the reverse as expected.<br>
<br>
And when I try to rsync a couple of ISO images using either path, I do
see a significant difference in transfer speeds as expected via DSL vs
cable. About 670 kB/s (~5.3 Mbps) vs 9 MB/s (~72 Mbps). Heck I was
able to push the same test file several times via the cable connection
while the dsl connection was still putting along. Test file was a 693
MB file:<br>
<br>
621611008 100% 9.00MB/s 0:01:05 (xfer#1, to-check=0/1)<br>
621611008 100% 8.73MB/s 0:01:07 (xfer#1, to-check=0/1)<br>
621611008 100% 673.28kB/s 0:15:01 (xfer#1, to-check=0/1)<br>
<br>
This pretty much matches the results of doing speed tests at home using
the web based tests so I'm pretty happy with the switch. After the
port of my home telephone is completed I'll be cancelling my old
service.<br>
<br>
Claude<br>
<br>
<br>
<blockquote style="border: 0px none;"
cite="mid:E2E5938B-9B5E-4A74-81BA-0C0FA9452DB9@gps.caltech.edu"
type="cite">
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="display:table;width:100%;border-top:1px solid
#EDEEF0;padding-top:5px"> <div
style="display:table-cell;vertical-align:middle;padding-right:6px;"><img
photoaddress="claude@gps.caltech.edu" photoname="Claude Felizardo"
src="cid:part1.04030903.00070503@gmail.com"
name="compose-unknown-contact.jpg" height="25px" width="25px"></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
<a moz-do-not-send="true" href="mailto:claude@gps.caltech.edu"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Claude Felizardo<br>
</a></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;">
Tuesday, June 23, 2015 5:46 PM</div></div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody"><meta content="text/html;
charset=UTF-8" http-equiv="Content-Type">Hey all,<div class=""><br
class=""></div><div class="">I am in the middle of transitioning from
DSL Extreme to TimeWarner (TV cable) and have most everything switched
over but I wanted to experiment with a couple of things while I still
have both ISPs working.</div><div class=""><br class=""></div><div
class="">When I first switched from AT&T DSL to DSL Extreme to get
rid of the bandwidth caps I tried various combinations of the supplied
modem (bridge vs non-bridge) to my existing router (LAN or WAN port) but
the only thing that seemed to work reliably was to use bridge to WAN
port. The other combinations resulted in one way connectivity (Laptops
on WiFi could not access file server due to nested non routable IPs) or
some other problem. Non bridge mode was listed as unsupported and I
think I saw something to the effect that it might not be stable and I’ve
had some long term stability problems. The only catch with this
configuration is I don’t have access to the modem web config, stats,
etc. So for the past 2 years or so, my configuration was as follows:</div><div
class=""><br class=""></div><div class="">DSL modem in bridge mode
(50.x.x.x) ==== (WAN) router with WiFi (192.168.1.1) —— various devices
static and DHCP starting at 192.168.1.100. The static devices such as
file servers, NAS, printers, etc. are configured to use 192.168.1.1 as
the gateway out.</div><div class=""><br class=""></div><div class="">The
new cable modem includes a router, 4 LAN ports and WiFi. I wanted to
minimize changes to the various static devices so I did the following:</div><div
class=""><br class=""></div><div class="">DSL modem in bridge mode
(50.x.x.x) ==== (WAN) router with WiFi (192.168.1.2) <— note that I
have changed the old router to be .2 instead of .1. DHCP enabled from
192.168.1.200-249.</div><div class="">cable modem (104.x.x.x) —
(192.168.1.1) <—— cable router is now .1 with DHCP enabled from
192.168.1.150 - .199.</div><div class=""><br class=""></div><div
class=""><br class=""></div><div class="">Note that I have both routers
configured to provide DHCP in different ranges that are different from
my original configuration. This lets me see what IPs devices are
getting and from which router as well as see what’s still hanging onto
old IPs. Again, boxes that offer services such as storage, web, etc,
are using static IPs in the .10 to .99 range.</div><div class=""><br
class=""></div><div class="">Everything seems to be working, no obvious
problems with duplicate IPs (yet). Depending on which WiFi access point
you connect to, I see noticeably different results when I try a speed
test: either 6-8 Mbps for DSL or 50+ Mbps for cable. Still collecting
stats to see how things change during the time of day, etc.</div><div
class=""><br class=""></div><div class="">I even got each modem updating
a different <a moz-do-not-send="true" class="" href="http://dyndns.org">dyndns.org</a> domain
so I can theoretically come in through a different ISP.</div><div
class=""><br class=""></div><div class="">However, when I try to connect
to my linux server from the outside world (both routers are configure
to forward specific ports to specific IP’s inside), I’m not seeing a
response when I try come in through the DSL connection. It just seems
to hang like packets are being dropped. I believe it’s because my
routing table only lists a single gateway:</div><div class=""><br
class=""></div><div class=""><div class="" style="margin: 0px;
font-size: 11px; font-family: Menlo;"><div class="" style="margin: 0px;">[claude@homeserver
network-scripts]$ route -n</div><div class="" style="margin: 0px;">Kernel
IP routing table</div><div class="" style="margin: 0px;">Destination
Gateway Genmask Flags Metric Ref Use Iface</div><div
class="" style="margin: 0px;">192.168.1.0 0.0.0.0
255.255.255.0 U 5 0 0 eth0</div><div class=""
style="margin: 0px;">169.254.0.0 0.0.0.0 255.255.0.0 U
5 0 0 eth0</div><div class="" style="margin: 0px;">0.0.0.0
192.168.1.1 0.0.0.0 UG 5 0 0 eth0</div><div
class="" style="margin: 0px;"><br class=""></div><div class=""
style="margin: 0px;">So I think when my server tries to respond to a
connection request that is coming from 192.168.1.2, it’s sending it out
via 192.168.1.1 so the connection never completes. Is this correct? </div><div
class="" style="margin: 0px;"><br class=""></div><div class=""
style="margin: 0px;">I should have another network card laying around
but it’s probably not worth it if I’m going to discontinue the old
service. I could try booting up the old old file server and see if I
can reconfigure it to use 192.168.1.2 for it’s gateway.</div><div
class="" style="margin: 0px;"><br class=""></div><div class=""
style="margin: 0px;">But I’m thinking I should be able to create another
route via command line but It’s been years since I’ve done this
manually so I’m hesitant to try it remotely and lock my self out. Any
suggestions?</div><div class="" style="margin: 0px;"><br class=""></div><div
class="" style="margin: 0px;">Claude</div><div class="" style="margin:
0px;"><br class=""></div></div></div></div>
</blockquote>
</body></html>