Re: Announce: Simple 65c02 simulator for Linux

["Ernest" <leucoplast@seanet.NOSPAM.com>]

"Bill Garber" <willy46pa@comcast.net> wrote in message
SbidncDPOr9VgUCiRVn-gg@comcast.com">news:SbidncDPOr9VgUCiRVn-gg@comcast.com...
>
> "Steve Nickolas" <uNsOoStPsAuMkSi@verizon.net> wrote in message
> news:Pine.LNX.4.44.0312142056540.28855-100000@localhost.localdoma
> in...
> : On Mon, 15 Dec 2003, M. Pender wrote:
> :
> : > Sheldon Simms <sheldonsimms@yahoo.com> wrote in message
> : > pan.2003.12.06.04.31.36.121795@yahoo.com">news:pan.2003.12.06.04.31.36.121795@yahoo.com...
> : > > I have also made a wxWindows .so available on my web page
> if you
> : > > prefer one-stop downloading, but please be nice to my web
> server;
> : > > it's just an old Mac Centris 650 on a cable modem.
> : >
> : > How do you make your Centris 650 accessible on a cable modem?
> I thought
> : > that the IP addresses for cable modems are dynamic?
> : >
> : > - Mike
> :
> : From what I've heard talking to a person who's used two
> different cable
> : ISPs, it depends on the ISP.
>
> Comcast told me they can allow static IP addresses, but
> they prefer not to. If you beg them and get the right
> customer support person, they can be talked into it.

Back when it was TCI, I purchase a static address for an additional $5 per
month. Then, ATT took over and assigned all new IP address'. I called them
about my previous static address and they said that they no longer were
offering static address' (but they didn't seem to mind taking my extra $5
per month until I called them about that too.) Then, Comcast took over and
continued ATT's policy.

The ironic part is that from the time that ATT took over until just a week
ago, I had the same "dynamic" address. In other words, since I never turned
my cable modem off, I kept the same address. I ran my web page for all of
that time on the same dynamic address, as though it was a static address,
and I didn't have to ask permission or pay extra.

OK, that was then but this is now. A week or so ago, my internet connection
stopped working. I followed the problem back to my IP address -or my NAT
settings to be more specific. It seems that Comcast reset my IP address
around 8am PST, which broke my NAT settings. So, I took my router out of the
loop, checked my new IP address, and reconfigured my NATs, and my webpage
was working again. The next morning at 8am PST, my IP address changed again.
Ugh! I followed the previous steps to get my page working again. Next day,
same thing. Shit!

Since then, I haven't restarted my webpage, and guess what? My IP address
hasn't changed. I get the feeling that Comcast is trying to stop people from
running web servers on their home systems. Can they know if I am doing that?
I'm not sure but it looks that way. I'll restart the web server tomorrow and
test my theory.