Haiku LAN vs WAN Access

[jmorris644]

What is the best way to handle LAN vs WAN access with Haiku? Currently I use DynDNS for all of the access but the other day when I was home the internet was down and I had to go in and reconfigure Haiku for local access.

Does everyone use 2 controller setups?

Thanks

Joe

 

[lupinglade]

Using the WAN address for both is usually best for seamless switching between connections, but I guess it can't hurt to have a second LAN controller for the times when Internet access may be down.

 

[tigers]

I have to use 2 controllers setup because my router does not allow NAT looping (that is: connecting via a public IP to a device that is part of my local network). So I have a LAN config when I'm at home and a DynDNS one when I'm away.

The difference in operating speed is negligible, so if your router supports NAT looping I guess it's OK operating as lupinglade said.

 

[tmbrown97]

If my internet were down, I don't know that i'd care about automation not working - I'd probably be in a corner lost, not knowing what to do with myself!

All kidding aside, I'm curious which router didn't support the NAT looping... I've had trouble getting it to work on Cisco (it's a pain - search for "NAT on a stick") but it's always worked fine with cheapo netgear routers. Unless you have some particular attachment to your existing router (need it for VOIP or something special) I'd just swap it for a netgear that supports the feature and move on.

Another workaround I have done in the past is use use my own DNS server in the house (on the router or elsewhere - somewhere always on) and set the internal DNS to respond with the internal IP; then when you're outside the house you'll be hitting public DNS and getting the public address. When I was running Cisco ISR routers in my house, I had to do this because the NAT on a stick was more trouble than it was worth.

 

[tigers]

Uhm, I DO have a Netgear DG834V5 which is NOT a good router. I had to downgrade to the original firmware since every update had a bug with NTP server update that prevented it to work with DynDNS.

I can see no setup for NAT looping, I simply realized it won't work.
I'm going to change it sooner or later and I'll check to see if the new one has these options.

 

[jmorris644]

I have a Netgear WNDR3700. No NAT loopback there either.

I also use Open-Mesh and have a tech request into them.

Joe

 

[tmbrown97]

Odd - I've done the NAT loopback with every Netgear I've had - and I've never had an issue with them. I've had several of their higher end consumer routers (including the WNDR models), and now I'm using a business class Netgear UTM and they've all worked flawlessly with simple port forwarding.

I will say I've never had success running DynDNS on any router - despite telling the thing to update at least once every 30 days, I've never found one that reliably does. My IP only changes maybe once a year. I run the updater on an always-on computer instead.

Perhaps post a screenshot of your rule?

 

[lupinglade]

Yeah, I would think NetGear should work too for loopback, its available on most routers. Any router without this feature is not very useful for anything more advanced than web browsing. Maybe some other rule or something is conflicting with this? Such as a default NAT destination host or having the web interface enabled on the WAN port? Or maybe its an issue of differing interfaces? Though again on a good router none of this should matter, it should still work. I can definitely vouch for Apple's routers always working for NAT loopback.