i’ve two techniques:
- system:
RPi4 with ENC28J60 community adapter (192.168.178.91)
working FreeRTOS on baremetal with UART debug output
- system:
dev-pc with Win11 (192.168.178.15)
working with PowerShell: ‘Check-NetConnection -ComputerName 192.168.178.91 -Port 10310’
They’re linked with a normal-patch cable (dev-pc do mdix) [no switch, no router]
gateway settings are left clean in addition to DNS, solely IP deal with and netmask: 255.255.255.0 are crammed out
My Drawback:
dev-pc sends an SYN and RPi4 reply with SYN+ACK, however now the ACK from dev-pc is lacking:
[![enter image description here][1]][1]
due to this, dev-pc is resuming SYN-paket.
RPi4 output reveals, that each SYN-paket is reply by SYN+ACK paket:
prvIPTask began
Beginning community up.
uart places on core1 working
printf on core1 working
main_Core1 has began!
Core1 begins Scheduler
Community card efficiently initialised.
Ready for ifup...
community is up and working.
Socket 10310 -> 0.0.0.0:0 State eCLOSED->eTCP_LISTEN
Socket 10400 -> 0.0.0.0:0 State eCLOSED->eTCP_LISTEN
Community buffers: 96 lowest 96
Community buffers: 96 lowest 95
Community buffers: 95 lowest 94
Community buffers: 94 lowest 93
Community buffers: 92 lowest 92
Community buffers: 91 lowest 91
Acquire: Socket 10310 now has 1 / 20 little one
prvSocketSetMSS: 1460 bytes for 192.168.178.15:35657
Socket 10310 -> 192.168.178.15:35657 State eCLOSED->eSYN_FIRST
Socket 10310 -> 192.168.178.15:35657 State eSYN_FIRST->eSYN_RECEIVED
eSYN_RECEIVED: ACK anticipated, not SYN: peer missed our SYN+ACK
Socket 10310 -> 192.168.178.15:35657 State eSYN_RECEI
Community buffers: 90 lowest 90
Socket 10310 -> 192.168.178.15:35657 State eSYN_FIRST->eSYN_RECEIVED
eSYN_RECEIVED: ACK anticipated, not SYN: peer missed our SYN+ACK
Socket 10310 -> 192.168.178.15:35657 State eSYN_RECEIVED->eSYN_FIRST
Socket 10310 -> 192.168.178.15:35657 State eSYN_FIRST->eSYN_RECEIVED
eSYN_RECEIVED: ACK anticipated, not SYN: peer missed our SYN+ACK
Socket 10310 -> 192.168.178.15:35657 State eSYN_RECEIVED->eSYN_FIRST
Socket 10310 -> 192.168.178.15:35657 State eSYN_FIRST->eSYN_RECEIVED
Community buffers: 91 lowest 89
eSYN_RECEIVED: ACK anticipated, not SYN: peer missed our SYN+ACK
Socket 10310 -> 192.168.178.15:35657 State eSYN_RECEIVED->eSYN_FIRST
Socket 10310 -> 192.168.178.15:35657 State eSYN_FIRST->eSYN_RECEIVED
Does anybody has a clue, whats mistaken?
[1]: https://i.sstatic.web/XISPFB6c.png
