vTalk2: [SIFY] Its not PORT BLOCK its VLAN setup BY SSV - vTalk2

Jump to content

  • (2 Pages)
  • +
  • 1
  • 2
  • You cannot start a new topic
  • You cannot reply to this topic

[SIFY] Its not PORT BLOCK its VLAN setup BY SSV Virtual LAN ... Rate Topic: -----

#1 User is offline   Siddharth Menon Icon

  • Administrator
  • Icon
Group:
Root Admin
Posts:
786
Joined:
07-October 05

Post icon  Posted 30 October 2005 - 11:02 PM

I am Updating my 1st post with new INFO I found!! The previous one has been deleted.


Well v had gone & met RAJAN from SSV with regards to all this. He said they have setup V-LAN ie VIRTUAL-LAN. At first I was clueless but after some research on google this is what I have to say.

So even tho we are all physically connected we are seperated by V-LAN configed SWITCH. They r doing all this to reduce the TRAFFIC. Say for eg when you take some file from users in SANPADA & 10 more users do the same, all the SANPADA users will face heavy traffic due to which slow LAN & Internet. SSV take this as a solution for slow Internet. Well I know I cannot blame them completly since even I am one of them who complains for SLOW net.

The solution here is very hard to tell, the v own beloved DC++ has lead tho all this. Now we cannot even play or chat on lan. Either SSV need to upgrade there current network to support 10/100/1000MB LAN or we stop using DC++ & only use LAN to chat & play games.
0

#2 User is offline   Muda4Kar Icon

  • Ek dam Fresh
Group:
Members
Posts:
2
Joined:
13-October 05

Post icon  Posted 07 November 2005 - 02:06 PM

What is said is correct but there is some misconception about that NAT thing. First of all NAT stands for Network Address Translation and and what NAT does is it map's one socket to another by keeping the port address same but with different ip address. So if the Socket was 10.12.42.68:4226 will be maped after NAT as something like 202.44.0.20:4226 ( any public/private ip mapping that has been configured on router).
Now the real misconception which we have is that we are beliving that sify has implemented NAT for address translation but which is not the case : actually Sify has implemented PAT (Port Address Translation) ..it is similar to NAT but here the port of the source socket is mapped to a different port of the destination socket.i.e like in our previous example source socket was 10.12.42.68:4226 ,with ip as 10.12.42.68 and port as 4226 ,which would be mapped to a destination socket like 202.11.0.20:5870 (any public/private ip with any random port) So here the port change to 5870 with same/different public ip address.
Now if you have followed what has been returned in above paragraph then you will get what exact problem is ?; which is keeping all of us from being connected to each other.
Now according to TCp/Ip ruls- To setup a connection between two machines you need to have a 3 way hand shake signals
1)-> SYN
2)<- SYN ACK
3)-> ACK
, for successful connection to be setup.
Now what happens on our network is the packet(-> SYN 1st connection setup signal ) from source machine (with socket address 10.12.42.68:4226 and lets name the machine as A ) reaches the router . router which has PAT enabled modifies the header of the source packet to socket 202.11.0.20:5870 and sends it to the destination machine let say with ip address as 202.11.0.16 (let's refer this machine as B ). Now the destination machine i.e B sends an acknowledge packet (<- SYN ACK) to the source machine ,i.e A, by creating a socket with address and port as 202.11.0.20:5870(as this is wat m/c B thinks the packet has arrived from). The packet 202.11.0.20:5870 reaches the same router (if different then it's a total differnt case,which is beyond the scope,to understand that read Todd Lamme , CCNA) but now the router cannot convert the socket 202.11.0.20:5870 to the original machine A ip address and port 10.12.42.68:4226 . So the packet is lost or dropped and what we receive "requested time out" if we ping the same ip only. And the third step (i.e ->ACK is not at all initiated) So the connection is never setuped. And hence we start to blame sify and abuse sify.
Now what we need to say to sify, in order to get connected is, to forward the port or map the port to the same ip address with the same port number. So that the socket remains the same. and hence the third signal that is -> ACK is sent from machine A to B and once that is done, a successful connection is said to have setuped between the two machines and after that you can do whatever between those to machines. And now the router act's as a mirror to both the machines.
I think i have given a comprehensive explanation for the solution to the problem. but if you still don't understand then post a reply to this message of contact me on borg WITH NICK AS --==[Dude]==-- or --==[PeAcE]==-- but i think this will suffice your needs:)...
0

#3 User is offline   Siddharth Menon Icon

  • Administrator
  • Icon
Group:
Root Admin
Posts:
786
Joined:
07-October 05

Posted 07 November 2005 - 02:59 PM

Hmm if i hav got it right tell me in local IP when i scan I can access HTTP service on port 80, Also this was same when i scan using internet IP before say 202.123.124.124:80. If cause of PAT the ports are diffrently address/translated then I should be able to access my 80 port service on INTERNET IP with some other PORT ?? I mean like 202.123.124.124
:845 .
If yes I tried scaning it but still coun't get anything.

BTW i belive PAT is used when a single IP is use by multiple PCs. But sify assigns Individual Internet IP so Y it adopts PAT ??


