[prev in list] [next in list] [prev in thread] [next in thread]
List: busybox
Subject: Re: [BusyBox] nameif
From: Jason Schoon <floydpink () gmail ! com>
Date: 2005-05-31 16:26:07
Message-ID: 78a54e1b05053109265d74b1bf () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Are you perhaps bring the device up before calling nameif on this platform?
That is a guaranteed way to make it fail.
Is there any way you can try a non-busybox version of nameif on this
particular platform to see how it behaves?
On 5/31/05, Miguel Ángel Álvarez Cabanes <ma.alvarez@usyscom.com> wrote:
>
> I have been using nameif in different embedded environments (PPC and
> 686) without problems.
>
> However, when trying to use it with an STPC Atlas (I think it is based
> on a 486) and kernel 2.6.10 (busybox 1.0.0), it allways breaks on:
>
> if (ioctl(ctl_sk, SIOCGIFNAME, &ifr))
> break;
>
> I am not quite sure about the causes of the problem, but I have solved
> it adding an option that allows to set the old name of the interface...
> (which I think it coulf be quite useful because you don't need to know
> the MAC of your device).
>
> I suppose that using this I could also eliminate the use of:
> /* Has this device hwaddr? */
> if (ioctl(ctl_sk, SIOCGIFHWADDR, &ifr))
> continue;
>
> but I have maintained it for compatibility.
>
> Has anybody experience the same problems with nameif?
>
> Thanks
>
> Miguel Ángel
>
> ----------------------------------------- PLEASE NOTE
> -------------------------------------------
> This message, along with any attachments, may be confidential or legally
> privileged.
> It is intended only for the named person(s), who is/are the only
> authorized recipients.
> If this message has reached you in error, kindly destroy it without review
> and notify the sender immediately.
> Thank you for your help.
> µSysCom uses virus scanning software but excludes any liability for
> viruses contained in any attachment.
>
> ------------------------------------ ROGAMOS LEA ESTE TEXTO
> -------------------------------
> Este mensaje y sus anexos pueden contener información confidencial y/o con
> derecho legal.
> Está dirigido únicamente a la/s persona/s o entidad/es reseñadas como
> único destinatario autorizado.
> Si este mensaje le hubiera llegado por error, por favor elimínelo sin
> revisarlo ni reenviarlo y notifíquelo inmediatamente al remitente. Gracias
> por su colaboración.
> µSysCom utiliza software antivirus, pero no se hace responsable de los
> virus contenidos en los ficheros anexos.
>
>
> _______________________________________________
> busybox mailing list
> busybox@mail.busybox.net
> http://codepoet.org/mailman/listinfo/busybox
>
>
>
>
[Attachment #5 (text/html)]
Are you perhaps bring the device up before calling nameif on this platform? \
That is a guaranteed way to make it fail.<br> <br>
Is there any way you can try a non-busybox version of nameif on this particular \
platform to see how it behaves?<br> <br>
<br><br><div><span class="gmail_quote">On 5/31/05, <b class="gmail_sendername">Miguel \
Ángel Álvarez Cabanes</b> <<a \
href="mailto:ma.alvarez@usyscom.com">ma.alvarez@usyscom.com</a>> \
wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, \
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> I have been using nameif \
in different embedded environments (PPC and<br>686) without problems.<br><br>However, \
when trying to use it with an STPC Atlas (I think it is based<br>on a 486) and kernel \
2.6.10 (busybox 1.0.0), it allways breaks on: <br><br>if (ioctl(ctl_sk, SIOCGIFNAME, \
&ifr))<br> break;<br><br>I am not \
quite sure about the causes of the problem, but I have solved<br>it adding an option \
that allows to set the old name of the interface...<br> (which I think it coulf be \
quite useful because you don't need to know<br>the MAC of your device).<br><br>I \
suppose that using this I could also eliminate the use of:<br>/* Has this device \
hwaddr? */<br>if (ioctl(ctl_sk, SIOCGIFHWADDR, &ifr)) \
<br> continue;<br><br>but I have \
maintained it for compatibility.<br><br>Has anybody experience the same problems with \
nameif?<br><br>Thanks<br><br>Miguel \
Ángel<br><br>----------------------------------------- PLEASE NOTE \
------------------------------------------- <br>This message, along with any \
attachments, may be confidential or legally privileged.<br>It is intended only for \
the named person(s), who is/are the only authorized recipients.<br>If this message \
has reached you in error, kindly destroy it without review and notify the sender \
immediately. <br>Thank you for your help.<br>µSysCom uses virus scanning software but \
excludes any liability for viruses contained in any \
attachment.<br><br>------------------------------------ ROGAMOS LEA ESTE TEXTO \
------------------------------- <br>Este mensaje y sus anexos pueden contener \
información confidencial y/o con derecho legal.<br>Está dirigido únicamente a la/s \
persona/s o entidad/es reseñadas como único destinatario autorizado.<br>Si este \
mensaje le hubiera llegado por error, por favor elimínelo sin revisarlo ni reenviarlo \
y notifíquelo inmediatamente al remitente. Gracias por su colaboración.<br>µSysCom \
utiliza software antivirus, pero no se hace responsable de los virus contenidos en \
los ficheros anexos.<br><br><br>_______________________________________________<br>busybox \
mailing list <br><a href="mailto:busybox@mail.busybox.net">busybox@mail.busybox.net</a> \
<br><a href="http://codepoet.org/mailman/listinfo/busybox">http://codepoet.org/mailman/listinfo/busybox</a><br><br><br><br></blockquote></div><br>
_______________________________________________
busybox mailing list
busybox@mail.busybox.net
http://codepoet.org/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic