How does BitComet PortForwards ?

[assassino]

I'm trying to open a few ports. I've got my router password, set DMZ, set virtual server, all I could do. BUT THE PORTS WON'T OPEN.

Then comes bitcomet with it's UPNP: I type the desired port in BitComet configs, and now they are magically open !

SO, BitComet can control my router and I cannot

I even tried

"C:\Program Files\BitComet\tools\UPNP.exe" -add -app BitComet -lanip 192.168.0.3 -tcpport 9988 -udpport 9988 -q

Didn't work

Router is a TG862 Arris

What am I missing ?

Edited September 5, 2013 by assassino (see edit history)

[queeniequ]

Hi, please check here. http://wiki.bitcomet.com/add_port_mapping_in_nat_router

[The UnUsual Suspect]

Routers have a bad habit of doing exactly what you tell them to do, not what you intended to tell them to do. The DMZ setting will undo the work you did setting up a virtual server and will direct all inbound traffic towards one device. This is only recommended in certain situations. You're really going to have to learn what your router does and how it's controlled if you want to manually configure it. This has nothing at all to do with bitcomet other than the fact that bitcomet requires direct bi-directional internet connection to operate efficiently. If you chose to install a router between the computer that's running bitcomet and the internet, that makes you the network administrator of that local area network (LAN), and many members do this then expect BitComet to do their job of configuring their network for them. It's not bitcomet's job to configure networks, that is the network administrator's job.

However, you have discovered that your router supports uPnP (universal plug and play), which when enabled in the router, windows, firewall/s and bitcomet, can (sometimes) open the port for you. uPnP works great when it works, if it doesn't you'll need to do a lot of work to figure out why, and even though it's called "universal", that doesn't mean that they all do it the same way or all play by the same rules and "plug n play" doesn't mean it will instantly work when you plug it in, it only means that after you get it to work it requires no effort to enable when you plug the device in. Some people assume a PnP device will configure everything around it to work with it, this is not the case. When the uPnP option is enabled in BitComet it will look for a uPnP device. If windows allows it to talk to your router and your firewall allows it, your router supports uPnP and it's enabled, and the routers firmware is compatible with bitcomet, your port will seem to magically open in which case "it's miller time", and you should kick back and enjoy a "cold one" and be happy it works.

If "success" isn't your goal then you are free to tinker with the system and learn how to open your ports manually, but if you do something that stops uPnP from working, we aren't going to have a magical fix to undo whatever caused it. In fact we recommend ignoring uPnP if it doesn't work. We all have bitcomet in common and many members are quite expert at using it, but there are countless models of routers and if you have a router problem you're not likely to find help here. You could get lucky and find a member with the same model, but if you do you'd be very lucky and I'd recommend buying a lottery ticket before that luck runs out. Routers are best supported in a router forum or support site.

My own personal opinion is since you have it working, why aren't you enjoying a cold beer instead of messing with DMZ and virtual servers? If you just want to learn then that is great, but asking about your router in a bittorrent community support forum is sorta like asking your car dealer about how the automatic toll booths work in the harbor tunnel. You may feel like it's all related but the service manager is going to tell you "dude, the car requires an open tunnel to drive through, it's upto you to provide that tunnel". However, we all enjoy a meaningful discussion about related technology so you're free to discuss router issues here just understand it's not really a bitcomet issue. If you want to know exactly how bitcomet requests a uPnP device to open a port, that is proprietary info that only the development team has, but you can use a tool like "wireshark" to capture the commands and analyse it yourself. You can learn a lot about how things work by doing some basic reverse engineering, but if you're still trying to master dmz and virtual servers, I don't think you're ready for troubleshooting uPnP protocols.

Lastly, if you find you're in over your head and need someone to straighten out things you can always contact your local tech college or university and ask one of the professors to recommend a student that is both talented and hungry, you'll probably get an hour or two of his/her time for about $50, and feeding a geek is surely a worthy cause. Todays geeks are tomorrows business leaders and in this economy we badly need up and coming business leaders.

So feed a geek, thank a geek, hug a geek... whatever, it's all good, and good luck with your new position as a network administrator.

[assassino]

Thanx Queeniequ,

That document really helps me understand my own device.

What comes forward is that uPnp thing I didn't know existed, and can be easily set even through windows !

The question now is how does it do that, and not how BitComet does that.

Obviously I tried setting ports manually in my router. I know how to deal with most of it.

And I need ports permanently open for many other apps

But ONLY BitComet so far knew successfully how to do that. That's why I came here.

I'll follow your advice and turn off dmz. But I still need the ports. Will use Windows uPnp.

Won't need to pay for help if that works...

Thanx UnusualSuspect too

[The UnUsual Suspect]

How Universal Plug n Play works