I am wondering what it takes to have a Red Hat (7.0) machine on two different internet connections at once.
I am in the midst of (possibly) changing over to a different DSL provider, and as it happens they are on different copper pairs, so I can have both at once. Because I host my own e-mail I would like to do a smooth cut-over, and the first (educational) step is to be on both networks at the same time. Both of these are NATing routers behind their own static IP numbers. In one case my server is at internal address 192.168.1.2 and in the other case it is at 192.168.100.2. I have two ethernet cards in the machine, each network connection plugged into its own card. It kinda works, I can plug my notebook into the new network and talk to the server, and everything that was running through the old connection seems to still work. What isn't working is connections from the outside world, coming in through the new router, and talking to my server. I know I have set up the router to send those connections to my server because a tcpdump running on the server shows them coming and the server thinking it is answering. Some more data. On the server: [root@borg root]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.100.1 0.0.0.0 UG 0 0 0 eth0 [root@borg root]# Is that sensible? (If not, what might I do to make it more sensible?) Doing a traceroute in from an external (also Covad) Red Hat box to the new Covad connection: $ /usr/sbin/traceroute 64.105.205.123 traceroute to 64.105.205.123 (64.105.205.123), 30 hops max, 38 byte packets 1 192.168.1.1 (192.168.1.1) 1.387 ms 0.897 ms 0.781 ms 2 h-66-166-225-1.CMBRMAOR.covad.net (66.166.225.1) 12.701 ms 22.114 ms 11.313 ms 3 * * * 4 borg (208.218.135.231) 31.349 ms 29.858 ms 29.501 ms How in Hell did my borg.org IP address get in there!? My server doesn't really know about its external static IP addresses, it thinks all local addresses are 192.168.x.x. Is this a clue? Thanks for any help, -kb, the Kent who will next be hooking up a dumb hub on the new line and doing a tcpdump sniff of what is *really* going over that wire. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
