|
I have a few questions about setting up a pretty simple home network using Ubuntu. Really, I just want a simple network share using SAMBA but I don't know enough networking to know the best way to set it up. The computers involved are 2 Ubuntu Desktops and a Macbook, with various other friends' computers connecting every so often. One ubuntu computer is mine, and our router forwards all traffic to it in DMZ mode. This means my computer gets the public-facing IP and everything else is behind NAT. I don't know enough about networking to know how to get computers behind NAT to talk to my PC, which would be hosting the files. I know I could forward just the ports I need and put my computer behind NAT, but I use a dynamic DNS so I can remote in from work/wherever, and don't really want to deal with the hassle. What's the best way to resolve the NAT/different subnet issue? Thanks!
|
| # ? Nov 07, 2009 18:17 |
|
|
|
| # ? Nov 20, 2009 23:07 |
|
|
Why does your computer have to be the DMZ? Just put everything in one logical group of computers and your router should be able to talk with all of them equally. This is just a workgroup that you want to establish, right?
|
| # ? Nov 07, 2009 19:40 |
|
|
I have a dynamic IP from my ISP, and I need my computer to get that IP so it can broadcast to my dynamic DNS service so I can remote in. If I could run the dyndns client on the router somehow then I could just forward the ports, but it's a lovely 2Wire router and I don't think there's a way to do this properly.
|
| # ? Nov 07, 2009 20:03 |
|
|
You should buy a router that can be flashed with tomato and then run the dynamic dns service off the router's wan port. Then you can do nat to the rest of your computers.
|
| # ? Nov 07, 2009 22:32 |
|
|
By dynamic DNS do you mean DynDNS? You can install a client ( should be in the Ubuntu repos ) so that it automatically updates DynDNS to point to you current public IP. http://www.dyndns.com/support/kb/us...s_services.html
|
| # ? Nov 07, 2009 22:56 |
|
|
Yeah what on earth. DynDNS has absolutely nothing to do with ports. You can run a client on a PC on your network with zero ports forwarded to it, and every ten minutes it'll check whether your external IP has changed (and if so update the website). You don't need to use a DMZ. I honestly don't understand the sentence "I need my computer to get that IP so it can broadcast to my dynamic DNS service so I can remote in". Your computer doesn't "get" the IP. Your router is assigned the IP, and all the computers behind your router appear to the world as that same IP regardless of what ports are forwarded to them. Unless, that is, you're using IPV6, which I'm pretty sure you're not.
|
| # ? Nov 08, 2009 00:45 |
|
Rate Thread:
