Finally, both the opportunity and the need to deal with routing and networks have appeared. In one switch, machines stuck with un-Schnick (suppose) 192.168.0.1\24 and 192.168.1.1\24 , and in the same switch stuck a wine server. The server has two aliases for one network card, for example: 192.168.0.10/24 and 192.168.1.10/24. On machines, the default gateway is this server for wine. And what I just did not try with the table on the server - it does not send traffic from one network to another. Help what you can. What other information is needed? Actually, the reason was found. I did not specify the default gateway on the machine in the second subnet.

  • Seriously, the following cases:> Π—Π΄Π°Π½ΠΈΠ΅ 1 ( ΠšΡƒΡ‡ΠΊΠ° машин + Π²ΠΈΠ½ сСрвСр = Π‘Π²ΠΈΡ‚Ρ‡ 1)-----ΠΎΠΏΡ‚ΠΎΠ²ΠΎΠ»ΠΎΠΊΠ½ΠΎ------Π—Π΄Π°Π½ΠΈΠ΅ 2 ( Π‘Π²ΠΈΡ‚Ρ‡ 2 = ΠšΡƒΡ‡ΠΊΠ° машин + Π²ΠΈΠ½ сСрвСр) And there will be four such buildings . And all physically - in the same network. How is this thing better set up? There is a problem with the disassembly of servers - they are under warranty, we can not plug in the optical network card. - SuperMooDuck
  • So and build. Do your switches support VLAN? How many cars will be online? - Dex
  • Switches, as I understand it, are not configured at all. Or I do not know something. Sorry did not record the model. The machines on each network are different. 10-30 on the building. We are building this way, but, I would like to divide it into subnets. As I understand it, without physical separation or VLAN, will the broadcast still go through all the buildings, regardless of the subnet? - SuperMooDuck
  • No, if divided into subnets, they will not. They will be limited only to their networks. In this case, I would suggest to break to start one range into 4 parts. Those. you take, for example, 192.168.0.0/24 and stuff all the computers into it (1 building: 1-64, 2 building 65-128 ..., etc.) In which case it will not be difficult to reconfigure everything for routing by choosing a / 26 mask. - Dex

1 answer 1

I advise you never to do this if the switch does not have a VLAN (otherwise, the extra broadcast traffic from the other network will fly to all the others, and the VLAN will limit it in its broadcast domain).

If you do 192.168.0.10/23, then no routing is needed. Machines, of course, also need to be reconfigured to 192.168.0.0/23 and issue IPs from the range 192.168.0-1.1 (0) -254 (5). But the gateway for all machines will still be 192.168.0.10. In this case, with an ordinary switch will work.

If you still need routing, then the question is:

And between computers in the same network bags run?

As for the table, it does not require additional configuration, because the packets going through the gateway to another network will be automatically forwarded to it (another network) because the routing table already has an entry for two interfaces.

UPD

This record from Microsoft says that it is necessary to do in order to enable routing in Windows (on the server, on the main router, on ordinary machines, there is no sense from this operation).

UPD2

Since the person is silent, I can assume that the solution was found.

  • The fact of the matter is that traffic is not routed. Subnets work quite fine. All machines in the subnet ping each other, including the server. The server, too, pings any machine on any subnet, having un-Schniki from both subnets. But the tracert stalls on the server. From both subnets. - SuperMooDuck
  • 1. A routing table can lead? 2. Required services running? 3. Firewall to block traffic? - Dex
  • 1. zalil.ru/31609250 (in the comment does not fit) 2. What services? Routing? Without it, the route setting guide does not work, so yes. No firewall. - SuperMooDuck
  • In my opinion, everything is fine. I feel that somewhere a small mistake and therefore everything does not work. - Dex
  • one
    The option is good, only in terms of cost and usability for the client is not always acceptable. - Dex