You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nuttx.apache.org by GitBox <gi...@apache.org> on 2021/11/17 06:08:59 UTC

[GitHub] [incubator-nuttx] SPRESENSE opened a new issue #4845: Network address was changed unexpectedly

SPRESENSE opened a new issue #4845:
URL: https://github.com/apache/incubator-nuttx/issues/4845


   When connecting to a network with a device such as gs2200m (eth0),
   if you try to change the address of the appropriate interface device name (e.g., hoge0) in ifconfig,
   the network address of eth0 will be changed.
   
   Is this behavior correct?
   ![ifconfig](https://user-images.githubusercontent.com/41312067/142144069-459688f4-c6b1-439d-aa15-f5fe164fd632.png)
   
   Thank you very much in advance.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [incubator-nuttx] gustavonihei edited a comment on issue #4845: Network address was changed unexpectedly

Posted by GitBox <gi...@apache.org>.
gustavonihei edited a comment on issue #4845:
URL: https://github.com/apache/incubator-nuttx/issues/4845#issuecomment-999006384


   This might be related to the usage of USRSOCK component.
   
   `netlib` does not perform any validation on the interface name before requesting the IP change to the network stack.
   https://github.com/apache/incubator-nuttx-apps/blob/master/netutils/netlib/netlib_setipv4addr.c#L66
   
   When USRSOCK is enabled, the NuttX netstack is bypassed and the handling of the `SIOCSIFADDR` ioctl command is delegated to the USRSOCK daemon, which in this case is `gs2200md`.
   So, in the current state, it is up to the device driver connected via USRSOCK to do the right processing, similar to what `netdev` does:
   https://github.com/apache/incubator-nuttx/blob/master/net/netdev/netdev_ioctl.c#L605-L617
   
   So, most probably the issue is that GS2200m is simply setting the IP regardless of the interface name being set:
   https://github.com/apache/incubator-nuttx/blob/master/drivers/wireless/gs2200m.c#L2857-L2861


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [incubator-nuttx] gustavonihei commented on issue #4845: Network address was changed unexpectedly

Posted by GitBox <gi...@apache.org>.
gustavonihei commented on issue #4845:
URL: https://github.com/apache/incubator-nuttx/issues/4845#issuecomment-999006384


   This might be related to the usage of USRSOCK component.
   
   `netlib` does not perform any validation on the interface name before requesting the IP change to the network stack.
   https://github.com/apache/incubator-nuttx-apps/blob/master/netutils/netlib/netlib_setipv4addr.c#L66
   
   When USRSOCK is enabled, the NuttX netstack is bypassed and the handling of the `SIOCSIFADDR` ioctl command is delegated to the USRSOCK daemon, which in this case is `gs2200md`.
   So, in the current state, it is up to the device driver connected via USRSOCK to do the right processing, similar to what `netdev` does:
   https://github.com/apache/incubator-nuttx/blob/master/net/netdev/netdev_ioctl.c#L605-L617
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [incubator-nuttx] acassis commented on issue #4845: Network address was changed unexpectedly

Posted by GitBox <gi...@apache.org>.
acassis commented on issue #4845:
URL: https://github.com/apache/incubator-nuttx/issues/4845#issuecomment-971486335


   No, it is not a feature, it is a bug! :-D


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [incubator-nuttx] gustavonihei edited a comment on issue #4845: Network address was changed unexpectedly

Posted by GitBox <gi...@apache.org>.
gustavonihei edited a comment on issue #4845:
URL: https://github.com/apache/incubator-nuttx/issues/4845#issuecomment-999006384


   This might be related to the usage of USRSOCK component.
   
   `netlib` does not perform any validation on the interface name before requesting the IP change to the network stack.
   https://github.com/apache/incubator-nuttx-apps/blob/master/netutils/netlib/netlib_setipv4addr.c#L66
   
   When USRSOCK is enabled, the NuttX netstack is bypassed and the handling of the `SIOCSIFADDR` ioctl command is delegated to the USRSOCK daemon, which in this case is `gs2200m`.
   So, in the current state, it is up to the device driver connected via USRSOCK to do the right processing, similar to what `netdev` does:
   https://github.com/apache/incubator-nuttx/blob/master/net/netdev/netdev_ioctl.c#L605-L617
   
   So, most probably the issue is that GS2200m is simply setting the IP regardless of the interface name being set:
   https://github.com/apache/incubator-nuttx/blob/master/drivers/wireless/gs2200m.c#L2857-L2861


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org