access denied on other internet network
 

Hello
I would like to say am totally new in Linux platform so i have a simple question please suggest me.

I have one dedicated Linux server.

i want to access this server in only my internet network not to other..If anyone try to access this server in other internet network then it would give the message like access denied on this network.

so please help me how can i do this

While Linux as a whole, and certainly mainstream Linux distributions, have come a long way, working with Linux efficiently and safely requires you to have knowledge. So if you are new to Linux then you will want to read the (security) documentation your Linux distribution offers you and practice common admin tasks. Please know running a server with a Control Panel (or GUI) is no substitute for actual practical knowledge.


*Would your current question perhaps have anything to do with this: https://www.linuxquestions.org/quest...ts-4175591988/ ? Either way please update that thread with relevant information and stay with it until completion.


So what other networks are available to your server ('ifconfig -a;'?)?
What does your firewall rule set look like ('sudo iptables-save;')?
What have you already read and done to research / answer your question?

It looks to me as if this really isn't a Linux problem, but a networking problem. We need a bit more information about this situation. In addition to the questions unSpawn posed, what exactly do you mean by "my internet network" in the sentence below?

Is the server local to you, that is, is it inside your local network on the same subnet as your computer?

A very simple solution to your requirement ... available on all types of computers and operating systems ... is a firewall.

In fact, probably several firewalls: one on the router that provides access to this network "from the outside," and a second one on the target computer itself.

A firewall simply consists of a set of rules that are applied, by the operating system, to every incoming and outgoing packet. The rules will direct one disposition for each packet: ACCEPT, REJECT, or DROP.

If you "reject" the packet, they will be notified of the rejection. (But it won't be any sort of "access denied.") If you "drop" it, they won't receive any response at all.

Every operating system has some implementation of this, and some user-interface for it, as do most routers. In Linux, the low-level interface is iptables, although there are a variety of interfaces (such as Ubuntu's "UFW = Uncomplicated FireWall") to make it more palatable. The behavior and general features of all firewalls will be more-or-less the same.

Firewalls are suitable if the connections can be reasonably trusted, i.e. no one is trying to "spoof" or otherwise trying seriously to penetrate anything. The packets can be accepted for what they say that they contain, and disposed-of accordingly by the firewall.

Firewalls can also be a very useful "housekeeping" tool, since they will reliably interdict traffic that you didn't want or expect to be in some particular place within your internal network. (After all, there's no reason for servers in some part of your network to be accepting and discarding "garbage" that they never were intended to see and that they can't do anything with. "Head 'em off at the pass!")