Re: [?] DYNDNS host vulnerability
- From: ibuprofin@xxxxxxxxxxxxxxxxxxxxxx (Moe Trin)
- Date: Sat, 23 Feb 2008 18:47:03 -0600
On Sat, 23 Feb 2008, in the Usenet newsgroup comp.os.linux.networking, in
article <ujd0s31inkqucs1eh56gdgre41v74pkpos@xxxxxxx>, Doug Mitton wrote:
Wolfgang Draxinger <wdraxinger@xxxxxxxxxxxxxxxx> wrote:
Doug Mitton wrote:
Also, the alternate server ports resolves issues with ISP's who block
certain ports getting into their address space.
Then get a better ISP. You got your own IP, when connected to the
Internet, all ports on that IP will only affect you. As long
your ISP doesn't share the IP with you (what it hopefully won't
do) there's simply no reason to block traffic on certain ports.
What planet/galaxy do you live on? It is very common for providers
to restrict access to/from ports and/or services based on the amount
of coin you are paying them. As for "no reason to block traffic on
certain ports" - how about the ISPs desire to stay off the various
block lists - or is spam and other net-abuse unknown in your world?
Technically you got a crippled Internet access, then.
Maybe that's what you are paying for.
Look up the contract with the ISP, if there's anything in it,
about letting ports x-y only through if "the moon is full and
venus in the house of scropio" or similair.
there's something about months with the letter 'r' in the name...
And if I'm not totally wrong, it's illegal in democratic countries
to filter by the content (which in the case means also protocol),
even if nowadays many politicians tell you otherwise. Such filtering
would definitely be censorship.
There are 246 countries listed in ISO-3166, some of which even have
the string "Democratic" in the English version of their name, but
rules, laws, and customs in one country do not always apply to all
or even any other country. In some countries, not only is some
filtering _allowed_ by law, but the right to filter is also protected
by law.
If you do a search on my name for the last year or so you'll see I've
been posting to see if others on my ISP (one of Canada's largest) are
having the same issues ... and they are.
Obviously a lot depends on the type of contract/agreement you have with
your ISP. You may find it more useful to find a replacement, especially
if you are having problems with them.
I have a lot of problems with my ISP ... all mainly just infrastructure
connection issues. But, they also change agreements right in the
middle ... contract or not.
Not enough details, but I'm in the US, and the usual solution here is
to unleash the legal types. Not that it is the ultimate solution
mind you, but changing agreements that are part of contract without
following all of the hoops is a no-no
And to complain ... the first issue is communication ... and not the
obvious one you'd expect for Canada ... Central Asia seems to be the
tech support supplier of choice.
True - one of my ISPs (a Southwestern regional) has their support on
the other side of the globe - probably reduces the incidence of user
trying to shove a 4x4 up the fundamental of the "support" klown, but
I also have other ISPs, and two of them get support from Pittsburgh
for some bizarre reason.
Any way ... if the world were a perfect place ... what would we have
to gripe and have opinions about! :-)
I'm sure we'd find something. Your d4mn hockey team... ;-)
Old guy
.
- Follow-Ups:
- Re: [?] DYNDNS host vulnerability
- From: Wolfgang Draxinger
- Re: [?] DYNDNS host vulnerability
- References:
- [?] DYNDNS host vulnerability
- From: Fr@nk Stef@ni
- Re: [?] DYNDNS host vulnerability
- From: Andy Ruddock
- Re: [?] DYNDNS host vulnerability
- From: Fr@nk Stef@ni
- Re: [?] DYNDNS host vulnerability
- From: Doug Mitton
- Re: [?] DYNDNS host vulnerability
- From: Wolfgang Draxinger
- Re: [?] DYNDNS host vulnerability
- From: Doug Mitton
- Re: [?] DYNDNS host vulnerability
- From: Wolfgang Draxinger
- Re: [?] DYNDNS host vulnerability
- From: Doug Mitton
- [?] DYNDNS host vulnerability
- Prev by Date: Re: Token Ring and Linux (See message for details.)
- Next by Date: frame value too large by ifconfig!!!!
- Previous by thread: Re: [?] DYNDNS host vulnerability
- Next by thread: Re: [?] DYNDNS host vulnerability
- Index(es):
Relevant Pages
|