Protocols/dhcp
the following is a list of how the DHCP talks over the network,
"bounce" is sending back the data so the sender can verify for integrity
the servers don't wait for to long for users, you can't type this fast enough, you'll have to use programs to make use of this.
this is to prevent a single user from hogging the servers.
dhcp request: - used by clients to find the dhcp server
client: BROADCAST:"DHCP-REQ" [requests dhcp id]
server: "DHCP-ACK"[responds with id]
auth server id request: - requests ID of the AUTH server, integer value.
client:string, "AUTH-ID" [request auth id]
server: int, ID value for _G.authserver [responds with id]
dhcp lookup - this is used to look up registered systems on the rednet network and can be used by programs to do network calls. it's like DNS.
client:string, "DHCP-LOOKUP" [request lookup session]
server:string, "DHCP-ACK" [server responds and waits for client]
client:string, searchname [send the name to search]
server:string, searchname [bounce data back]
client:string, "SYNC-TRUE"/"SYNC-FALSE" [data is in sync true or false, not a bool for corruption reasons]
-- dhcp does it's lookup in it's files
server: string, lookupname
server: string, lookupid
server: string, lookupowner
dhcp register - this registers a system on the dhcp server that can be looked up.
client:string, "DHCP-REG" [request register]
server:string, "DHCP-REG-ACK" [server responds and waits for client]
client: string, username [logged in username]
client: string, password [logged in password]
client: string, sysname [system name]
server: string, username [bounce back]
server: string, password [bounce back]
server : string, sysname [ bounce back]
client: string, "SYNC-TRUE" / "SYNC-FALSE" [data verification is true or false]
-- at this point, the dhcp server talks to the auth server, this is explained there as it does not apply to the dhcp client
server: string, "DHCP-ALERT" / "REG-EXIST" / "REG-ACCEPT" [server response, accept means it's done, alert means hacking attempt!]
dhcp unregister: - removes a system from the dns registry
client:string, "DHCP-UREG" [request register]
server:string, "DHCP-REG-ACK" [server responds and waits for client]
client: string, username [logged in username]
client: string, password [logged in password]
client: string, sysname [system name or id]
server: string, username [bounce back]
server: string, password [bounce back]
server : string, sysname [ bounce back]
client: string, "SYNC-TRUE" / "SYNC-FALSE" [data verification is true or false]
-- at this point, the dhcp server talks to the auth server, this is explained there as it does not apply to the dhcp client
server: string, "DHCP-ALERT" / "REG-EXIST" / "REG-ACCEPT" / " REG-DENIED" [server response, accept means it's done, alert means hacking attempt!]