However, networking can be stop or started using special script located in /etc/rc.d/ directory. This directory includes script to stop or start network, and other services such as SSH server.
FreeBSD 5.x/6.x and above version – start or stop network service
FreeBSD 5.x/6.x and above version comes with netif script to start, restart, stop network service. You need to login as a root user. Then you can use following commands:
To start FreeBSD network service:
# /etc/rc.d/netif start
To stop FreeBSD network service:
# /etc/rc.d/netif stop
To restart FreeBSD network service:
# /etc/rc.d/netif restart
Manual method using ifconfig
To stop network card (NIC) on-fly:
# ifconfig network-interface down
To start network card (NIC) on fly:
# ifconfig network-interface up
To list down network interface:
# ifconfig -d
To list up network interface:
# ifconfig -u
FreeBSD Update / restart routing tables / service
It is also necessary to update routing table after restating networking service, enter:
# /etc/rc.d/routing restart
How do I restart network service over ssh session?
You need to type the commands as follows in order to avoid problems:
# /etc/rc.d/netif restart && /etc/rc.d/routing restart
FreeBSD 4.x and prior version only – start, restart, stop network service
To start network service under FreeBSD you need to copy special script as follows:
# cp /usr/share/examples/etc/netstart /etc/network
Execute this script:
. /etc/network
OR
sh /etc/network
Please note that script will do all necessary work for you i.e. it will start network, routing, firewall etc.
🐧 7 comments so far... add one ↓
| Category | List of Unix and Linux commands |
|---|---|
| File Management | cat |
| Firewall | Alpine Awall • CentOS 8 • OpenSUSE • RHEL 8 • Ubuntu 16.04 • Ubuntu 18.04 • Ubuntu 20.04 |
| Network Utilities | dig • host • ip • nmap |
| OpenVPN | CentOS 7 • CentOS 8 • Debian 10 • Debian 8/9 • Ubuntu 18.04 • Ubuntu 20.04 |
| Package Manager | apk • apt |
| Processes Management | bg • chroot • cron • disown • fg • jobs • killall • kill • pidof • pstree • pwdx • time |
| Searching | grep • whereis • which |
| User Information | groups • id • lastcomm • last • lid/libuser-lid • logname • members • users • whoami • who • w |
| WireGuard VPN | Alpine • CentOS 8 • Debian 10 • Firewall • Ubuntu 20.04 |









I wish the caveat note about running /etc/rc.d/routing restart immediately afterwards was near the note about /etc/rc.d/netif restart — I just took down my host remotely by not finding out that tidbit a little too late after it didn’t come up.
Appreciate the info. A little asterix ** note beside the first command of “routing restart” would have really saved my nightmare. (I was already in a panic to reboot my network interface, and didn’t get a chance to read through the entire document — it seemed easy and clear enough with the first command)
Hi!
Thank you for the easy to unterstand articles.
I try to use vlans. How can I ‘restart’ the virtual interface? The command /etc/rc.d/netif restart vlan5 not works for me.
Another vlan question: what about interfaces? Must have the external/real/physical interface an address?
Yes, you are right. It was typo on my part and the post has been updated.
I appreciate your feedback and post.
You need to type the commands as follows in order to avoid any problems:
# /etc/rc.d/networking restart && /etc/rc.d/routing restart
The right way is:
# /etc/rc.d/netif restart && /etc/rc.d/routing restart
I am right?
Thank you very mach 🙂
/etc/netstart is old method and does not support all the options (like stop, restart etc), which is now supported by /etc/rc.d/netif script. Ease of use is main difference between two.
Whats the difference between /etc/netstart and /etc/rc.d/netif for restarting networking?