Jun 27
Please be informed that the speedtouch ST536 from Singnet is a router and adsl modem rolled into one. It is not the same as starhub’s cable modem. It is not just a modem where you plug it to the WAN/INTERNET port of your home consumer router. Buy another adsl/2+ modem (purely just a modem) and do your singnet configuration like PPPoE/A VCI = 100, VPI = 0, username and password if you feel the below suggestions are too much of a hassle.
You have to either disable the router in Speedtouch by putting it into bridge mode, or enabling bridge mode on your router of choice (subjected to availability of this feature on your router), or disable DHCP at your router, set your router IP address to be in the range of the speedtouch dhcp range and plug it to the LAN/switch ports.
Choice 1: Disable router in speedtouch ST536. Basically do it in command line. Apparently singnet GUI does not have such an option, not sure with further firmware updates, but as of now, command line. Is a bitch to do for some, daunting for some. Burning an ISO to do is another method, but I’m not sure if singnet permits. Connect from speedtouch to your router WAN/INTERNET port. This will be the best method in my opinion as you can freely configure your router knowing the speedtouch is acting just as a modem and not router/gateway, applying firewall rules, port forwarding and QoS with ease.
Choice 2: Enabling bridge mode on router. For my Dlink DGL 4300 router, I can configure the WAN/INTERNET port to bridge mode, therefore no configurations to be done on the speedtouch router. Everything else applies and you can set DMZ of the router on speedtouch, or simply turn off the firewall on the speedtouch so that during port forwarding, you do not have to do it on your router and again on speedtouch. This will eliminate problems especially during port forwarding in future. A good method to use if you do not want to change the firmware of your speedtouch. A good thing anyway, in case singnet gets buggy during support, saying that personal upgrade of firmware is not permitted or stupid stuffs like this. QoS, port forwarding might be a problem, subjected to the bridge mode capabilities of the router.
Choice 3: Another method, basically using your router (also switch rolled into one) as a wireless access point. You connect the speedtouch Ethernet to any of the LAN/switch ports of your router, not to the WAN/INTERNET port. The main drive was that speedtouch ST536 do not have wireless capabilities, therefore requiring the router to act as a wireless access point and switch. Set the router IP to be in the range of the DHCP scope of speedtouch, default 192.168.1.100 /24. So choose something like 192.168.1.140 for your router in case of IP conflict, leaving about 40 new devices to connect and get IP addresses from the DHCP of speedtouch, not your router. Applying QoS, firewall rules and port forwarding of your router will be a problem, basically you are relying on the QoS, firewall and port forwarding of speedtouch. Used when there is no bridge mode option on the WAN/INTERNET port for your router. Few people tinkers with their QoS, firewall and port forwarding anyway, so it’s a viable method.
Conclusion: In order of personal preference, choice 1 then 2 then 3. Good luck. I’m sticking to cable. Call up singnet for more help, if they render any. Haha