![]() Search build threads with the search function and search on build number.ġ0. This is an example of a build thread for build 42617 for Broadcom routers: If your post is answered and your problem solved, mark your thread with (the header of your first post).Ĩ.ĝo NOT use the router database, builds can be found at:Īll builds are beta including those from the router database.ĩ.ěefore uploading a new build to your router, research the build by looking in the build threads. This so that it can be searched and found by others.ħ. When posting pictures make sure the maximum width is not more than 600 pixels.Ħ.ĝo not hijack a thread, meaning do not post your own problem in someone else's thread. If you followed a wiki or manual let us know which one(s).įor your Network setup, state what wiki you have used: ĥ. Give as much detail as you can also provide your network setup if applicable. When posting always state router model, build number and when applicable the Kernel version.ĭescribe your problem and how you think it can be solved. Post in the right forum, from the former step you can see if your router is Broadcom, Qualcomm/Atheros, Marvell or other, use that forum to post router specific questions, for networking questions post in the Advanced Networking forum and for other things in the General Questions forum.Ĥ. In the supported devices wiki you can see if your router is supported and what architecture your router has and if you are lucky also an install guide/wiki.ģ. Research your router, start with the supported devices wiki:Ģ. Oh and if you are done configuring, a reboot often helps to get things going.īelow some pointers which might help to get the best out of DDWRT and out of the forum:ġ. I cannot imagine entering the routers own ip address as port forwarding address is in the wiki, or is it? So per forum rules it really helps if you state not only your router model but also your build number (and kernel version if applicable). Perhaps you are using a crappy build or even worse you have used the router database? What in my procedure am I doing wrong? This is clearly not rocket science yet it will not work. I understand what I am doing to a fault, and have laid out my steps in this post. So instead of my computers' IP I used my modems IP in DD-WRT port forwarding… nothing. ![]() But what seems to be happening is that the IP address Bigly is working with is my HOMES IP (Modem), 97.xx.xx.xxx. Then I had Bigly BT try to test any of those ports… nothing. I used my static IP from my computer, say 192.168.1.x, and still a range of ports, which I have set in BiglyBT. Now BiglyBT says the ports are closed when they were opened before. I figured out what to do from the jump, finding the right tab in DD-WRT (port forwarding) inputting my computers static IP in the Source Net (or leaving it blank), entering my port from range (which I have set in BiglyBT as random from 60000 to 65535) and my home actual IP to be opened. But again, I’m lost on the port forwarding area. Ok, fast forward to today, and I finally installed DD-WRT on my router to open up new options my original factory firmware didn’t have, and hopefully some new features. But BiglyBT said it was open and I was fine with it. However, when I went to the Open Port Checker website, it would say any port in that range was closed. My router is an older Buffalo WZR 1750, and I had port forwarding working on it, at least my torrent app, BiglyBT says the port ranges I specified (60000-65535, opened randomly by BiglyBT) were opened during self-tests. Posted: Mon 20:30 Post subject: Port Forwarding hell?
0 Comments
Leave a Reply. |