Network security and bind IP in MongoDB - Step-by-Step Execution

Concept Flow - Network security and bind IP

Start MongoDB Server

↓

Read config file

↓

Check bindIp setting

↓

bindIp = 127.0.0.1?

Yes→Listen only on localhost

↓

Restrict external access

↓

bindIp includes external IP?

Yes→Listen on specified IPs

↓

Allow remote connections

↓

No bindIp set?

→Default to 127.0.0.1

↓

Start listening on allowed IPs

↓

Accept or reject connections based on IP and firewall

MongoDB reads the bindIp setting to decide which IP addresses it listens on, controlling network access for security.

Execution Sample

MongoDB

net:
  bindIp: 127.0.0.1,192.168.1.100

This config makes MongoDB listen on localhost and a local network IP, allowing local and specific remote access.

Execution Table

Step	Action	bindIp Value	Listening IPs	Security Effect
1	Start MongoDB server	Not read yet	None	No listening yet
2	Read config file	127.0.0.1,192.168.1.100	None	Config loaded
3	Check bindIp setting	127.0.0.1,192.168.1.100	None	Evaluating IPs
4	Set listening IPs	127.0.0.1,192.168.1.100	127.0.0.1, 192.168.1.100	Listening on localhost and LAN IP
5	Start listening	127.0.0.1,192.168.1.100	127.0.0.1, 192.168.1.100	Accept connections from these IPs
6	Connections from other IPs	127.0.0.1,192.168.1.100	127.0.0.1, 192.168.1.100	Rejected - not in bindIp list

💡 MongoDB listens only on IPs listed in bindIp, blocking others for security.

Variable Tracker

Variable	Start	After Step 2	After Step 4	Final
bindIp	undefined	127.0.0.1,192.168.1.100	127.0.0.1,192.168.1.100	127.0.0.1,192.168.1.100
Listening IPs	none	none	127.0.0.1,192.168.1.100	127.0.0.1,192.168.1.100

Key Moments - 3 Insights

Why does MongoDB only accept connections from certain IPs?

Because the bindIp setting limits listening to specified IP addresses, as shown in execution_table step 6 where connections from other IPs are rejected.

What happens if bindIp is not set in the config?

MongoDB defaults to listening only on 127.0.0.1 (localhost), restricting access to the local machine for security.

Can MongoDB listen on multiple IP addresses?

Yes, bindIp can list multiple IPs separated by commas, allowing MongoDB to listen on all those addresses, as shown in step 4.

Visual Quiz - 3 Questions

Look at the execution_table, what IPs is MongoDB listening on after step 4?

A 127.0.0.1 and 192.168.1.100

B All IPs on the network

C Only 127.0.0.1

D No IPs yet

💡 Hint

Check the 'Listening IPs' column at step 4 in the execution_table.

At which step does MongoDB start rejecting connections from IPs not in bindIp?

A Step 4

B Step 6

C Step 2

D Step 1

💡 Hint

Look at the 'Security Effect' column in execution_table step 6.

If bindIp was set only to 127.0.0.1, what would change in the variable_tracker for Listening IPs?

A Listening IPs would be empty

B Listening IPs would include 192.168.1.100

C Listening IPs would be 127.0.0.1 only

D Listening IPs would include all IPs

💡 Hint

Refer to the 'bindIp' and 'Listening IPs' rows in variable_tracker.

Concept Snapshot

MongoDB bindIp controls which IP addresses the server listens on.
Set bindIp in config file under net section.
Example: bindIp: 127.0.0.1,192.168.1.100
Only listed IPs can connect; others are blocked.
Default is 127.0.0.1 if not set.
This setting improves network security by limiting access.

Full Transcript

When MongoDB starts, it reads the bindIp setting from its configuration file. This setting tells MongoDB which IP addresses it should listen on for incoming connections. If bindIp is set to 127.0.0.1, MongoDB listens only on the local machine, blocking remote access. If bindIp includes other IPs, like a local network IP, MongoDB listens on those too, allowing connections from those addresses. If bindIp is not set, MongoDB defaults to 127.0.0.1 for security. This helps protect the database by restricting network access to trusted IPs only.