home.social
Sign in Create account

#lwip — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #lwip, aggregated by home.social.

  1. goetz @[email protected] ·
    CW: IPv6 rant

    I hate, that I have to explain again and again that EUI64 address generation is the worst feature of #IPv6 in terms of tracking and privacy.
    Nevertheless nearly all #IoT devices us #lwIP which lacks RFC7217 or RFC4941/8981 support and leaks GUIDs to everyone listening.

    When is everyone taking this serious?

    Even a famous German CPE vendor uses this method.

    Have a look here if you do not understand what I mean:

    bgp.tools/prefix/2a02:908:8000

    BTW your #Synology #nas spoils your privacy.

    #ipv6 #iot #lwip #synology #nas
  2. goetz @[email protected] ·

    #IPv6, #EUI64 und #IoT

    Ein deutscher Heizungshersteller bietet ein IoT Connector für seine Heizungen/Wärmepumpen an. Dieser kann DualStack (yeah) allerdings EUI64 GUA (😭 ).
    DNS ist #IPv4only A/AAAA Queries und im Moment sind alle Endpunkt für APIs #IPv4only weil #azure

    Was können wir tun, damit #lwIP #RFC7217 #RFC8981 kann?

    #ipv6 #eui64 #iot #ipv4only #azure #lwip
  3. uvok @[email protected] ·

    Uvoks daily struggle.

    "Huh?? Why does the LwIP stack send an ACK for a second incoming TCP connection?? I only accept one at a time!?!?"

    Apparently, that's a "backlog", and it's suffering you can't turn off completely.
    If I really want to only work with one client at a time, I probably have to accept and close the other sockets immediately?

    (No, setting backlog to 0 on listen doesn't help)

    #esp32 #lwip #networking

    #esp32 #lwip #networking
  4. LeoDJ @[email protected] ·

    Accessing #lwip directly seems to work pretty ok already.

    Now I'm trying to see how far I can implement rudimentary #Arduino framework compatibility (before losing interest in the tedium).

    After some hours, the EthernetClient finally behaved enough for a simple TCP echo test :D

    #WCH #CH32 #CH32V208

    #lwip #arduino #wch #ch32 #ch32v208
  5. LeoDJ @[email protected] ·

    Progress of the night: Getting the essentials of the #lwip stack running on the #CH32V208.

    Still need to clean it up _a lot_ and build the wrapping library, so it's actually useful.
    But seeing lwip run at all is amazing.
    (So I don't need to depend on the proprietary, closed source #WCHNET library)

    Good night :D

    #WCH #CH32

    #lwip #ch32v208 #wchnet #wch #ch32
  6. xq @[email protected] ·

    @cv Everything except #lwIP and the FatFS library. But i'm going to replace the FAT library with a driver that is able to handle asynchronous I/Os. Network is working super well tho, lwIP is very Zig-compatible.

    All apps, kernel and so on is written in pure Zig, and it's very convenient

    #lwip
  7. IT News @[email protected] ·

    GP2040: A Configurable Game Pad Firmware - [feralAI] and fellow GitHub contributors present for your viewing pleasure GP2040:... - hackaday.com/2022/09/04/gp2040 #peripheralshacks #directinput #gamepad #rp2040 #xinput #react #rndis #lwip #rgb

    #rgb #lwip #rndis #react #xinput #rp2040
  8. chrysn @[email protected] ·

    @lupyuen When I notice that I started depending on your network library as if it were an OS (using its timer chains and memory slabs). Then I went from #lwIP to @RIOT_OS

    #lwip