انجمن مدیران و راهبران شبکه

انجمن مدیران و راهبران شبکه

Network Managers and Administrators
انجمن مدیران و راهبران شبکه

انجمن مدیران و راهبران شبکه

Network Managers and Administrators

نحوه تنظیم Static Route بصورت ثابت بر روی سرور لینوکس




To keep the Static Route persistent on Linux or you want to add the route entries to the network

 script files (not using the route command) then all you need to do is to edit the file

/etc/network/interfaces

and the static routes in the following format:

up route add [-net|-host] <host/net>/<mask> gw <host/IP> dev <Interface>

Example

up route add -net 172.20.11.0/16 gw 172.20.10.254 dev eth1

And the file will like the following

sudo cat /etc/network/interfaces

The output should show something like this

sudo cat /etc/network/interfaces

The output should show something like this

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0 eth1

iface eth0 inet static
address 192.168.1.2
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.254
# dns-* options are implemented by the resolvconf package, if installed

iface eth1 inet static
address 172.20.10.1
netmask 255.255.255.0
broadcast 172.20.10.255
gateway 172.20.10.254

# static route
up route add -net 172.20.11.0/16 gw 172.20.10.254 dev eth1

The above has 2 Ethernet interfaces and the static route is added to the interface eth1.

For the change to /etc/network/interface to take effect. please restart the "networking" service as follows:

sudo /etc/init.d/networking restart

NOTE: If you added the route already using the "route" then there is no need to restart the networking service because, the next time server is restarted this takes effect.

رفع مشکل رجیستر نشدن کلاینت ها در سرور WSUS


سلام ، خدا قوت 

اگر شما هم با مشکل رجیستر نشدن کلاینت ها در کنسول سرویس WSUS در Windows server 2016 مواجه شدید لازم است بدانید برای رفع این مشکل کافیست در تنظیمات Group policy سرور Active directory اطلاعات شماره پورت سرویس WSUS را نیز به شکل زیر اضافه کنید:

http://wsussrv:8530


 


نحوه پنهانکاری آدرس مبدا - Stun messages generated by WebRTC

جهت یاد آوری  خودم  





Google Chrome:

chrome://flags

WebRTC Stun origin header -> Disable


Mozila FireFox:

about:config

media.peerconnection.ena

نحوه تنظیم Time Zone بر روی Debian Linux






Linux Debian - Set Time Zone



  جهت تنظیم Time Zone بر روی سرور لینوکس Debian از دستور زیر استفاده می شود:


dpkg-reconfigure tzdata

9 Immutable Laws of Network Design






9 Immutable Laws of Network Design


Follow these simple rules to ensure your network is stable, secure and built to last as you overlay new services and applications.


Each year, my company has the opportunity to work with many clients on their network architectures, designs and configurations. We also work with clients when they have network issues and need troubleshooting assistance. Based on those many years of experience with a variety of environments and customers, I've developed this list of nine immutable laws of network design.

Following these simple rules helps you create and maintain a stable, long-lasting network infrastructure that will be invaluable as your organization begins to overlay additional services or applications. Whether you’re redesigning for wireless, preparing for software-defined networking (SDN) or simply expanding your virtualized environments, designing by these rules will increase the stability, manageability and security of your network.

1. Know, Don’t Guess

Two phrases uttered frequently during network design are “I’m pretty sure” and “I think.” As a professional tasked with discovering, researching and documenting client networks, I can tell you those phrases don’t cut it in our organization, and they shouldn’t be accepted in yours. There’s more than a 50% chance what you think you know is wrong. Networks are inherited, many admins may touch them, and they’re frequently changed in a fit of fury, troubleshooting or testing. When documenting a network or committing even a minor change, you should always look, verify and know--never guess. The mantra in our office is, “No information is better than wrong information.”

2. Avoid Dangling Networks

As SDN, virtualization and application-based technologies creep into our networks, we need to take a hard look at configuration sprawl and prepare for a massive cleanup. Avoid dangling and mismatched networks and VLANs throughout the infrastructure. It’s not unusual to see VLANs tagged where they should be untagged, or a VLAN dead end into an untagged VLAN. There are some instances of think-outside-the-box moments where a configuration like this is needed, either for a transition period or to work around a specific situation, but the practice should be the exception, not the rule.

3. Route Where Needed, Not Where Possible

Routing at the edge sounds like an advanced approach to network architecture, but it can cause more problems than it solves. Sure, you may get some additional speed, but in most networks, that speed will never be measurable, and the complexities of overly distributed routing lead to management and security headaches.

4. See All, Manage All

You certainly can’t manage what you can’t see. Visibility into the network has always been important, and it’s going to be even more essential as networks evolve to solve the demands of virtualization and applications. Know what you have, where it is, and monitor it constantly.

5. Know When To Standardize

There are times when standardizing offers great advantages, and other times when it will be working at cross-purposes to your objectives. This might mean standardizing on a single vendor for interoperability, or it may mean standardizing on configurations, security settings and management. Either way, make sure your choice is serving a purpose and providing flexibility as your network grows in the future. Don’t get pigeonholed in to a single-vendor solution when the costs outweigh the benefits, and don’t miss opportunities to standardize on platforms that can increase effectiveness of management and security.

[ Common errors like mismatched masks and duplicate IPs can spell disaster on a network. Find out the top mistakes to avoid in "The 10 Deadliest Networking Mistakes."]


6. Layer 1 Is King

Your sleek new infrastructure of VLANs and virtual devices is complete trash if the foundation of your network is faulty. Layer 1 is king, and disruptions in Layer 1 still contribute to a huge volume of detrimental network outages. As network capabilities develop and grow, Layer 1 requirements will evolve and remain the most critical consideration.

7. Simple Always Wins

Just because you can do it doesn’t mean you should. Labs and test environments are the place to play and think outside the box with your configurations. In an enterprise production environment, you’re best served following the K.I.S.S. model, and keeping your network as simple as it can be while maintaining the required connectivity and security.

8. Power Is Important

To say we’ve been spoiled in recent decades with our power sources seems strange, but it’s true. As power demands increase with newer technology, availability and consistency of power is more critical than ever. The addition of virtualized machines and software-based appliances that are more sensitive to power issues compounds the problem. Oftentimes, power issues can cause widespread network disruptions without ever triggering an alert. Clean, conditioned, consistent power used to be a luxury, but is now a necessity in the network.

9. Embrace Documentation

You may have flashbacks of writing book reports in high school, but maintaining documentation on your network is the easiest way to ensure you’re following best practices, tracking changes and creating the means to troubleshoot effectively. As we layer on more technology and applications, documentation will increase in significance. Embrace it, live it, love it, do it. Twenty minutes of documentation now, even if you feel you don’t have 20 minutes to spare, may save you 20 hours down the road.