APLawrence.com -  Resources for Unix and Linux Systems, Bloggers and the self-employed

Nat-nat


© July 2008 Anthony Lawrence

I had a customer move their office last week. Verizon said that "everything will be the same" - same IP, same type of T1, so in theory all they had to do was unplug their router(s), move them over, replug and all would be fine..

Just in case, the customer had asked me to be on-site and at first everything seemed fine.. I moved the routers (we have a VPN router behind Verizon's Netopia), replugged and expected a miracle, but nothing worked.. I called Verizon.

"Oh yeah", said the Verizon tech, "the number of channels has changed - you need to change that on the Netopia".

Okey dokey, 'cept I don't have the password to the Netopia because they installed that. We tried Verizon's "default" password, no go. Now what?

Well, the Netopia can be reset from a hole on the bottom. I hated doing that, but had no other choice. After the reset, the tech led me through the Netopia config without a problem.. except..

During the config the tech asked "Are you Natting?". I replied "Yes", because we have our VPN router set to hand out private dhcp addresses. He said "Fine, because we can't double nat".

Yeah.. so anyway, everything seemed to come up all right, we had internet access, but our VPN's wouldn't come up. Maybe a routing problem?

I decided to give it till the next morning, but it still wasn't up then. Called Verizon again. We went over the Netopia setup. When we got to the last screen, I noticed that "IP Address Serving" was turned on. "Doesn't that mean it's natting?", I asked. The tech mumbled something and said he'd have to call me back..

I didn't want to mess with their router, so I waited patiently and soon enough that tech and another called back. We went through the config again, and when we got to the last screen the new tech said "It's natting - are you natting?".

I sighed. "Yes, I am". We turned that off and moments later the VPN's came up.


Got something to add? Send me email.





(OLDER)    <- More Stuff -> (NEWER)    (NEWEST)   

Printer Friendly Version

->
-> Troubleshooting double NAT

1 comment


Inexpensive and informative Apple related e-books:

Sierra: A Take Control Crash Course

Take Control of Parallels Desktop 12

iOS 8: A Take Control Crash Course

Are Your Bits Flipped?

Take Control of OS X Server




More Articles by © Anthony Lawrence






Thu Jul 10 15:20:03 2008: 4410   BruceGarlock


"Working" with Verizon always means something will go wrong, or not be the way they say it will be. In fact, I don't think I have ever had a positive experience working with them. I can remember one time I had to order a DSL circuit, and I actually thought everything was going well. Then the install date came, and went, no DSL. A week later, and many phone calls, and then someone finally figured out what happened - they never "pushed" the order to the next department! I should have known. I ordered it on a Friday afternoon, and for all I know the person taking the order was being extra nice, so she could hit happy hour. I really, honestly said after that call "Gee, that went so smooth! Maybe Verizon is getting better!" Nope. No go. They still messed up. It never fails when "working" with Verizon.




------------------------


Printer Friendly Version

Have you tried Searching this site?

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more.

Contact us


Printer Friendly Version





I love deadlines. I love the whooshing noise they make as they go by. (Douglas Adams)




Linux posts

Troubleshooting posts


This post tagged:

Networking

Troubleshooting



Unix/Linux Consultants

Skills Tests

Unix/Linux Book Reviews

My Unix/Linux Troubleshooting Book

This site runs on Linode





SCO Unix Sales, Support, & Service

Phone:  707-SCO-UNIX (707-726-8649Toll Free: 833-SCO-UNIX (833-726-8649)
www.SCOsales.com