Torbjørn Tvermosegaard | 26 Jan 14:56 2015
Picon

[bug #44092] tcp_pcb hangs in FIN_WAIT_1 after lwip_close call

URL:
  <http://savannah.nongnu.org/bugs/?44092>

                 Summary: tcp_pcb hangs in FIN_WAIT_1 after lwip_close call
                 Project: lwIP - A Lightweight TCP/IP stack
            Submitted by: tbt
            Submitted on: Mon Jan 26 13:56:10 2015
                Category: TCP
                Severity: 3 - Normal
              Item Group: Faulty Behaviour
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: 
            lwIP version: 1.4.0

    _______________________________________________________

Details:

On a socket connection to a PC through a switch it seems that the lwip does
not properly handle the situation, that the cable between switch and PC is
disconnected (this means that interface in lwip is still up). I have an
application that discovers the lack of communication and calls lwip_close, but
it seems that the tcp_pcb is stuck in FIN_WAIT_1 because it never receives any
further data on the connection.

    _______________________________________________________
(Continue reading)

chrysn | 25 Jan 00:17 2015
Picon

[bug #44082] unit tests fail out of the box

URL:
  <http://savannah.nongnu.org/bugs/?44082>

                 Summary: unit tests fail out of the box
                 Project: lwIP - A Lightweight TCP/IP stack
            Submitted by: chrysn
            Submitted on: Sat 24 Jan 2015 23:17:10 GMT
                Category: None
                Severity: 3 - Normal
              Item Group: Faulty Behaviour
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: 
            lwIP version: git head

    _______________________________________________________

Details:

when running the unit tests by checking out lwip and lwip-contrib masters and
running `make check` in lwip-contrib/ports/unix/check on debian sid with check
0.9.10-6.1, the checks don't even run, with such error messages:

> libcheck.a(check.o): In function `tcase_create': (.text+0x194): undefined
reference to `floor'

running `LDFLAGS="-lm -lpthread -lrt" make check` makes the problems go away.
(Continue reading)

Krishna Shingala | 24 Jan 13:44 2015
Picon

[task #13455] Extend neighbhor discovery ti support 6LoWPAN better.

URL:
  <http://savannah.nongnu.org/task/?13455>

                 Summary: Extend neighbhor discovery ti support 6LoWPAN
better.
                 Project: lwIP - A Lightweight TCP/IP stack
            Submitted by: kshingala
            Submitted on: Sat Jan 24 12:44:21 2015
                Category: IPv6
         Should Start On: Sat Jan 24 00:00:00 2015
   Should be Finished on: Tue Feb 24 00:00:00 2015
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
        Percent Complete: 0%
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None
                  Effort: 0.00

    _______________________________________________________

Details:

For use cases that implement a 6LoWPAN inerface, the context identifiers and
prefixes distributed as a part of neighbor discovery procedures need to be
provide to the 6LoWPAN layer to enable efficient compression and decompression
of the IP header. This interface today does not exist in lwIP as lWIP does not
accound for the 6LoWPAN. It will be extremly useful to enable notifying new
(Continue reading)

Krishna Shingala | 24 Jan 13:25 2015
Picon

[bug #44077] lwIP as IPv6 only stack.

URL:
  <http://savannah.nongnu.org/bugs/?44077>

                 Summary: lwIP as IPv6 only stack.
                 Project: lwIP - A Lightweight TCP/IP stack
            Submitted by: kshingala
            Submitted on: Sat Jan 24 12:25:32 2015
                Category: IPv6
                Severity: 3 - Normal
              Item Group: Feature Request
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: 
            lwIP version: git head

    _______________________________________________________

Details:

6LoWPAN interfaces are being defined for many of the short range wireless
technolgies and these use cases require an embedded IPv6 only stack.

Today, while it is possible to use lwIP stack's IPv6 functionality, it is not
possible to not include reduncdant IPv4 portions of the stack, resulting in
large code size.

    _______________________________________________________
(Continue reading)

chrysn | 22 Jan 18:25 2015
Picon

[bug #44069] udp_sendto and similar don't accept const destination addresses

URL:
  <http://savannah.nongnu.org/bugs/?44069>

                 Summary: udp_sendto and similar don't accept const
destination addresses
                 Project: lwIP - A Lightweight TCP/IP stack
            Submitted by: chrysn
            Submitted on: Thu 22 Jan 2015 17:25:48 GMT
                Category: UDP
                Severity: 3 - Normal
              Item Group: Change Request
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: 
            lwIP version: git head

    _______________________________________________________

Details:

functions like udp_sendto take address arguments which they
conceptionally won't modify, but do not declare them as const. this
causes issues with libraries like libcoap that treat their addresses,
which might be shared among different parts of the program, as const.

the attached patch is more a suggestion for discussion than a complete
solution, for once because it's atop DEVEL-1_4_1, and then because it is not
(Continue reading)

Simon Goldschmidt | 17 Jan 21:18 2015
Picon

[bug #44032] select might work on invalid/reused socket

URL:
  <http://savannah.nongnu.org/bugs/?44032>

                 Summary: select might work on invalid/reused socket
                 Project: lwIP - A Lightweight TCP/IP stack
            Submitted by: goldsimon
            Submitted on: Sa 17 Jan 2015 20:18:08 GMT
                Category: sockets/netconn
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: 
            lwIP version: git head

    _______________________________________________________

Details:

When a socket gets closed and reused from another thread while select is
waiting on it, 'select_waiting--' can be executed on this socket although it's
not the socket where 'select_waiting++' was executed before (this mainly
depends on the priorities of the threads using sockets).

To circumvent this, we could either not completely free sockets where select
is waiting or add a global 'sockalloc' counter, stored per socket, which
select could used to detect newly allocated sockets.
(Continue reading)

Simon Goldschmidt | 17 Jan 14:32 2015
Picon

[bug #40788] lwip_setsockopt_internal() crashes

Update of bug #40788 (project lwip):

                  Status:                    None => Fixed                  
             Assigned to:                    None => goldsimon              
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #1:

Fixed for (hopefully) all cases in set/getsockopt (NULL check was missing in
many places).

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?40788>

_______________________________________________
  Nachricht gesendet von/durch Savannah
  http://savannah.nongnu.org/
Simon Goldschmidt | 16 Jan 17:35 2015
Picon

[bug #44023] TCP: ssthresh value is unclear

URL:
  <http://savannah.nongnu.org/bugs/?44023>

                 Summary: TCP: ssthresh value is unclear
                 Project: lwIP - A Lightweight TCP/IP stack
            Submitted by: goldsimon
            Submitted on: Fr 16 Jan 2015 16:35:58 GMT
                Category: TCP
                Severity: 3 - Normal
              Item Group: Change Request
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: 
            lwIP version: git head

    _______________________________________________________

Details:

There are some things unclear to me in the value of ssthresh:

- it is set to "pcb->mss * 10" when connecting (for client connections): why
10 * MSS?

- it is set to *the full snd_wnd" in tcp_listen_input() (for server
connections)

(Continue reading)

salih ahi | 8 Jan 10:29 2015
Picon

[bug #43951] minimal project "echop" not working on the specified ip

URL:
  <http://savannah.nongnu.org/bugs/?43951>

                 Summary: minimal project "echop" not working on the specified
ip
                 Project: lwIP - A Lightweight TCP/IP stack
            Submitted by: legyndir
            Submitted on: Thu 08 Jan 2015 09:29:33 AM GMT
                Category: Contrib
                Severity: 3 - Normal
              Item Group: Faulty Behaviour
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: 
            lwIP version: git head

    _______________________________________________________

Details:

When I compile and run "contrib-1.4.1/ports/unix/proj/minimal" the default
message indicates:
Host at 192.168.0.2 mask 255.255.255.0 gateway 192.168.0.1

But if I try to connect with "nc -C 192.168.0.2 7" I get "No route to host"
error.

(Continue reading)

hanhui | 30 Dec 06:42 2014
Picon

[bug #43904] ip_route() and ip6_route() must detect linkup status.

URL:
  <http://savannah.nongnu.org/bugs/?43904>

                 Summary: ip_route() and ip6_route() must detect linkup
status.
                 Project: lwIP - A Lightweight TCP/IP stack
            Submitted by: hanhui03
            Submitted on: Tue 30 Dec 2014 05:42:25 AM GMT
                Category: IPv4
                Severity: 3 - Normal
              Item Group: Faulty Behaviour
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: 
            lwIP version: git head

    _______________________________________________________

Details:

Hi Simon 

   ip_route() select netif only detect netif_is_up(), I suggest that add
netif_is_link_up() detect.

   ip6_route() did not even detect the state of the network interface.

(Continue reading)

salih ahi | 23 Dec 14:25 2014
Picon

tapif.c gateway-ip bug

In addition to the netmask ignoring I mentioned in the previous post, the interface is given the ip of gateway, instead of the ip specified after the “-i” parameter

sprintf(buf, IFCONFIG_BIN IFCONFIG_ARGS,

                  ip4_addr1(&(netif->gw)),

 

these 4 arguments to sprintf should be built from “netif->ip_addr”, not from “netif->gw”

_______________________________________________
lwip-devel mailing list
lwip-devel <at> nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-devel

Gmane