![]() ![]() |
LennonNZ: I presume there is a security hole in the router which allows external people to change the DNS servers on the router thus hijacking people's traffic.
Changing the APN to wap.telecom.co.nz from internet.telecom.co.nz makes the router have a non public ip address thus not accessible from the internet but it doesn't fix the security issue but mitigate it
Maybe a good solution but what about people who actually want a real world ip address? a New firmware version or what?
Ragnor: Have you tried asking Telecom via one of their support channels?
No guarantee they will notice a thread on a 3rd party forum like Geekzone.
Try their Twitter
https://twitter.com/TelecomNZ
Ragnor: Have you tried asking Telecom via one of their support channels?
No guarantee they will notice a thread on a 3rd party forum like Geekzone.
Please support Geekzone by subscribing, or using one of our referral links: Samsung | AliExpress | Wise | Sharesies | Hatch | GoodSync | Backblaze backup
dimsim:Ragnor: Have you tried asking Telecom via one of their support channels?
No guarantee they will notice a thread on a 3rd party forum like Geekzone.
Try their Twitter
https://twitter.com/TelecomNZ
I've just wasted 20 minutes on the phone to a muppet who knows nothing... I had this fixed for another client in five minutes a week ago just from speaking to the right person... I was hoping for someone a little higher up the food chain to provide a definitive answer/comment/solution.
freitasm:Ragnor: Have you tried asking Telecom via one of their support channels?
No guarantee they will notice a thread on a 3rd party forum like Geekzone.
Actually they're pretty good here - including other ISPs.
Yyrael:loldimsim:Ragnor: Have you tried asking Telecom via one of their support channels?
No guarantee they will notice a thread on a 3rd party forum like Geekzone.
Try their Twitter
https://twitter.com/TelecomNZ
I've just wasted 20 minutes on the phone to a muppet who knows nothing... I had this fixed for another client in five minutes a week ago just from speaking to the right person... I was hoping for someone a little higher up the food chain to provide a definitive answer/comment/solution.
I am looking into it but usually saying I'm looking into it isn't a very useful reply hence why you have no reply yet.
But you've forced my hand!
"Looking into it."
dimsim:Yyrael:loldimsim:Ragnor: Have you tried asking Telecom via one of their support channels?
No guarantee they will notice a thread on a 3rd party forum like Geekzone.
Try their Twitter
https://twitter.com/TelecomNZ
I've just wasted 20 minutes on the phone to a muppet who knows nothing... I had this fixed for another client in five minutes a week ago just from speaking to the right person... I was hoping for someone a little higher up the food chain to provide a definitive answer/comment/solution.
I am looking into it but usually saying I'm looking into it isn't a very useful reply hence why you have no reply yet.
But you've forced my hand!
"Looking into it."
nice one - thanks.
My comments and remarks are not necessarily of my employer.
plambrechtsen: Just one point of clarification.
Neither wap.telecom.co.nz or internet.telecom.co.nz are internet accessible APNs. "wap.telecom.co.nz" is a Carrier Grade NAT range that goes via the WAP Gateway and thus is true private address and the IP Address allocated to you will not be your internet IP address. "internet.telecom.co.nz" you get a public address but it's behind a router/firewall that only allows outbound connections.
If for whatever reason you did want inbound connections to your router you should use "direct.telecom.co.nz" which does give you direct access to your router from the internet.
Using "direct.telecom.co.nz" would mean that if your router had been "owned" and someone was using it as a DNS Relay, you could be up for a very nasty bill.
So what is the actual problem you are trying to solve?
Edit: It wouldn't be related to this issue? http://forums.whirlpool.net.au/archive/1856871
gajan: Network changes have been made in the last 48hours for the Netcomm DNS Ports. The issue should now be resolved (for both APNs). If you are still having DNS issues with the Netcomm device PM me some details, and I'll get someone to look into this.
![]() ![]() |