Did a bit more looking and it looks like I attributed this wrong. The device isn't getting confused by moving to a new port, instead it looks like atftpd may be losing track. Got some better packet traces now:
:69 <- remote RREQ <file>, timeout 5 local -> remote OACK timeout 5 local <- remote ACK, block 0 So, it adapts to the new port, but atftpd never responds to what got tagged as the ACK packet. I'm wondering if atftpd isn't expecting to receive anything on the newly allocated port. -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | [email protected] PGP F6B23DE0 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ 2477\___\_|_/DC21 03A0 5D61 985B <-PGP-> F2BE 6526 ABD2 F6B2\_|_/___/3DE0 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
