Answer the question
In order to leave comments, you need to log in
How to build such a network?
A library in the village... Last time I asked, but didn't say anything concrete, they sent it to the sysadmins...
You need to build it like this
Answer the question
In order to leave comments, you need to log in
Take and build.
What is the problem? What do you want? What specifically doesn't work for you? What was the purpose of the question?
Hmm, with such things, and even the name of the switches as splitters, you will achieve your goal for an extremely long time without a normal admin or at least an integrator.
So far, the questions are only the following:
1. Full configuration of hardware and an approximate list of tasks for server 1
2. Models of all available network equipment (switches, points)
3. Normal (full) network map, not in paint, but in visio, indicating the names of the network equipment and where EVERY (and not n, m) computer is connected
4. why it is necessary to maintain communication with someone else's network if no one goes to each other
5. decoding the type and purpose of the wireless connection, the possibility of replacing it with a wired one
6. Budget for the project
7. Full characteristics of the Internet channel: type of connection, upstream, downstream, the possibility of reservation, the prospects for transition / improvement
The splitter is apparently all the same a switch/hub/switch.
On computer1, you need to install a firewall with NAT, it is better to use some ready-made assembly, something like pfSense or another similar in functionality. On NAT, forward the port so that the web server is visible on the Internet. At the expense of the "old computer" for the role of computer1 - old age depends on the Internet channel, if there is a normal speed, then thanks to "old age" you may never see it.
Web server - usually use Apache, you can also use Windows IIS.
There is also a "foreign network" on the diagram, it is not clear what kind of entity it is, whether it needs access to the local network / your Internet. According to the mind, between someone else's network and yours, you also need to put a firewall (you can consider using computer1 for this as well) or separate it into a separate VLAN on the switch so that the networks do not intersect.
It’s better to deal with an unknown wireless connection and make it known, otherwise, it’s not even an hour, something will fall off there and you won’t know what to do.
The purpose of the wifi router is not clear, depending on the planned use of wifi, some actions need to be taken. For example, if only your employees will sit on wifi - this is one thing, if it is public with access only inside the network - it is also worth restricting it in access to the network through a firewall or by means of the router itself. If the public one with access to the Internet is a completely different story - you become a telecom operator :) it's better to avoid this.
It would be nice to find a specialist who would set up and support all this, at least "coming".
Before planning and moving forward, my personal advice is to read LinkMe-Up's " Networks for Little Ones" series of posts . In them you will find many answers to your questions. And in fact, as far as I personally understood, you are making a library based on the requirements of the Federal Law. Half you can do on OpenSource, but filtering, at your level of technical literacy, sorry, you won’t do it. For it, you need to buy a paid solution and you will be calmer.
The easiest thing for you is to take and draw everything that goes where, what, where and to whom should be available, and only after that you will understand how to implement it. 80% of solutions start with drawing and save about 50% of the time at the implementation stage.
I will support the comrade AntHTML
Author
, you should spend time and paint everything exactly - what you have now, what is connected where, what IP addresses it has. Yes, with equipment models and other details. And then describe in no less detail what exactly you want to receive. Otherwise, at the moment, your questions are read in the spirit of "How many tons of clover from each laying hen will be put into incubators after threshing the fallow?"
Why do you need blacklists? This should be done by the provider. We have already said about Yandex.DNS - you can use it.
- In order for the internal resource to be available, it is necessary to forward port 80 on the gateway.
- regarding the wireless channel - look at the pieces of iron, packets cannot be lost just like that, perhaps some kind of interference on the way.
- the computer under the gateway, as I understand it, is ancient. Should I build a local network on it? Buying a simple Mikrotik will be much more reliable, and deploy the necessary resources on the server.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question