relay - network interfaces..

[Shane Kerr]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

foomail123 wrote:
> Hi,
> 
> 
> I see:
> 
> 
>  File     Line
> 0 bpf.c     532 void maybe_setup_fallback ()
> 1 dlpi.c   1321 void maybe_setup_fallback ()
> 2 lpf.c     395 void maybe_setup_fallback ()
> 3 nit.c     405 void maybe_setup_fallback ()
> 4 socket.c  347 void maybe_setup_fallback ()
> 5 upf.c     356 void maybe_setup_fallback ()
> 6 bpf.c     532 void maybe_setup_fallback ()
> 7 dlpi.c   1321 void maybe_setup_fallback ()
> 8 lpf.c     395 void maybe_setup_fallback ()
> 9 nit.c     405 void maybe_setup_fallback ()
> a socket.c  347 void maybe_setup_fallback ()
> b upf.c     356 void maybe_setup_fallback ()
> 
> 
> Which one do I use ?
> I see site.h has definitions ?
> Is it right locations ?

Because DHCP works on systems that don't have active IP addresses, the interface
code tends to be different for each OS. So it depends on the operating system
you are using. Linux usually uses lpf, *BSD usually uses bpf, Solaris usually
uses dlpi, and so on. Which on is used is defined in the header files in the
includes/cf directory.

If you don't feel like reading the code, you can grep the object files after
compiling. So on a Linux box:

$ cd work.linux-2.2/common
$ grep maybe_setup_fallback *.o
Binary file discover.o matches
Binary file lpf.o matches

We see that DHCP is indeed using lpf on Linux.

> Does using socket above work ? I see some routines
> are stubbed out.

I don't understand the question. What is it you think might not be working?

- --
Shane
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEzcJVMsfZxBO4kbQRApBZAKDLaxdB5gEkrY87HmdZQrwPqPMQ0wCeLnKA
aCdcgRNWPnDJWs6KZUZLUMc=
=vSB/
-----END PGP SIGNATURE-----