Hi,
I don't think the more complex scenario of Router/Host has been discussed.
If so, please provide a pointer.
Consider a system where SERVER wants to have a shortcut into LAN1 (but not
forward traffic from it):
LAN0 --- eth0 SERVER tun1 - - - ROUTER ----> Internet
eth1 |
| |
LAN1 --------------^
(this is a scenario where server acts as a router for LAN0, and uses
LAN1 to e.g. mount NFS shares off a server there ("nfs interface"))
Now, this would appear to be rather problematic. Some items for a router
include among others setting IsRouter flag in NA's and responding to RS's.
These seem to be usually implemented as global toggles; either the system
is a router or it is not.
This creates problems in the above scenario because:
- SERVER should act as a router toward eth0 and tun1
- SERVER MUST NOT be used to forward traffic from LAN1.
* IsRouter flag off
* Not answering to RS's
* Etc.
* Whether this should be able to accept RA's (to autoconfigure the
prefix, but not otherwise modify the routing table) is open to discussion;
on a "primarily" router, it would probably be acceptable to having to
configure it manually.
Has these kind of "mixed" scenarios been thought of? I'm sure this is not
the only one...
--
Pekka Savola "Tell me of difficulties surmounted,
Netcore Oy not those you stumble over and fall"
Systems. Networks. Security. -- Robert Jordan: A Crown of Swords
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
