One to One NAT and Telus
Posted by Kelly Adams on December 29th, 2005
Print This Post
I mentioned in my previous blog entry the fun I was having getting my new Firewall/Router (LinkSys RV016) working properly. My original plan was to set up my web server behind the RV016 and use one to one network address translation (NAT) and firewall rules to manage access.
Unfortunately, I couldn’t get this to work. And it started to dawn on me that really, it *couldn’t* work with the way Telus assigns IP addresses to devices. Telus’s home and Business ADSL services use a tool whereby you identify the MAC (physical layer) address of your device, and Telus uses that to provide an IP address to that device via DHCP. Since the RV016 has a single MAC address, Telus can’t assign it two IP addresses and allow the RV016 to route appropriately: in essence, Telus is assuming you are either directly connected to their network, or behind a simple one to many NAT device.
I got this confirmed by Telus technical support today. Now, I’m not saying I trust the technical response since they really didn’t confirm that my understanding of why it wasn’t working was correct. They just indicated that I *was* correct in assuming that there was no way with their standard service to allow one MAC address to service multiple IP addresses. According to them, I’d need to upgrade to managed ADSL to get this capability.
I have a call in with Telus now, but my recollection of Telus’ managed ADSL service suggests that I’d likely be looking at about $500 a month to get it. That won’t fly for me- that’s insanely expensive. I won’t find out until the new year when Telus will hopefully call me back.
Technorati Tags: Linksys, One to One NAT, Telus

May 8th, 2006 at 4:03 pm
Hi,
Just curious, did you ever get a response from the T-word? I am attempting the exact same thing and have found that their OCA Website won’t allow me to map the same MAC to both my IPs. Any work around? Thanks.
–Dan
May 8th, 2006 at 10:34 pm
Greetings, Dan!
Yeah I got a call back from Telus. It’s a few months ago now, but as I recall the gist was that I was right. If I wanted support for one to one NATing, I’d need to go with managed ADSL and it was about $500 a month.
I started to check out another service provider, Smarttnet. They have a true “static IP” managed ADSL service for under $100 a month that looked like it would do the trick. But functionally I was able to get what I wanted more or less working, and I didn’t want to go through the hassle of changing providers.
Smarttnet (yes, there are two “t”s in the name) is in business in BC and Alberta- they might be worth checking out if you are looking for the service.
June 4th, 2008 at 3:57 pm
Originally found this post cause I was pissed off at Telus for the very same issue. Thank you Kelly Adams for your find. I signed up with SmarttNet with a $80 dollar package…Telus quoted me more than $450. I’ve saved TONS!
Why isn’t CRTC doing anything? It’s not right for Telcos to advertise one rate (as low as $15) but then charge you when you need additional stuff. Actually, paying $15 or even $50 more is okay. But close to $500? They do it because they know you are desperate.
June 4th, 2008 at 5:52 pm
Thanks for commenting here, John!
It is good to hear a comment from someone using SmarttNet. I’m still with Telus- actually, I now have both Shaw Cable and Telus, and am using a load balancing router.
Regarding the fees Telus charges- big companies sometimes do that more out of being process-bound than out of any real malicious intent. They might have everything automated for setting up a “standard” ADSL service, and then have to kick you over to another department with more manual services and of course much higher costs for anything out of the ordinary. I’m not sure if this is the case at Telus, but it *seems* that way.
In any case, I’m glad to hear you have had good luck with SmarttNet. I’ll keep them on my list for any future changes to my network.
June 19th, 2008 at 12:23 pm
Did you try to clone the MAC of your server on the RV016? You can choose to clone a MAC for each Internet connection. This would allow you to have more than the single MAC.
June 20th, 2008 at 1:28 pm
Hello, Kenn, and welcome to my blog…
It has been a long time since I last looked at this, but I think we are talking about two different things. MAC cloning allows you to over-ride the embedded MAC address on a device, and replace it with the MAC address from another device.
One to One NAT is quite a different animal entirely. Normally, Network Address Translation is “one to many”: it puts a single IP address on the WAN side of your router. Any in-bound traffic (E.G.: from the Internet) sees just that single IP address, regardless how many devices you have on the other side of the router. If you want (for example), HTTP traffic to go to a particular server behind your router, you use “port mapping”: all the port 80 related inbound traffic can be directed to a single IP address on your LAN.
But what would you do if you wanted to have multiple servers inside your LAN that could handle port 80 traffic? That’s where one to one NAT comes in. Your router responds to several different IP addresses on the WAN side. Traffic to a given specific WAN IP address can then be directed to a specific LAN IP address…. one (WAN) IP to one (LAN) IP.
Now watch: you probably know everything I just explained, and were saying something completely different than what I thought you were…that’s the way communication goes some times
June 20th, 2008 at 5:55 pm
He may have, but I didn’t. And now I know.