Skip to content

Change from old route command to iproute2 command #50

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
+5 −7
Open

Change from old route command to iproute2 command #50

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 5 additions & 7 deletions onramp/network.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,9 +109,8 @@ successful:

.. code-block::

$ route -n | grep "Iface\|access"
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.252.0 0.0.0.0 255.255.255.0 U 0 0 0 access
$ ip ro|grep "dev access"
192.168.252.0/24 dev access proto kernel scope link src 192.168.252.1

Within the UPF, the correct behavior is to forward packets between the
``access`` and ``core`` interfaces. Upstream packets arriving on the
Expand Down Expand Up @@ -142,10 +141,9 @@ rules on the server:

.. code-block::

$ route -n | grep "Iface\|core"
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.100.0 192.168.250.3 255.255.0.0 UG 0 0 0 core
192.168.250.0 0.0.0.0 255.255.255.0 U 0 0 0 core
$ ip ro |grep "dev core"
192.168.100.0/24 via 192.168.250.3 dev core proto static
192.168.250.0/24 dev core proto kernel scope link src 192.168.250.1

The first rule above matches packets to the UEs on the
``192.168.100.0/24`` subnet. The next hop for these packets is the
Expand Down