Member Avatar for krupasagar

Hi,

I have an home networking which runs on wifi router (Intenet access ). Now i am planning to setup an server (ftp and web), for this i have to get an static IP address. where shd be the static IP address will be assigned and (to the home wifi router or the gateway of the router ).
Please guide me, as i want all other devices of my network to be access the internet along with my server to serve the request s from the internet.

  • 4 Contributors
  • 4 Replies
  • 218 Views
  • 8 Hours Discussion Span
  • Latest Post Latest Post by stormal1
laisenia.bale.9 commented: download Wifi programme on this computer +0

Dani AI

Generated

Quick practical summary tied to the replies: wants a home FTP + web server while keeping other devices on the same Wi‑Fi network. is right that the public address sits with the ISP and sensibly suggested dynamic DNS as an alternative—but first confirm whether the WAN address is actually publicly routable. Many consumer providers use Carrier‑Grade NAT / shared address space; if the router’s WAN IP is in the shared range or differs from the Internet‑visible IP, inbound connections won’t reach the home server without a provider‑assigned public address. (datatracker.ietf.org)

Operational security and transport: avoid plain, unencrypted FTP for remote access. Prefer SFTP (SSH subsystem) or FTP over TLS for file transfers, and run the website over HTTPS. Use an automated ACME client to get and renew certificates for the web service so TLS maintenance is not manual; this is practical for small home servers. (datatracker.ietf.org)

Quick verification steps (practical checklist):

  • From a machine outside the LAN, confirm reachability of the service ports. Example command to run on a remote host: 
    nmap -Pn -p 22,80,443 <public-ip-or-hostname>
  • Compare the router’s WAN IP to the external lookup result; a mismatch indicates provider‑side NAT. Use external scans only from networks you control. (nmap.org)

If the ISP doesn’t provide a routable public IP or blocks inbound ports, options include paying for a public/static IP, running a small VPS as a reverse proxy/tunnel endpoint, or hosting the services offsite. Operational cautions: check the ISP’s terms (hosting restrictions), keep services patched, use firewall rules (avoid broad DMZ exposure), disable UPnP for servers, and use DHCP reservation or a dedicated LAN/VLAN for the server so local addressing is stable (this complements ’s internal static‑address suggestion).

Recommended Answers

All 4 Replies

Member Avatar for JorgeM

If you are trying to access this server from outside of your private network (the Internet), the static IP address that you are referring to is the one that is provided to you by your ISP and is configured on the router or modem that connects your network to your ISP's network. This configuration can vary depending on the type of connection that your ISP provides you. You should contact them directly to get help on this configuration. You should be aware that most ISPs do charge extra for a static IP address.

As an alternate option to a static IP, there is another option. There are some services that are available on the internet that provide you with a DNS hostname and you run a client on your network that detects the current public IP address on your router, then dynamicall updates DNS host name that your are using. If the IP address changes, the host name is updated. For more information about this type of service, do a search online for dynamic dns. I havent used these services personnally in quite some time, but I used dynDNS.org for a while and I know of no-ip.com as well.

Member Avatar for CimmerianX

I use no-ip.org for my home's dynamic IP address so I can VPNin easily. It works well enough, just don't like the annoyance of having to verify I use the service every month or loose the name).

The static IP would be set at the router/modem, as JorgeM indicated. If you opt for dynamic DNS service, then you can run the dyn dns client from anywhere in the internal network to register the dynamic address (i.e. no-ip.org).

Either way, you need to configure either a port forward for http and ftp to the internal host, or use the consumer router's DMZ ip which forwards all packets to a single internal host. Then it's up to the internal host to handle blocking unwanted ports via firewall or iptables or whatever.

Member Avatar for stormal1

You can indeed use a static IP address for the server which will not be connected directly to the WAN side of the WiFi router. The router will also run a DHCP service and you can limit its DHCP IP range to not dispense IP addresses in your allocated static IP range.

IE: DHCP IP range = 192.168.1.21 thru 192.168.1.254 / Server IP address = 192.168.1.3 anything with final octet value of 2 thru 20). Your gateway address will be the same as your WiFi router.

I use such a configuration myself.

Edited by stormal1 because: typo
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.