Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Is it normal to NOT be able to access an external IP from an internal host that lives on the same network as the other internal host that corresponds to the external IP?

For instance: say I'm on an internal network for widget inc and want to access widget.com which is a public IP with NAT to an internal host called widget1.local. Is it normal to not be able to do so?

share|improve this question
    
It is common, did you not see the list of a dozen or so similar questions questions when you typed in the subject for this question? –  Zoredache Apr 18 '12 at 0:27

1 Answer 1

Is it normal? Well, normal like vehicular manslaughter in a busy city. "Normal" doesn't necessarily mean "desirable" however.

It's called hairpin routing among Cisco people, but has other names (e.g. "tromboning"). Some routers support it, others don't. For example, I don't know about 2012, but three years ago Cisco's IOS did not support hairpin routing.

share|improve this answer
    
haha, thanks! Can you expand on the reasons it would be undesirable? –  CarpeNoctem Apr 18 '12 at 0:30
    
Tromboning is most notably bad for performance reasons. No need to get the SPI / routing engines involved for traffic that's on the same LAN. –  Wesley Apr 18 '12 at 0:35

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.