URL
https://opencores.org/ocsvn/or1k/or1k/trunk
Details |
Compare with Previous |
View Log
Line No. |
Rev |
Author |
Line |
1 |
199 |
simons |
The IPX support in the Linux kernel has two modes of operation:
|
2 |
|
|
With and without the full internal IPX network. For all normal
|
3 |
|
|
operations, you do not need the full internal IPX network.
|
4 |
|
|
|
5 |
|
|
The full internal IPX network enables you to allocate sockets on
|
6 |
|
|
different virtual nodes of the internal network. This is done by
|
7 |
|
|
evaluating the field sipx_node of the socket address given to the bind
|
8 |
|
|
call. So applications should always initialize the node field to 0
|
9 |
|
|
when binding a socket on the primary network. In this case the socket
|
10 |
|
|
is assigned the default node that has been given to the kernel when
|
11 |
|
|
the internal network was created.
|
12 |
|
|
By enabling the full internal IPX network the cross-forwarding of
|
13 |
|
|
packets targeted at 'special' sockets to sockets listening on the
|
14 |
|
|
primary network is disabled. This might break existing applications,
|
15 |
|
|
especially RIP/SAP daemons. A RIP/SAP daemon that works well with
|
16 |
|
|
the full internal net can be found on ftp.gwdg.de:/pub/linux/misc/ncpfs.
|
17 |
|
|
|
18 |
|
|
If you want the full internal network, please uncomment the correspondig
|
19 |
|
|
#define in line 19 of include/net/ipx.h
|
© copyright 1999-2024
OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.