Well 3day back my friend had called SIFY & some one fro Vile Parle had called back. He was too suprised with the probs, he also download Bitcomet & eMule to really test the connectity it happens so even he is not able to connect. Well he say may be its from back end & will look into it. To my suprise most of them don't even knw I guess, wats da probs.
0

#4 User is offline   Siddharth Menon Icon

  • Administrator
  • Icon
Group:
Root Admin
Posts:
786
Joined:
07-October 05

Posted 10 November 2005 - 01:54 AM

Sorry for Double post guys but a good newZ ... Sify engineer also called me regarding ports blocks. I spoke to him & asked him to open port 6884 on both UDP & TCP. When it so happen is there are so many firewalls in each level he says its difficult to make out which on to work on, finally he fig it out & then managed to OPEN PORT 6884 UDP. Its good newZ for us that they now knw how to fix things. Also got port 80 opened for TCP & UDP. Yes they where not open as listen ports where blocked.

With help from Sujit & Dini
Ports from 6881-6889 TCP Opened
And if your using bittoren & u get banned using above ports use this open port 65535

Complain more to open more ports like 7000 to 8000 Also 27000-28000 (Counter Strike) etc etc ...

COMMON PORTS
Internet Users
Lan Users
0

#5 User is offline   Devdas Icon

  • Ek dam Fresh
Group:
Members
Posts:
1
Joined:
26-November 05
Location:sanpada sec-3

Posted 29 November 2005 - 01:53 PM

I can't connect to DC++! what is this shit going around??
Can anybody give me satisfactory answer for this. This is just getting on my nerves huh.gif huh.gif
0

#6 User is offline   Dinesh W. Icon

  • Ek dam Fresh
Group:
Members
Posts:
2
Joined:
18-October 05

Posted 24 January 2006 - 06:56 PM

why to stop dc......first all of us must ask sify man.....for reciptes...when we renew our account.......
the sify or ssv....i dont know who is responsible for bloking portes or thta Virtual lan...let them know about the price of tax%

we ppl never ask them for reciptes..they just come to our house for the renuewal charge....bcoz of this things...sify get all that mony in their poket n nothing is charged as tax...which is decided by TRY or whoelse @ 10.3% behind the pakage of Brodband.
this thing of sify is just like the local cable operatores......so just dont pay the renuwal charge without reciptec...n chek whether they r giving proper reciptes.which must include the reg no. and recip no.
Just do this thing for 2-4 weeks n let see........
in Bombay sify gives Big reciptes for every charge......
0

#7 User is offline   ankush Icon

  • Acha laga
  • Pip
Group:
Members
Posts:
21
Joined:
08-October 05

Posted 24 January 2006 - 07:33 PM

I THINK U R A FOOL DINESH W!!!THEY ALWAYS GIVE RECEIPTS !!!I HAVE ALL
0

#8 User is offline   white_fangs Icon

  • Acha laga
  • Pip
Group:
Members
Posts:
14
Joined:
24-January 06
Location:SANPADA

Posted 25 January 2006 - 04:12 PM

Life here in Sanpada ... cold and BORINGGGGGGGGGG!!!!!!!!!!!
mad.gif
I think Iam living on a Island....

cant we do smthing ph34r.gif apart frm waiting? blink.gif

Iam totally new <fresh>.. infact got connection 2 days before...
0

#9 User is offline   ritesh11031985 Icon

  • Ek dam Fresh
Group:
Members
Posts:
1
Joined:
28-January 06

Posted 28 January 2006 - 12:23 PM

thanx & keep it up

thank you very much
0

#10 User is offline   Tushar Icon

  • Ek dam Fresh
Group:
Members
Posts:
8
Joined:
02-February 06

Posted 02 February 2006 - 10:07 PM

Just opening ports on the firewall will not work. Sify can open every damn port on the firewall and P2P apps will still not work right. This is because each of us has a private 10.x.x.x IP address, and we receive Internet connectivity through NAT. Let me explain simplistically how this works:

Sify IP: 202.199.x.x (assume for example)
Your IP: 10.0.1.1 (assume for example)

Steps:

1. Your DC++ asks for somesuperbhub.com
2. Sify's NAT router processes the request, rewriting the source to show 202.199.x.x port 1234 (assume)
3. Request goes out to somesuperhub.com and is answered
4. Router (202.199.x.x) receives the reply, looks up its own table about who asked for it.
5. Router sends back reply to you on 10.0.1.1

This is all fine, assuming that YOU initiate the connection FIRST. What if another DC++ user across the world wants to connect to you? DC++ only uses hubs as a directory server of sorts. Actual transfers are direct. So how will the other user across the world get to you? He needs to get to 10.0.1.1, which he can't, because thats on your LAN. He needs to go through 202.199.x.x port 1234. But the router just has port 1234 OPEN. That means nothing. That just means that the request, if it comes, will be accepted into... nothing.

This is where PORT FORWARDING comes into play. Sify will need to PORT FORWARD 203.199.x.x:1234 to 10.0.1.1:1234. This way, you virtually have a public IP address. So Sify would need to do this with EVERY user for EVERY port, or simply assign a one-to-one map for EVERY user with a PUBLIC IP address. The whole point of using NAT is so that you DONT NEED to assign a public IP to everyone.

Conclusion: It's not likely to work. Not working inside the LAN is another matter altogether.

Tushar
0

  • (2 Pages)
  • +
  • 1
  • 2
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users