Nifty Hat Mitch writes:
On Fri, Oct 01, 2004 at 09:41:46PM -0400, Sam Varshavchik wrote:....Thom Paine writes:
>I ran into a small problem last month in that I used over 70G of >bandwidth. My current ISP can't really handle that, as it costs him $4 >per G of transfer. > >I really need the static IP that he provides, as well as the discount on >my internet....>I need my current static IP to connect to servers I support, but I would >rather have most of my incoming connections as well as most of my >internet traffic head out the cable one.
Commonly the static IP address is for incoming connections and packets. You can use either of your ports for a reply unless the far host is doing something 'interesting'.
All Internet traffic to your static IP address will go over the connection to your first ISP. End of story.
How is routing configured.
Are both IP services routed nets.
In some cases it is possible to setup routing metrics so your favorite connection is used more than another.
Except that his other connection is a cablemodem ISP.
Only clueless ISPs allow their retail subscribers to fling any packets they like.
Clueful ISP will have their border routers drop all packets that originate from some IP address that does not belong to the ISP.
Attachment:
pgpS2fmD7pptO.pgp
Description: PGP signature
