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
Each socket type (ICMP, UDP, and TCP) has a corresponding accetps function that determines if the given packet was meant for the current socket. Currently this function accepts the entire IpRepr, but only the source address and destination address are used.
The text was updated successfully, but these errors were encountered:
It isn't really a problem. I was primarily thinking of this as unused information. In particular I was thinking about the case where the packet is something like IPv6 > Hop-by-Hop > UDP. In this case the UDP socket accepts function will accept the IpRepr with a next_header value of Hop-by-Hop, but obviously repr would be a UdpRepr.
Yeah, that check is already done in EthernetInterface, so I didn't add it to accepts as redundant. We may add it for completeness, although it feels a bit pointless.
Each socket type (
ICMP
,UDP
, andTCP
) has a correspondingaccetps
function that determines if the given packet was meant for the current socket. Currently this function accepts the entireIpRepr
, but only the source address and destination address are used.The text was updated successfully, but these errors were encountered: