HELP! Virgin SuperHub Port Forwarding Problems

deejayquai · 13-02-2011, 17:56

Hi

I've just gone from a D-Link 615 + seperate modem (20 mbps) to the new superhub (30 mbps) service. The new setup has knocked out my Synology 107 homeserver and all its services that were working fine before, via the relevant port forwarding rules. I reverted back to my old router and modem and rang Virgin who said that the old set up doesn't work on the new 30 mbps service and that I would have to revert back!

I've set up all the rules in the superhub and it doesn't open the ports when I check them with a free portscanner tool. I've then set up the D-Link router to the superhub w/ DMZ and connected everything through that (using this reference- http://www.unofficialguidetolive.co....edia-super-hub), which works fine apart from the port forwarding again- these rules worked absolutely fine before. I've switched off the Superhub's firewall too but they still don't work. Any advice gratefully received as its sending me *bleep* insane.

David

PhusioNMCR · 13-02-2011, 18:03

deejay, dont expect any help, its the FW in the Stuperhub, im having the exact same problem and been met with brick walls when trying to explain this

(you should have said pc, if its anything else vm say they dont support it)

heres my thread http://www.cableforum.co.uk/board/12...upgrading.html i know it wont help you but you can see theres no help from people that can and im still having problems

qasdfdsaq · 13-02-2011, 18:39

Some members on this forum (Chrysalis for example) have managed to make it work with some tweaking.

PhusioNMCR · 13-02-2011, 18:42

You shouldnt have to do "tweeks" it should do as it say in the gui, or are the "tweeks" encouraging security breaches because the "tweek" is to disable every security setting in the SH

Chrysalis · 13-02-2011, 18:44

for it to work make sure the ethernet between 1st router and 2nd router goes in the wan not lan port on the 2nd router and ideally keep the superhub on 192.168.0.x and have the 2nd router on a diff subnet eg. 192.168.1.x (yes me and others discussed this and I was wrong in the end). The dmz should point to the wan ip of the other router, not the lan side ip.

If you do this you may need to reboot the superhub every few days tho, my superhub bombed out on dmz after about 3 days uptime last time.

Peter_ · 13-02-2011, 18:44

Turn off DHCP in the D Link and ip Flood Detection and the Firewall in the Superhub under Content Filtering> Services, I did that and my Edimax BR6504n works perfectly.

Please login by clicking http://192.168.0.1/ the username is admin and the password is change me, then click on the small red writing that says advanced settings then look down the left hand side and under Content Filtering> Services you untick ip Flood Detection and the Firewall.

I do know this is not Port Forwarding but it should help.

Chrysalis · 13-02-2011, 18:47

Quote:

Originally Posted by PhusioNMCR

You shouldnt have to do "tweeks" it should do as it say in the gui, or are the "tweeks" encouraging security breaches because the "tweek" is to disable every security setting in the SH

those settings are near useless anyway so isnt really a problem to turn them off.

PhusioNMCR · 13-02-2011, 18:59

Quote:

Originally Posted by Chrysalis

those settings are near useless anyway so isnt really a problem to turn them off.

lol, well there doing something for you to state "near useless" and this it a product that i think should have this security feature working or is firewall and ip flood protection all myths

1.so why have it there, thats right it is useless anyway cause the netgear FW is a joke full of holes so you dont even get the punch line

2. a busness router or even a high end home router has spi, work alot better than netgears, or is it there just to make u feel secure awww

in the end i dont want this waste of 5wph on my network

**Maggy J** · 13-02-2011, 19:05

OK I want to make it clear that those VM staff who are here trying to help our members do so in their own time.They DO NOT REPRESENT VM whilst here.This site is not owned by VM and is completely independent from VM.

It is not a rant site it is first and foremost a help site.Attacking the VM staff who are being as helpful as they can is not attacking VM it's merely attacking individuals who are giving up their own time to help out.

If you are angry at VM I suggest you take it up with VM.

PhusioNMCR · 13-02-2011, 19:14

point taken, its just they wont fix this problem ever, because they dont understand whats causing it, im trying to point out the problem with the SH, thats all

Chrysalis · 13-02-2011, 19:15

Quote:

Originally Posted by PhusioNMCR

lol, well there doing something for you to state "near useless" and this it a product that i think should have this security feature working or is firewall and ip flood protection all myths

