05-08-2001
RIP is not necessary and does not provide any useful functionality in your topology, IMHO; and you would 'learn more' by building the correct static routing tables, setting up default routes, etc.
If you still want to experiment, would recommend you experiment with something more useful than RIP. A freeware version of OSPF would be more instructive because there are more metrics (5, as I recall) in OSPF, in RIP(v1) there are only hop counts.
3 More Discussions You Might Find Interesting
1. IP Networking
I am trying to set up a linux box as a router, but I am a little confused
on how to do this. I am using Red Hat 9.0 on a machine that has 2
nic cards. Also, I am using a DSL pppoe connection. I have installed
rp-pppoe and I am connected to the internet via the pseudo pppoe
interface. I have... (1 Reply)
Discussion started by: cstovall
1 Replies
2. Solaris
hi guys,
its been a while since my last visit here,
could not keep up the pace on this ever changing industry :)
i'd just doing my home research under vmware to make a solaris-based router-firewall using zones - doing a lot of reading about zones & review solaris zone functionality.
and... (4 Replies)
Discussion started by: stdout
4 Replies
3. News, Links, Events and Announcements
A new project was posted on your project board.
Project title: Bash Shell Tutoring
Estimated Budget:
$50/hr
Start date:
Immediately
Required skills:
Linux, Bash, Shell, UNIX
I work as a datawarehouse designer and developer.
Although I usually stick to the role of an analyst,... (0 Replies)
Discussion started by: Neo
0 Replies
LEARN ABOUT X11R4
ip-token
IP-TOKEN(8) Linux IP-TOKEN(8)
NAME
ip-token - tokenized interface identifier support
SYNOPSIS
ip token { COMMAND | help }
ip token set TOKEN dev DEV
ip token del dev DEV
ip token get [ dev DEV ]
ip token [ list ]
DESCRIPTION
IPv6 tokenized interface identifier support is used for assigning well-known host-part addresses to nodes whilst still obtaining a global
network prefix from Router advertisements. The primary target for tokenized identifiers are server platforms where addresses are usually
manually configured, rather than using DHCPv6 or SLAAC. By using tokenized identifiers, hosts can still determine their network prefix by
use of SLAAC, but more readily be automatically renumbered should their network prefix change [1]. Tokenized IPv6 Identifiers are described
in the draft [1]: <draft-chown-6man-tokenised-ipv6-identifiers-02>.
ip token set - set an interface token
set the interface token to the kernel.
TOKEN the interface identifier token address.
dev DEV
the networking interface.
ip token del - delete an interface token
delete the interface token from the kernel.
dev DEV
the networking interface.
ip token get - get the interface token from the kernel
show a tokenized interface identifier of a particular networking device. Arguments: coincide with the arguments of ip token set but the
TOKEN must be left out.
ip token list - list all interface tokens
list all tokenized interface identifiers for the networking interfaces from the kernel.
SEE ALSO
ip(8)
AUTHOR
Manpage by Daniel Borkmann
iproute2 28 Mar 2013 IP-TOKEN(8)