You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I didn't mean that get(2..1) is a bug itself. In the DHCP protocol an option with length 4 has 6 octets (4 + code + length fields) and I thought that TCP was identical. But it seems like in TCP the length field includes the whole option, i.e. length 4 means 4 octets. So no bug here, just a strange difference between the TCP and DHCP option format.
I think there is a bug in this line in wire/tcp.rs:
I think it should be
buffer.get(2..(2+length))
instead, because otherwise we try to take the range2..1
for an option with length 1.The text was updated successfully, but these errors were encountered: