This is a three step process:
- Issue the command: hostname new-host-name
- Change network configuration file: /etc/sysconfig/network
Edit entry: HOSTNAME=new-host-name - Restart systems which relied on the hostname (or reboot):
- Restart network services: service network restart
(or: /etc/init.d/network restart) - Restart desktop:
- Bring down system to console mode: init 3
- Bring up X-Windows: init 5
One may also want to check the file /etc/hosts for an entry using the system name which allows the system to be self aware.
The hostname may be changed at runtime using the command: sysctl -w kernel.hostname="superserver"
Change the host name using GUI tool: /usr/sbin/system-config-network
(Red Hat / Fedora / CentOS)
Hostname entries are made in two places:
| |
| Select the "DNS" tab. | Select the "Devices" tab + "Edit" + the "General" tab. |
Assign more than one IP address to one ethernet card:
ifconfig eth0 XXX.XXX.XXX.XXX netmask 255.255.255.0 broadcast XXX.XXX.XXX.255
ifconfig eth0:0 192.168.10.12 netmask 255.255.255.0 broadcast 192.168.10.255
ifconfig eth0:1 192.168.10.14 netmask 255.255.255.0 broadcast 192.168.10.255
route add -host XXX.XXX.XXX.XXX dev eth0
route add -host 192.168.10.12 dev eth0
route add -host 192.168.10.14 dev eth0
In this example 0 and 1 are aliases in addition to the regular eth0. The result of the ifconfig command:
eth0 Link encap:Ethernet HWaddr 00:10:4C:25:7A:3F
inet addr:XXX.XXX.XXX.XXX Bcast:XXX.XXX.XXX.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14218 errors:0 dropped:0 overruns:0 frame:0
TX packets:1362 errors:0 dropped:0 overruns:0 carrier:0
collisions:1 txqueuelen:100
Interrupt:5 Base address:0xe400
eth0:0 Link encap:Ethernet HWaddr 00:10:4C:25:7A:3F
inet addr:192.168.10.12 Bcast:192.168.10.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:5 Base address:0xe400
eth0:1 Link encap:Ethernet HWaddr 00:10:4C:25:7A:3F
inet addr:192.168.10.14 Bcast:192.168.10.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:5 Base address:0xe400
Config file: /etc/sysconfig/network-scripts/ifcfg-eth0:0
DEVICE=eth0:0 ONBOOT=yes BOOTPROTO=static BROADCAST=192.168.10.255 IPADDR=192.168.10.12 NETMASK=255.255.255.0 NETWORK=192.168.10.0 ONBOOT=yes
|
Aliases can also be shut down independently. i.e.: ifdown eth0:0
The option during kernel compile is: CONFIG_IP_ALIAS=y (Enabled by default in Redhat)
Note: The Apache web server can be configured so that different IP addresses can be assigned to specific domains being hosted. See Apache configuration and "configuring an IP based virtual host" in the YoLinux Web site configuration tutorial.
The concept of network classes is a little obsolete as subnets are now used to define smaller networks. These subnets may be part of a class A, B, C, etc network. For historical reference the network classes are defined as follows:
- Class A: Defined by the first 8 bits with a range of 0 - 127.
First number (8 bits) is defined by Internic i.e. 77.XXX.XXX.XXX
One class A network can define 16,777,214 hosts.
Range: 0.0.0.0 - 127.255.255.255 - Class B: Defined by the first 8 bits with a range from 128 - 191
First two numbers (16 bits) are defined by Internic i.e. 182.56.XXX.XXX
One class B network can define 65,534 hosts.
Range: 128.0.0.0 - 191.255.255.255 - Class C: Defined by the first 8 bits with a range from 192 - 223
First three numbers (24 bits) are defined by Internic i.e. 220.56.222.XXX
One class B network can define 254 hosts.
Range: 192.0.0.0 - 223.255.255.255 - Class D: Defined by the first 8 bits with a range from 224 - 239
This is reserved for multicast networks (RFC988)
Range: 224.0.0.0 - 239.255.255.255 - Class E: Defined by the first 8 bits with a range from 240 - 255
This is reserved for experimental use.
Range: 240.0.0.0 - 247.255.255.255
Forwarding allows the network packets on one network interface (i.e. eth0) to be forwarded to another network interface (i.e. eth1). This will allow the Linux computer to conect ("ethernet bridge") or route network traffic.
The bridge configuration will merge two (or several) networks into one single network topology. IpTables firewall rules can be used to filter traffic.
A router configuration can support multicast and basic IP routing using the "route" command. IP masquerading (NAT) can be used to connect private local area networks (LAN) to the internet or load balance servers.
All methods will result in a proc file value of "1". Test: cat /proc/sys/net/ipv4/ip_forward
The TCP Man page - Linux Programmer's Manual and /usr/src/linux/Documentation/proc.txt (Kernel 2.2 RH 7.0-) cover /proc/sys/net/ipv4/* file descriptions.
Alos see: (YoLinux tutorials)
| Usefull Linux networking commands: |
- /etc/rc.d/init.d/network start - command to start, restart or stop the network
- netstat - Display connections, routing tables, stats etc
- List externally connected processes: netstat -punta
- List all connected processes: netstat -nap
- Show network statistics: netstat -s
- Kernel interface table info: netstat -a -i eth0
- ping - send ICMP ECHO_REQUEST packets to network hosts. Use Cntl-C to stop ping.
- traceroute - print the route packets take to network host
- traceroute IP-address-of-server
- traceroute domain-name-of-server
- mtr - a network diagnostic tool introduced in Fedora - Like traceroute except it gives more network quality and network diagnostic info. Leave running to get real time stats. Reports best and worst round trip times in milliseconds.
- mtr IP-address-of-server
- mtr domain-name-of-server
- whois - Lookup a domain name in the internic whois database.
- finger - Display information on a system user. i.e. finger user@host Uses $HOME/.plan and $HOME/.project user files. Often used by game developers. See http://finger.planetquake.com/
- iptables - IP firewall administration (Linux kernel 2.6/2.4) See YoLinux firewall/gateway configuration.
- ipchains - IP firewall administration (Linux kernel 2.2) See YoLinux firewall/gateway configuration.
- socklist - Display list of open sockets, type, port, process id and the name of the process. Kill with fuser or kill.
- host - Give a host name and the command will return IP address. Unlike nslookup, the host command will use both /etc/hosts as well as DNS.
Example: host domain-name-of-server - nslookup - Give a host name and the command will return IP address. Also see Testing your DNS (YoLinux Tutorial) Note that nslookup does not use the /etc/hosts file.
| inetd/xinetd: Network Socket Listener Daemons: |
The network listening daemons listen and respond to all network socket connections made on the TCP/IP ports assigned to it. The ports are defined by the file /etc/services. When a connection is made, the listener will attempt to invoke the assigned program and pipe the data to it. This simplified matters by allowing the assigned program to read from stdin instead of making its own sockets connection. The listener hadles the network socket connection. Two network listening and management daemons have been used in Red Hat Linux distributions:
- inetd: Red Hat 6.x and older
- xinetd: Red Hat 7.0-9.0, Fedora Core
- Configuration file: /etc/inetd.conf
Entries in this file consist of a single line made up of the following fields: service socket-type protocol wait user server cmdline
- service: The name assigned to the service. Matches the name given in the file /etc/services
- socket-type:
- stream: connection protocols (TCP)
- dgram: datagram protocols (UDP)
- raw
- rdm
- seqpacket
- protocol: Transport protocol name which matches a name in the file /etc/protocols. i.e. udp, icmp, tcp, rpc/udp, rpc/tcp, ip, ipv6
- wait: Applies only to datagram protocols (UDP).
- wait[.max]: One server for the specified port at any time (RPC)
- nowait[.max]: Continue to listen and launch new services if a new connection is made. (multi-threaded)
Max refers to the maximum number of server instances spawned in 60 seconds. (default=40) - user[.group]: login id of the user the process is executed under. Often nobody, root or a special restricted id for that service.
- server: Full path name of the server program to be executed.
- cmdline: Command line to be passed to the server. This includes argument 0 (argv[0]), that is the command name. This field is empty for internal services. Example of internal TCP services: echo, discard, chargen (character generator), daytime (human readable time), and time (machine readable time). (see RFC)
Sample File: /etc/inetd.conf
#echo stream tcp nowait root internal #echo dgram udp wait root internal
ftp stream tcp nowait root /usr/sbin/tcpd in.ftpd -l -a #pop-3 stream tcp nowait root /usr/sbin/tcpd ipop3d #swat stream tcp nowait.400 root /usr/sbin/swat swat
|
A line may be commented out by using a '#' as the first character in the line. This will turn the service off. The maximum length of a line is 1022 characters. The inet daemon must be restarted to pick up the changes made to the file:
/etc/rc.d/init.d/inetd restart
For more information see the man pages "inetd" and "inetd.conf".
| xinetd: Extended Internet Services Daemon: |
- Xinetd has access control machanisms, logging capabilities, the ability to make services available based on time, and can place limits on the number of servers that can be started, redirect services to different ports and network interfaces (NIC) or even to a different server, chroot a service etc... and thus a worthy upgrade from inetd.
Use the command chkconfig --list to view all system services and their state. It will also list all network services controlled by xinetd and their respective state under the title "xinetd based services". (Works for xinetd (RH7.0+) but not inetd)
The xinetd network daemon uses PAM also called network wrappers which invoke the /etc/hosts.allow and /etc/hosts.deny files.
Configuration file: /etc/xinetd.conf which in turn uses configuration files found in the directory /etc/xinetd.d/.
To turn a network service on or off:
- Edit the file /etc/xinetd.d/service-name
Set the disable value:
- disable = yes
or
disable = no
Restart the xinetd process using the signal: - SIGUSR1 (kill -SIGUSR1 process-id) - Soft reconfiguration does not terminate existing connections. (Important if you are connected remotely)
- SIGUSR2 - Hard reconfiguration stops and restarts the xinetd process.
(Note: Using the HUP signal will terminate the process.)
OR
- Use the chkconfig command: chkconfig service-name on
(or off)
This command will also restart the xinetd process to pick up the new configuration.
The file contains entries of the form:
service service-name
{
attribute assignment-operator value value ...
...
{
Where: - attribute:
- disable:
- type:
- RPC
- INTERNAL:
- UNLISTED: Not found in /etc/rpc or /etc/services
- id: By default the service id is the same as the service name.
- socket_type:
- stream: TCP
- dgram: UDP
- raw: Direct IP access
- seqpacket: service that requires reliable sequential datagram transmission
- flags: Combination of: REUSE, INTERCEPT, NORETRY, IDONLY, NAMEINARGS, NODELAY, DISABLE, KEEPALIVE, NOLIBWRAP.
See the xinetd man page for details. - protocol: Transport protocol name which matches a name in the file /etc/protocols.
- wait:
- no: multi-threaded
- yes: single-threaded - One server for the specified port at any time (RPC)
- user: See file : /etc/passwd
- group: See file : /etc/group
- server: Program to execute and recieve data stream from socket. (Fully qualified name - full pathe name of program)
- server_args: Unlike inetd, arg[0] or the name of the service is not passed.
- only_from: IP address, factorized address, netmask range, hostname or network name from file /etc/networks.
- no_access: Deny from ... (inverse of only_from)
- access_times
- port: See file /etc/services
Also: log_type, log_on_success, log_on_failure (Log options: += PID,HOST,USERID,EXIT,DURATION,ATTEMPT and RECORD), rpc_version, rpc_number, env, passenv, redirect, bind, interface, banner, banner_success, banner_fail, per_source, cps, max_load, groups, enabled, include, includedir, rlimit_as, rlimit_cpu, rlimit_data, rlimit_rss, rlimit_stack.
The best source of information is the man page and its many examples. - assignment-operator:
- =
- +=: add a value to the set of values
- -=: delete a value from the set of values
Then restart the daemon: /etc/rc.d/init.d/xinetd restart
Example from man page: Limit telnet sessions to 8 Mbytes of memory and a total 20 CPU seconds for child processes.
service telnet { socket_type = stream wait = no nice = 10 user = root server = /usr/etc/in.telnetd rlimit_as = 8M rlimit_cpu = 20 }
|
[Pitfall] Red Hat 7.1 with updates as of 07/06/2001 required that I restart the xinetd services before FTP would work properly even though xinetd had started without failure during the boot sequence. I have no explanation as to why this occurs or how to fix it other than to restart xinetd: /etc/rc.d/init.d/xinetd restart.
Man Pages:
For more info see:
Pluggable Authentication Modules for Linux (TCP Wrappers)
This system allows or denies network access. One can reject or allow specific IP addresses or subnets to access your system.
File: /etc/hosts.allow
in.ftpd:208.188.34.105
This specifically allows the given IP address to ftp to your system. One can also specify an entire domain. i.e. .name-of-domain.com
Note the beginning ".".
File: /etc/hosts.deny
ALL:ALL
This generally denies any access.
See the pam man page.
File: /etc/inetd.conf
ftp stream tcp nowait root /usr/sbin/tcpd in.ftpd -l -a
|
The inet daemon accepts the incoming network stream and assigns it to the PAM TCP wrapper, /usr/sbin/tcpd, which accepts or denies the network connection as defined by /etc/hosts.allow and /etc/hosts.deny and then passes it along to ftp. This is logged to /var/log/secure
Advanced PAM: More specific access can be assigned and controlled by controlling the level of authentication required for access.
Files reflect the inet service name. Rules and modules are stacked to achieve the level of security desired.
See the files in /etc/pam.d/... (some systems use /etc/pam.conf)
The format: service type control module-path module-arguments
- auth - (type) Password is required for the user
- nullok - Null or non-existatant password is acceptable
- shadow - encrypted passwords kept in /etc/shadow
- account - (type) Verifies password. Can track and force password changes.
- password - (type) Controls password update
- retry=3 - Sets the number of login attempts
- minlen=8 - Set minimum length of password
- session - (type) Controls monitoring
Modules:
- /lib/security/pam_pwdb.so - password database module
- /lib/security/pam_shells.so -
- /lib/security/pam_cracklib.so - checks is password is crackable
- /lib/security/pam_listfile.so
After re-configuration, restart the inet daemon: killall -HUP inetd
For more info see:
| Network Monitoring Tools: |
- tcpdump - dump traffic on a network. See discussion below.
| Command line option | Description |
|---|
| -c | Exit after receiving count packets. |
| -C | Specify size of output dump files. |
| -i | Specify interface if multiple exist. Lowest used by default. i.e. eth0 |
| -w file-name | Write the raw packets to file rather than parsing and printing them out. They can later be printed with the -r option. |
| -n | Improve speed by not performing DNS lookups. Report IP addresses. |
| -t | Don't print a timestamp on each dump line. |
Filter expressions: | primitive | Description |
|---|
| host host-name | If host has multiple IP's, all will be checked. |
| net network-number | Network number. |
| net network-number mask mask | Network number and netmask specified. |
| port port-number | Port number specified. |
| tcp | Sniff TCP packets. |
| udp | Sniff UDP packets. |
| icmp | Sniff icmp packets. |
Examples:
- tcpdump tcp port 80 and host server-1
- tcpdump ip host server-1 and not server-2
- iptraf - Interactive Colorful IP LAN Monitor
- nmap - Network exploration tool and security scanner
- List pingable nodes on network: nmap -sP 192.168.0.0/24
Scans network for IP addresses 192.168.0.0 to 192.168.0.255 using ping.
- Ethereal - Network protocol analyzer. Examine data from a live network.
- RPM's required:
- ethereal-0.8.15-2.i386.rpm - Red Hat 7.1 Powertools CD RPM
- ucd-snmp-4.2-12.i386.rpm - Red Hat 7.1 binary CD 1
- ucd-snmp-utils-4.2-12.i386.rpm - Red Hat 7.1 binary CD 1
- Also: gtk+, glib, glibc, XFree86-libs-4.0.3-5 (base install)
There is an error in the ethereal package because it does not show the snmp libraries as a dependancies, but you can deduce this from the errors that you get if the ucd-snmp libraries are not installed.
- EtherApe - Graphical network monitor for Unix modeled after etherman. This is a great network discovery program with cool graphics. (Red Hat Powertools CD 7.1)
- Gkrellm - Network and system monitor. Good for monitoring your workstation. (Red Hat Powertools CD)
- IPTraf - ncurses-based IP LAN monitor. (Red Hat Powertools CD)
- Cheops - Network discovery, location, diagnosis and management. Cheops can identify all of the computers that are on your network, their IP address, their DNS name, the operating system they are running. Cheops can run a port scan on any system on your network. (Red Hat Powertools CD)
- ntop - Shows network usage in a way similar to what top does for processes. Monitors how much data is being sent and received on your network. (Red Hat Powertools CD)
- MRTG - Multi Router Traffic Grapher - Monitor network traffic load using SNMP and generate an HTML/GIF report. (See sample output)
- dnsad - IP traffic capture. Export to Cisco Netflow for network analysis reporting.
- scotty - Obtain status and configuration information about your network. Supports SNMP, ICMP, DNS, HTTP, SUN RPC, NTP, & UDP. (Red Hat Powertools CD)
- Big Brother - Monitoring ans services availablility.
- OpenNMS.org - Network Management using SNMP.
- Nagios - host, service and network monitoring
- Angel network monitor
Using tcpdump to monitor the network:
[root]# ifconfig eth0 promisc - Put nic into promiscuous mode to sniff traffic.
[root]# tcpdump -n host not XXX.XXX.XXX.XXX | more - Sniff net but ignore IP which is your remote session.
[root]# ifconfig eth0 -promisc - Pull nic out of promiscuous mode.
| Network Intrusion and Hacker Detection Systems: |
SNORT: Monitor the network, performing real-time traffic analysis and packet logging on IP networks for the detection of an attack or probe.
| ARP: Address Resolution Protocol |
Ethernet hosts use the Address Resolution Protocol (ARP) to convert a 32-bit internet IP addresses into a 48-bit Ethernet MAC address used by network hardware. (See: RFC 826) ARP broadcasts are sent to all hosts on the subnet by the data transmitting host to see who replies. The broadcast is ignored by all except the intended receiver which recognizes the IP address as its own. The MAC addresses are remembered (APR cache) for future network communications. Computers on the subnet typically keep a cache of ARP responses. ARP broadcasts are passed on by hubs and switches but are blocked by routers.
Reverse ARP (See: RFC 903) is a bootstrap protocol which allows a client to broadcast requesting a server to reply with its IP address.
- arp (8) man page - manipulate the system ARP cache
- Shows other systems on your network (including IP address conflicts): arp -a
- Show ARP table Linux style: arp -e
- arpwatch (8) man page - keep track of ethernet/ip address pairings
- arpsnmp (8) man page - keep track of ethernet/ip address pairings. Reads information generated by snmpwalk
- arping (8) man page - send ARP REQUEST to a neighbor host
Print ARP reply (similar to arp -a): arping 192.168.10.99 - List ARP table: cat /proc/net/arp
- ip (8) man page - show / manipulate routing, devices, policy routing and tunnels
View ARP table: ip neighbor
ARP is something that simply works. No Linux system configuration is necessary. It's all part of the ethernet and IP protocol. The aforementioned information is just part of the Linux culture of full visibility into what is going on.
| Configuring Linux For Network Multicast: |
Regular network exchanges of data are peer to peer unicast transactions. An HTTP request to a web server (TCP/IP), email SNMP (TCP/IP), DNS (UDP), FTP (TCP/IP), ... are all peer to peer unicast transactions. If one wants to transmit a video, audio or data stream to multiple nodes with one transmission stream instead of multiple individual peer to peer connections, one for each node, one may use multicasting to reduce network load. Note that multicast and a network broadcast are different. Multicast messages are only "heard" by the nodes on the network that have "joined the multicast group" which are those that are interested in the information.
The Linux kernel is Level-2 Multicast-Compliant. It meets all requirements to send, receive and act as a router for multicast datagrams. For a process to receive multicast datagrams it has to request the kernel to join the multicast group and bind the port receiving the datagrams. When a process is no longer interested in the multicast group, a request is made to the kernel to leave the group. It is the kernel/host which joins the multicast group and not the process. Kernel configuration requires "CONFIG_IP_MULTICAST=y". In order for the Linux kernel to support multicast routing, set the following in the kernel config:
- CONFIG_IP_MULTICAST=y
- CONFIG_IP_ROUTER=y
- CONFIG_IP_MROUTE=y
- CONFIG_NET_IPIP=y
The default Red Hat / Fedora kernels are compiled to support multicast.
See the YoLinux tutorial on optimization and rebuilding the Linux kernal.
Note that on multihomed systems (more than one IP address/network card), only one device can be configured to handle multicast.
Class D networks with a range of IP addresses from 224.0.0.0 to 239.255.255.255 (See Network Classes above) have typically been reserved for multicast.
Usefull commands:
| Command | Description |
|---|
| cat /proc/net/igmp | List multicast group to which the host is subscribed. Use "Internet Group Management Protocol". (See /usr/src/linux/net/core/igmp.c) |
| cat /proc/net/dev_mcast | List multicast interfaces. (See /usr/src/linux/net/core/dev_mcast.c) |
| ping 224.0.0.1 | All hosts configured for multicast will respond with their IP addresses |
| ping 224.0.0.2 | All routers configured for multicast will respond |
| ping 224.0.0.3 | All PIM routers configured for multicast will respond |
| ping 224.0.0.4 | All DVMRP routers configured for multicast will respond |
| ping 224.0.0.5 | All OSPF routers configured for multicast will respond |
Multicast transmissions are achieved through proper routing, router configuration (if communicating through subnets) and programatically with the use of the following "C" function library calls:
| Function Call | Description |
|---|
| setsockopt() | Pass information to the Kernel. |
| getsockopt() | Retrieve information broadcast using multicast. |
For more on multicast programming see: Multicast Howto. The multicast application will specify the multicast loopback interface, TTL (network time to live), network interface and the multicast group to add or drop.
Add route to support multicast:
- route add 224.0.0.0 netmask 240.0.0.0 dev eth0
Note that if adding a route to forward packets through a router, that the router MUST be configured to forward multicast packets. Many routers do not support forwarding of multicast packets or have a default configuration which does not. The internet by default does not forward multicast packets.
| Living in a MS/Windows World: |
See the YoLinux tutorial on integrating Linux into a Microsoft network.
- IPv4: Most of the Internet servers and personal computers use Internet Protocol version 4 (IPv4). This uses 32 bits to assign a network address as defined by the four octets of an IP address up to 255.255.255.255. Which is the representation of four 8 bit numbers thus totaling 32 bits.
- IPv6: Internet Protocol version 6 (IPv6) uses a 128 bit address and thus billions and billions of potential addresses. The protocol has also been upgraded to include new quality of service features and security. Currently Linux supports IPv6 but IPv4 is used when connecting your computer to the internet.
- TCP/IP: (Transmission Control Protocol/Internet Protocol) uses a client - server model for communications. The protocol defines the data packets transmitted (packet header, data section), data integrity verification (error detection bytes), connection and acknowledgement protocol, and re-transmission.
- TCP/IP time to live (TTL): This is a counting mechanism to determine how long a packet is valid before it reaches its destination. Each time a TCP/IP packet passes through a router it will decrement its TTL count. When the count reaches zero the packet is dropped by the router. This ensures that errant routing and looping aimless packets will not flood the network.
- MAC Address: (media access control) is the network card address used for communication between other network devices on the subnet. This info is not routable. The ARP table maps TCP/IP address (global internet) to the local hardware on the local network. Use the command /sbin/ifconfig to view both the IP address and the MAC address. The MAC address uniquely identifies each node of a network and is used by the Ethernet protocol.
- Full Duplex: Allows the simultaneous sending and receiving of packets. Most modern modems support full duplex.
- Half Duplex: Allows the sending and receiving of packets in one direction at a time only.
- OSI 7 Layer Model: The ISO (International Standards Organization) has defined the OSI (Open Systems Interconnection) model for current networking protocols.
| OSI Layer | Description | Linux Networking Use |
|---|
| 7 | Application Layer. The top layer for communications applications like email and the web. | telnet, web browser, sendmail |
| 6 | Presentation Layer. Syntax and format of data transfer. | SMTP, http |
| 5 | Session Layer. |
|
| 4 | Transport Layer. Connection, acknowledgement and data packet transmission. | TCP UDP |
| 3 | Network Layer. | IP ARP |
| 2 | Data Link Layer. Error control, timing | Ethernet |
| 1 | Physical Layer. Electrical characteristics of signal and NIC | Ethernet |
- Network Hub: Hardware to connect network devices together. The devices will all be on the same network and/or subnet. All network traffic is shared and can be sniffed by any other node connected to the same hub.
- Network Switch: Like a hub but creates a private link between any two connected nodes when a network connection is established. This reduces the amount of network collisions and thus improves speed. Broadcast messages are still sent to all nodes.