differences of cable and dsl for linux

[brent harding]

I thought that. Isn't it more cable that blocks ports more than dsl? Dsl is
likely the only thing, if anything I may be able to get. How can they block
my inbound connections, isn't that in my control how I configure firewalls
I run on my system? Is using a private ipaddress that I set my computer to
run a dialin connection good enough if I need to dial in to my computer to
get on the net if I'm away using my laptop somewhere else, or does my
laptop become transmit only when I dial it in and log in with ppp? What do
there http proxies do that some of them insist so much that you use them,
do they affect whether or not I may, for instance, get a window-eyes update
or visit linux related websites? I know if I test enabling ratings in ie
5.0, gwmicro's site is locked from use without a password, of course I knew
it because I was testing it out for fun one day. Is it pretty well
necessary if they don't give two ips to use ipmasking on the system with
the modem that is to answer when I call? Getting linux to answer the line
doesn't seem real hard, but what ip to dynamically assign the dialin
machine, most likely my laptop from a remote location that's still a local
call, would be hard. I read the cable howto, just to see what things might
involve, and it seems that different providers do different things, some
give static ip, some can change ip by dhcp as often as 10 minutes. Why do
some need to change your ip so often, are they so incredibly paranoid that
people might be running servers, or is there a real reason for changing
quite often?