About Zebra Error

About Zebra Error

[Aubrey Lee]

 hi, In the PC(i686) system, I build and run zebra successfully. And now
I'm porting it to the powerpc system. Cross-compiling finished without error.
But when I run the zebra from my target board, it gives me  a big headache:
--------------------------------------------------------------------------  
bash-2.05b# /opt/zebra/sbin/zebra
             sock: Address family not supported by protocol
----------------------------------------------------------------------------
And Up to now I cann't find the message in the souce 
code files.  
     The two ethx and their driver of my board is OK.
     What shall I do?
     Any comment and suggestion will be welcome!
     Thank you very much!
      Best regards!
          Aubrey.Lee

Re: About Zebra Error

[Eugene Surovegin]

On Thu, Jan 13, 2005 at 04:50:27PM +0800, Aubrey Lee wrote:
>  hi, In the PC(i686) system, I build and run zebra successfully. And now
> I'm porting it to the powerpc system. Cross-compiling finished without error.
> But when I run the zebra from my target board, it gives me  a big headache:
> --------------------------------------------------------------------------  
> bash-2.05b# /opt/zebra/sbin/zebra
>              sock: Address family not supported by protocol
> ----------------------------------------------------------------------------
> And Up to now I cann't find the message in the souce 
> code files.  
>      The two ethx and their driver of my board is OK.
>      What shall I do?

Most probably zebra needs some some socket family (e.g. PF_PACKET) 
which wasn't enabled in your PPC kernel.

Compare .config files for x86 and PPC kernels, especially networking 
configuration parts.

The reason you cannot find "Address family not supported by protocol" 
message in the zebra sources is because this message comes from libc, 
e.g. by using perror(3) or sys_errlist directly.

--
Eugene

Re: About Zebra Error

[Mark Powell]

Aubrey Lee wrote:

> hi, In the PC(i686) system, I build and run zebra successfully. And now
>I'm porting it to the powerpc system. Cross-compiling finished without error.
>But when I run the zebra from my target board, it gives me  a big headache:
>--------------------------------------------------------------------------  
>bash-2.05b# /opt/zebra/sbin/zebra
>             sock: Address family not supported by protocol
>----------------------------------------------------------------------------
>And Up to now I cann't find the message in the souce 
>code files.  
>     The two ethx and their driver of my board is OK.
>     What shall I do?
>  
>
I had a similar message when running udhcpd. The problem was that some 
network drivers were built as modules. Adding the following to 
modules.conf cured my problem:

    # PF_PACKET support needed by udhcpc
    alias net-pf-17 af_packet

-- 
Mark Powell, Senior Software Engineer
Curtiss-Wright Controls Embedded Computing
Tel: +44 (0) 1763 852222
Email: medp@primagraphics.com

About zebra Error

[Aubrey Lee]

    Hi, now I know what the problem is.
    For my case, the ppc-linux kernel should be configured as the following:
    The Item [Unix domain Socket]  should be selected [Y]
    Just so so.

Re: About Zebra Error

[Tolunay Orkun]

Aubrey Lee wrote:
>  hi, In the PC(i686) system, I build and run zebra successfully. And now
> I'm porting it to the powerpc system. Cross-compiling finished without error.
> But when I run the zebra from my target board, it gives me  a big headache:
> --------------------------------------------------------------------------  
> bash-2.05b# /opt/zebra/sbin/zebra
>              sock: Address family not supported by protocol
> ----------------------------------------------------------------------------
> And Up to now I cann't find the message in the souce 
> code files.  

You are probably missing the particular socket type Zebra is trying to 
use. I had a similar experience while trying to use DHCP in busybox on 
by PPC405 embedded system. Go over your kernel configuration and ask a 
Zebra mailing list regarding the socket support it needs.