5
Routing
94
Example 1: Displaying the main routing table
This
example
illustrates
how
to
display
the
contents
of
the
default
main
routing
table.
To
display
the
configured
routing
table,
enter:
Device:/>
cc
RoutingTable
main
Device:/RoutingTable/main>
show
Route
#
Interface
Network
Gateway
Local
IP
‐ ‐‐‐‐‐‐‐‐‐ ‐‐‐‐‐‐‐‐ ‐‐‐‐‐‐‐‐‐‐‐‐‐ ‐‐‐‐‐‐‐‐
1
wan
all
‐
nets
213.124.165.1
(none)
2
sfp1
sfp1net
(none)
(none)
3
wan
wannet
(none)
(none)
To
display
the
active
routing
table,
enter:
Device:/>
routes
Routing
table:
main
Flags
Network
Iface
Gateway
Local
IP
Metric
‐‐‐‐‐ ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ ‐‐‐‐‐‐‐ ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ ‐‐‐‐‐‐‐‐ ‐‐‐‐‐‐
192.168.0.0/24
sfp1
0
213.124.165.0/24
wan
0
0.0.0.0/0
wan
213.124.165.1
0
Tip:
In
the
CLI
example
above,
it
was
necessary
to
first
select
the
name
of
a
specific
routing
table
with
the
cc
command
(meaning
change
category
or
change
context
)
before
manipulating
individual
routes.
This
is
necessary
for
any
category
that
could
contain
more
than
one
named
group
of
objects.
all-nets route
The
most
important
route
that
should
be
defined
is
the
route
to
all
‐
nets
,
which
usually
corresponds
to
your
ISP
for
public
Internet
access.
Throughout
this
manual,
the
all
‐
nets
‐
ip4
address
object
is
used
in
most
cases,
which
is
a
subset
of
all
‐
nets
.
Core routes
The
SEG
automatically
populates
the
active
routing
table
with
Core
Routes
.
These
routes
are
present
for
the
system
to
understand
where
to
route
traffic
that
is
destined
for
the
system
itself.
There
is
one
route
added
for
each
interface
in
the
system.
For
example,
two
interfaces
named
sfp1
and
wan
,
with
IPv4
addresses
192.168.0.10
and
193.55.66.77
,
respectively,
will
result
in
the
following
routes:
Route
Interface
Destination
Gateway
1 core
192.168.0.10
2 core
193.55.66.77
