- RMLL 2008, days 1 and 2
- Sub-pixel antialiasing report #1 [GSoC]
- HCD [bfs]: Status Report #1
- Timers (GSoC) Update #1
- Haiku Code Drive: May 16 update
- Google Summer of Code project: Sub-pixel anti-aliasing
- Google Summer of Code Project: Alternate System Timers
- Anthy Ported to Haiku, Binary Available on Bebits
- Premonitions of a rising sun
- GSoc Swap File Project
ivo's blog
Design Considerations
Thu, 2007-07-05 07:24 Tags: icmp :: network stack :: protocols
Haiku's network stack follows a top-down approach with clear boundaries, pure object oriented design. However, TCP/IP protocol stack was designed more than 30 years ago with different idea in mind. It's mostly speed, fast processing and stability that designers were looking for back then. That's why many boundaries in the TCP/IP protocol suite design are blurred somehow.
Current ICMP implementation in HAIKU kernel
Hi all,
According to current Haiku source ICMP implementation is only a ... framework. Only ICMP echo request messages are processed.
There are essentially two RFCs that should be considered when implementing ICMP (for IPv4). RFC792 - 'INTERNET CONTROL MESSAGE PROTCOL' and RFC1122 - 'Requirements for Internet Hosts -- Communication Layers'.
According to RFC1122, paragraph 3.2.2. there are two types of ICMP messages a host must process:
1) ICMP Error Messages
- Destination Unreachable
- Redirect
- Source Quench
- Time Exceeded
- Parameter Problem
2) ICMP query messages:
- Echo
- Information
- Timestamp
- Address Mask
