Experimental Physics and
Industrial Control System

Vladis Korobov <[email protected]> · Thu, 14 Jun 2001 10:47:25 +0200 (MEST)

On Tue, 12 Jun 2001, Andrew Johnson wrote:

> Jeff Hill wrote:
> >
> > If "ifShow()" on the slave does not list the ei interface then
> > you must call eiattach() to install the network interface
> > into the IP kernel. Next, call ifAddrAdd() to set the
> > interface's IP address. Next, call routeShow() to verify
> > that a route was installed for the new interface. If insufficient,
> > then call routeAdd() to specify the range of addresses that will
> > be delivered to the 2nd Ethernet.
>
> Note that ifAddrAdd() is a vxWorks 5.4 call, on 5.3 you have to use
> ifMaskSet() and ifAddrSet() individually and in that order.  You won't
> need to call ifMaskSet() if the subnet mask for this segment is the same
> as the netmask for the class of IP address that you're giving the
> interface.
>

eiattach() routine needs 5 arguments like interrupt vector, sysbus (?)
etc. One need to know what they mean in details. But I used
usrNetIfAttach(), which I found in usrNetwork.c module from
VxWorks sources. This call needs only two arguments: interface name and
IP addres (in fact, the second argument is not used in the routine).
>From this routine appropriate attach routine is invoked with
predefined for each interface type arguments.
  All other calls I did as you recommended. After this I started
the communication task and saw that the new interface was used for
the data exchange. Thank you for your help.
  One more question. How does the system determine which interface
should be used. Or, may be, it uses for  new connections the last
attached interface. Is it true?

Thanks to all,
V.Korobov

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System