Port Prioritisation or not? For ProAsm

slobbargoat, I'm on tower 12 (Mintek) and there's no problem...Got the login prompt as expected.

Definitely not a twoer problem.

-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<

...and Gandalf stared into the distance with a faraway look of gold...
 
Good Day Lenore

There are a number of ports that are blocked on the My
Wireless service some of them are the average ports that
are blocked by any isp and we have got some other ports
that are blocked as they can be used for spamming purposes,
if possible please could you issue us with information as
to which ports you will be looking at using and we can then
provide you with information as to whether or not those
specific ports have been blocked

Regards
Sentech Support

On Sat, 05 Jun 2004 13:14:13 +0200
"miss creant" <pixistyx> wrote:
> hi good day,
>
> just wanting to be finding out, which ports are blocked
> on
> the myWireless service, if any?
>
> thanking you for reply
> lenore

----------------------------------------------------------------------
oh...



-------------------------
What Would C'thulhu Do?
 
For all those concerned with whether or not Sentech is "shaping ports" and you getting slow P2P downloads, why don't you test this for yourselves, most of the P2P apps have an option to choose which port it will be useing, in your app, change the incoming port to port 80.
If speed improves, then
We have a problem
else
Sentech is not port shaping, the problem lies in your peers!

I tried this using KaZaa, and shareaZa, both allow you to change incoming port, tried shareaza with Gnutella, Edonkey, and bitTorrents, no improvements, and the same goes for Kazaa(Fasttrack)
Any other results, I'd be interested to know
 
<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by pixistyx</i>
<br />some of them are the average ports that are blocked by any isp
<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">
WTF is that supposed to mean? The "average ports blocked by any isp?" Crap, most ISPs do not block ports. Some block incoming 25 (SMTP, for spam reasons) and occasionally 80 (Sentech does NOT block port 80). Anyway, these are ports listening for INCOMING CONNECTIONS, which has nothing to do with the problem discussed here which is a user having problems connecting OUT to a *remote* port 2082 (where the local port would be randomly assigned and certainly not blocked). And Sentech is definitely not blocking port 2082 anyway, because at least three other Sentech users can connect to the site in question and to other sites hosted on port 2082.
 
<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by Karnaugh</i>
<br />Please read your own post.

They firewall windows machines they host, they do not place filtering on their side of customer lines. Firewalling is to be done on the client side if they want it.

I repeat, ISP's do *not* firewall ports for you - that IS irresponsible and stupid.

"Getting traffic shaping right is easy and can be summed up in one word: Dont." -- George Barnett
<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">

You're mostly right here K. The Microsoft quote was about protecting hosts on the ISP network (both their own and hosted servers). It was pretty evident from the name of the ISP (CoHo - Co-Hosting). The only IP traffic that ISP backbones block/will not route is anything to do with the "private" IP address spaces. Other than that ISP, do not "filter" or "firewall" traffic in any way.

Where you were in error is on the client firewall point. Many ISP's will host client firewalls on their side of client's lines as a managed service offering. IS has rack-loads of Cisco PIX firewalls that they host on their premises on clients' behalf. They also offer SP-side mail filtering and other value-added services.

I agree with your sentiments that slobbargoat's "shotgun" nmap portscan was irresponsible and most likely casued an IPS/IDS trigger to filter any further traffic from his IP address. AS you can see from your own more limited scan and from simply telnetting to some likely ports on thr i-roar host, there are a number of ports accepting connections.
 
So erm ... like erm ...
Isnt anyone gonna phone them and demand to know which ports are blocked ? :)
 
<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote">
I agree with your sentiments that slobbargoat's "shotgun" nmap portscan was irresponsible and most likely casued an IPS/IDS trigger to filter any further traffic from his IP address. AS you can see from your own more limited scan and from simply telnetting to some likely ports on thr i-roar host, there are a number of ports accepting connections.
<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">

the port scan did NOT trigger an IPS/IDS. Clue number 1 is where karnaugh himself did a scan at got different results, and clue number 2 is where i telnetted to port 2082 on i-roar.com and it wouldnt allow me even then. Even disconnecting and reconnecting (giving me another ip of course) wouldn't allow me to connect.
 
well, what do you know. I go away for the weekend, come home and see an email that sentech did some work on their towers, and now suddenly i can access those ports again.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X