EL9 (Rocky9) EADDRNOTAVAIL (Cannot assign requested address) on connect() #74
Description
- Exablaze device: 192.168.80.3 (Exablaze ExaNIC X100)
- Other end: 192.168.80.2
Communication works well; ping, sockperf and whatever. However when exasock is added to the mix, the following error returns on connect(): EADDRNOTAVAIL (Cannot assign requested address).
Server side: nc -l 192.168.80.2 11111
Exablaze side: nc -s 192.168.80.3 192.168.80.2 11111 ✔️
Exablaze side with exasock: EXASOCK_DEBUG=1 exasock --trace --debug nc -s 192.168.80.3 192.168.80.2 11111:
[pid 7524] signal(13, SIG_IGN) = SIG_DFL
[pid 7524] read(5, "0\n", 2) = 2
[pid 7524] close(5) = 0
[pid 7524] read(4, "\372Y\220\216\334\34}\304\tC\23\270U\243\v\304(\276\330\330\330\345:\305\24R\246\202H\177\233e"..., 236) = 236
[pid 7524] close(4) = 0
[pid 7524] socket(AF_INET, SOCK_STREAM, 6) = 4
[pid 7524] fcntl(4, F_GETFL) = 2
[pid 7524] fcntl(4, F_SETFL, O_NONBLOCK|0x2) = 0
[pid 7524] setsockopt(4, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
[pid 7524] bind(4, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("192.168.80.3")}, 16) = 0
[pid 7524] connect(4, {sa_family=AF_INET, sin_port=htons(11111), sin_addr=inet_addr("192.168.80.2")}, 16exasock: enabled bypass on fd 4
) = -1 EADDRNOTAVAIL (Cannot assign requested address)
Ncat: Cannot assign requested address.
Running exanic-2.7.3-1.el9.x86_64, but also the provided fc32 RPMs yielded the same.
With UDP (nc -u) it seems to work with exasock, however, no accelerated sockets are seen using exasock-stat. Suspecting the socket is not accelerated and this is why it does work.