I have only just seen this post now, it would make total sense that ipv6 routing was the issue. i only wish they knew that when i called them! id of happy adapted my rules to ipv6 if it was possible, its the future after all still cant quite get my head around it tho! would of been a good opportunity to learn.
I have tried to forward some ports are forwarded without a problem, however some other ports are impossible to forward I keep getting the same error message.
The local ports between 80 and 80 on IP 192.168.0.xx have been added as virtual server already, please try another one.
What on earth is it talking about ? Why is it compulsory to create a rule of beginning and end local ports why not put it there as an option if desired or the situation requires it then we use if not we can easily skip it, I have used IpTables I have all kinds of routers for years I have never seen where it is obligatory to specify the local start and the local end ports now it is giving me this error as if it is used elsewhere while it is not the case.
And it does that with many other ports not just the 80 or 443.
Any ideas why it is throwing this stupid error ?
However this is just one of the many things that are wrong with this hub I can make a list of the things that aren't and should never be accepted and tolerated by anyone, I know VirginMedia is a soulless corporations who cares not about anybody but its shareholders.
But we must not pay for a service that keeps breaking down and a cheap equipment that looks like it was made back in the 1940s.
It is a disgrace for a such large corporation to treat its customers like idiots.
I know that VM has the habit of testing things on its most faithful customers, VM uses its customers as its guinea pigs
I am in the process of moving out of VM as soon as possible, I have had enough, it's time to move on.
Since they took over NTL World I knew it was going to be bad news.
That was my five minute rant.
In the meantime If anyone has any idea on how to solve this issue, I would really appreciate it.
A frustrated and very disappointed VM user.
P.S I also have tried to use the Hub 3 as a modem and connected several routers (one after another) not one of them worked.
For those who are having problems with the Hub 3 I have managed to get it to work as a "Modem" and I plugged in my Linksys wireless router and I can now use it to forward all the ports.
I disabled the "firewall" in the Hub.
Plugged the second router to the Hub I then changed the Hub from a router mode to a modem mode while the second router was plugged into it, It took roughly a long painful 5 minutes for the Hub to complete the process.
After that I refreshed the page on the second router Linksys wireless router, nothing, so I went and released the DHCP and renewed it again, (you may have something similar with one of your routers) and bingo it pulled all the (external) IP address, I then plugged all of my computer and devices to the second router. I activated the wireless on the second router (since the hub was in a modem mode) now everything is working smoothly I did not notice any speed issues as a matter of a fact I actually noticed an increase in a speed it really is weird, although I know from my experience that the Linksys routers are exceptionally good next to Cisco's second perhaps after the Cisco technology, I do like them, they never let me down, I have been using them for donkeys years, They are very reliable and stable, extremely easy to configure and setup.
Ok in this order.
1) Disable firewall in Hub 3
2) Plug second router
3) Change the Hub from a router mode to a modem mode. (In some cases it can even work with the Hub as a router) (Wait for the process to complete)
4) In case your router did not pick up the IP address, try and refresh it, or by releasing and renewing the DHCP.
5) Refresh or reboot the second router, it usually clears the cache of any existing data and loads the new data served by the Hub and voilà!
Note: It might be slightly different if you're using a different type of router, but the firewall in the Hub blocks all traffic so it's best to disable it.
I hope this can help someone.
I agree with you, that it's a firmware issue, but some average users don't need all of this hassle and they certainly don't pay VM to hear their excuses.
VM is very good at making excuses, it uses the worst equipments on the market and when the s*** hits the fan they pull out the encyclopaedia of excuses.
On Virgin Media Hub 3.0 Hardware version : 10 Software version : 9.1.116V
Port forwarding works for me.
I can't get WOL from the Internet to be forwarded to my home server to wake it up, but then it's not a TCP or UDP packet, and the forwarding rules seem to be for TCP/UDP only. I never got WOL to work with BT or TalkTalk either.