1.so why have it there, thats right it is useless anyway cause the netgear FW is a joke full of holes so you dont even get the punch line

2. a busness router or even a high end home router has spi, work alot better than netgears, or is it there just to make u feel secure awww

in the end i dont want this waste of 5wph on my network

1 - its consumer impression that these are good features and useful to have, so to leave it off would cause bad publicity, (superhub insecure), but they do have limited use in certian scenarios eg. if using DMZ to a pc which would remove NAT protection. However I suspect this a SPI only firewall rather than a normal firewall.
2 - true there is better SPI variants out there, however its a feature I disable all the time on any router regardless.

PhusioNMCR · 13-02-2011, 19:19

OMG

deejayquai · 14-02-2011, 18:46

Quote:

Originally Posted by Chrysalis

for it to work make sure the ethernet between 1st router and 2nd router goes in the wan not lan port on the 2nd router and ideally keep the superhub on 192.168.0.x and have the 2nd router on a diff subnet eg. 192.168.1.x (yes me and others discussed this and I was wrong in the end). The dmz should point to the wan ip of the other router, not the lan side ip.

If you do this you may need to reboot the superhub every few days tho, my superhub bombed out on dmz after about 3 days uptime last time.

I get the following error message- "The router cannot be configured as the DMZ." if I try to use the WAN IP ie the Virgin Superhub IP of 192.168.0.1. If I use the D-Link router IP (which I've set as 192.168.0.11) under the Superhub DMZ nothing happens. I've set up all the port forwarding rules in the D-Link, turned off firewalls, DHCP, ip flood detection, etc etc

---------- Post added at 19:46 ---------- Previous post was at 19:45 ----------

Quote:

Originally Posted by Masque

Turn off DHCP in the D Link and ip Flood Detection and the Firewall in the Superhub under Content Filtering> Services, I did that and my Edimax BR6504n works perfectly.

Please login by clicking http://192.168.0.1/ the username is admin and the password is change me, then click on the small red writing that says advanced settings then look down the left hand side and under Content Filtering> Services you untick ip Flood Detection and the Firewall.

I do know this is not Port Forwarding but it should help.

Hi- done all this but still not port forwarding...

Chrysalis · 14-02-2011, 19:29

the wan ip isnt the superhubs ip.

the dlink will have 2 ips.

one for your lan, which is the gateway set in your pc's. (default 192.168.1.1)
and one for the wan, which should be shown to you somewhere in the dlink gui, on ddwrt firmware its top right. its the dlink wan ip you should set for dmz.
of course the superhub may be bombing out on you and its just been buggy, is possible. so you can try rebooting it.

incidently if you using the dlink for routing then keep dhcp enabled on it, as your lan computers wont be communicating with the dhcp server on the superhub on this setup.

also remember to connect between lan port on superhub and wan port on dlink, not a lan port on dlink.

deejayquai · 14-02-2011, 22:24

Quote:

Originally Posted by Chrysalis

the wan ip isnt the superhubs ip.

the dlink will have 2 ips.

one for your lan, which is the gateway set in your pc's. (default 192.168.1.1)
and one for the wan, which should be shown to you somewhere in the dlink gui, on ddwrt firmware its top right. its the dlink wan ip you should set for dmz.
of course the superhub may be bombing out on you and its just been buggy, is possible. so you can try rebooting it.

incidently if you using the dlink for routing then keep dhcp enabled on it, as your lan computers wont be communicating with the dhcp server on the superhub on this setup.

also remember to connect between lan port on superhub and wan port on dlink, not a lan port on dlink.

Hi thanks for your patience. I've got the D-Link running LAN IP 192.168.1.1 and its WAN (Internet) IP is 192.168.0.11 (which I set via the SH DHCP reservation).

I've got the SH DMZ on 192.168.0.11 (the D-Link's WAN IP) and connected the D-Link via ethernet from its Internet Port to the SH LAN port. I have the DHCP enabled on the D-Link too.

I've got the DHCP reservation list on the SH set to the D-Link Mac address and IP set to 192.168.0.11 too, following the instructions of setting up a seperate router here- http://www.unofficialguidetolive.co....edia-super-hub.

I've disabled the SH firewall and ip flood etc.

The port rules are set up on the D-Link for my server which is now on IP 192.168.1.103, but they still aren't forwarding (stupid question but do I need to set up the same port forwarding rules on the SH too?)