forget real hardware, just consider only kernel resource (keeping ip address as lowest resource (let's ignore MAC address))
connectdo exactly (or
- ip, route table, gateway, interface
- chap 24, show how L4 protocol register a handler!!
I should read network internal part 5 and 7
- manage relation between interface and some type of address (non necessary ip address)
- nmcli can also control some parameters
- abstract device (so it can be virtual)
- the name to bind "network operation" to driver kernel module
- kernel ip routing
- kernel packet filtering upon IP layer
- "route" functionality for protocols (network things) other than ip layer
- bridge is still one type of interface, one type of network stack driver
- after route check
- involves transmission
- local delivery
- tcp (connect, listen)
- will register handler to ip_rcv ?
$ ip route $ route $ ifconfig -s
- when these are initialized?
- from systemd?
- or from programs itself (e.g. vbox, docker)
- how socket, interface, address are managed in kernel?
- ip table
- there's a bunch of
Requirements for HTTP/1.1 proxiesin https://tools.ietf.org/html/rfc2616
- and quotes from https://tools.ietf.org/html/rfc7230:
A "proxy" is a message-forwarding agent that is selected by the client, usually via local configuration rules, to receive requests for some type(s) of absolute URI and attempt to satisfy those requests via translation through the HTTP interface.
- snull in ldd3