Re: IP routing with remote DNS, but server & client on same subnet - how?
- From: Stefan Monnier <monnier@xxxxxxxxxxxxxxxx>
- Date: Tue, 16 Oct 2007 16:34:57 -0400
Thanks! I like this theory (well, maybe to you it is a fact!) -- so
tonight I will try pulling the ethernet cable out of the cable modem
while a file transfer from my website is underway. If all stays on my
local network and no traffic out through the ISP, then the file
transfer (staying within the Linksys router) should be uninterrupted.
It may work. It may also fail because disconnecting the modem may force PPP
to take down the connection and interface and hence remove the external IP
and potentially remove the corresponding iptables rules as well, depending
on how the scripts work. It'll probably work, tho.
Another way to look at it is to run a tcpdump on the WAN side and look at
the packets that go through.
Stefan
.
- Follow-Ups:
- Re: IP routing with remote DNS, but server & client on same subnet - how?
- From: Randy Brick MacKenna
- Re: IP routing with remote DNS, but server & client on same subnet - how?
- References:
- IP routing with remote DNS, but server & client on same subnet - how?
- From: Randy Brick MacKenna
- Re: IP routing with remote DNS, but server & client on same subnet - how?
- From: Stefan Monnier
- Re: IP routing with remote DNS, but server & client on same subnet - how?
- From: Randy Brick MacKenna
- IP routing with remote DNS, but server & client on same subnet - how?
- Prev by Date: Re: IP routing with remote DNS, but server & client on same subnet - how?
- Next by Date: Linux NFS client to Solaris 8 NFS Server
- Previous by thread: Re: IP routing with remote DNS, but server & client on same subnet - how?
- Next by thread: Re: IP routing with remote DNS, but server & client on same subnet - how?
- Index(es):
Relevant Pages
|