I find that most problems with NAT and port forwarding can be solved by common VPN software. Assuming your networkable device is running embedded linux, it's not overly difficult to set up hamachi, or even some homebrew software to create a virtual, private, unroutable IP.
Better yet, toss a bind/[insert dns server of preference] server on to one of your VPN'd boxes, and use it to do local resolution and you'll have easy to remember names that are only accessible to you.
Example scenario:
4 networked devices [toaster, dvr, etc]
1 'server' [bind, VPN server (if you're running your own)]
each device is given a non-routable IP in addition to its NAT'd DHCP ip. the bind server could provide names like toaster.devices.myhouse
That isn't true. Time warner's routing system internally 'knows' where your IP is, and if you assign yourself a static one, most incoming packets simply wont get routed. You can still browse the internet mostly, but quite a few problems start arising if you assign yourself an IP thats in a different logical network than your dynamic one.
No you can't, the hosts file that you're describing forces static lookups of certain names. What you've described is redirecting all port 80 traffic to port 443 for that domain name, which would logically be done at the router level (if your router supported such technologies, most today are woefully lacking.)
Padlocks. Lots and lots of padlocks. Those pesky electrical panels have a tendency of getting shut off, and they all seem to be outfitted with padlock holes.
Slashdot Mirror
Agreed. As an employee of a credit union, I can tell you the benefits are generally pretty substantial. Over banks anyway.
Please enter the correct response: [ k 4wesum wh3n d0 1 git mi int4rwubs? ]
I find that most problems with NAT and port forwarding can be solved by common VPN software. Assuming your networkable device is running embedded linux, it's not overly difficult to set up hamachi, or even some homebrew software to create a virtual, private, unroutable IP. Better yet, toss a bind/[insert dns server of preference] server on to one of your VPN'd boxes, and use it to do local resolution and you'll have easy to remember names that are only accessible to you. Example scenario: 4 networked devices [toaster, dvr, etc] 1 'server' [bind, VPN server (if you're running your own)] each device is given a non-routable IP in addition to its NAT'd DHCP ip. the bind server could provide names like toaster.devices.myhouse
That isn't true. Time warner's routing system internally 'knows' where your IP is, and if you assign yourself a static one, most incoming packets simply wont get routed. You can still browse the internet mostly, but quite a few problems start arising if you assign yourself an IP thats in a different logical network than your dynamic one.
whoa dude, next time just one cup of coffee with your lines in the morning.
so is this a new era for 'i want your key because [its got your data behind it] i believe you have stolen my data' lawsuits?
But will it run linux? And, better yet, if it were to kernel panic, what would the world look like?
No you can't, the hosts file that you're describing forces static lookups of certain names. What you've described is redirecting all port 80 traffic to port 443 for that domain name, which would logically be done at the router level (if your router supported such technologies, most today are woefully lacking.)
Gmail has gone live, they're allowing anyone to sign up now. It's not a private beta anymore.
Padlocks. Lots and lots of padlocks. Those pesky electrical panels have a tendency of getting shut off, and they all seem to be outfitted with padlock holes.
the plumber costs must be outrageous.