Well, I'm not going to elaborate on my needs for multiple IP's (static
preferably) for fear of starting another holy-war from the IP-zealots that
feel its their job to make sure the IP4 adderss space is not used up.
I have certain needs that proxy/nat/masq whatever cant meet and
therefore i prefer multiple static ip's for the same reason any company
out there needs a subnet. I've designed and administered enterprise
level networks for years and also write network software from firewalls
to RMON2 probes on linux so Im aware when places like time-warner
are doing a shoddy job or just feeding me BS (or both in this case).

As for the internal network thing. I already have 2 nics (at least) in every
box and have a local 10-net for my private traffic. That way when time-
warner's crap equipment doesnt do its job I dont lose network access
internally at least. I'd rather not waste my time administering my own
network like its a job which is what having an internal network, masq'ing
ip's, using DHCP address that constantly change, etc. makes me do.
I'd much rather have a static subnet, statically IP my boxes once and
be done with it. That way I can spend more time designing useful
software and writing code for the people of this world instead of
spending my time building and maintaining a "titanium network-fort".

Cheers

At 07:50 AM 1/25/01 -0600, you wrote:
>Question, why did you "buy" five IP's.  I would love to know what you plan
>to do with them. I have one IP and route my other two computers through
>Linux to the internet.  As for tech(no)support, I would not be surprise if
>you were right about them passing the phone around.  The sad thing is that I
>know as much about networking as there level one and two people do and the
>only training I had was a semester of networking at St. Paul Tech and the
>course was not that great either.  
>
>Other information:
>I have two NICs registered with ATT Broadband (mediaone).  They allow you to
>have up to three registered, you can only use them one at a time.  
>
>Try putting a second NIC in your Linux machine and try connecting, say your
>laptop, through it out to the internet.  I have hard coded the IP address
>for the intranet because that is the only way I know how to do it right now.
>I am using 192.168.0.1 through 192.168.0.3.  I don't need to access the
>other two machines from outside my home so this setup works well.  
>
>As per the warning I received yesterday.  Here is my message in plain text,
>thanks to all for not flaming me.
>
>
>John Miller 
>Dain Rauscher Inc. 
>Application Services 
>IS Capital Markets 
>Phone 612-547-7573 
>Fax 612-547-7580