configd question

[Theoyster]

Curious why configd connects to 10.136.xx.x on every startup? What is 10.136.xx.x?

Connection report for process: configd (/usr/sbin/configd)
Total: 0 Bytes sent, 303 Bytes received
10.136.xx.x (10.136.xx.x), Port 67 (bootps), Protocol 17 (UDP), 0 Bytes sent, 303 Bytes received

 

[LPZ]

It's probably invoking this agent:

IPConfiguration
This agent is responsible for establishing and maintaining IPv4 addresses
on the system. These addresses may be manually specified in the network
preferences or acquired using DHCP (or BOOTP).

What do you get if you open Network Utility (in Utilities), select Lookup, enter [that IP address] and click on Lookup?

 

[Theoyster]

Lookup has started ...


; <<>> DiG 9.2.2 <<>> -x 10.136.xx.x any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 16683
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;x.xx.136.10.in-addr.arpa. IN ANY

;; AUTHORITY SECTION:
10.in-addr.arpa. 300 IN SOA prisoner.iana.org. hostmaster.root-servers.org. 2002040800 1800 900 604800 604800

;; Query time: 25 msec
;; SERVER: 68.115.xx.xx#53(68.115.xx.xx)
;; WHEN: Mon Oct 11 13:47:09 2010
;; MSG SIZE rcvd: 119


The above ip address belongs to my isp...

 

[LPZ]

Lookup has started ...


The above ip address belongs to my isp...

It seems that configd is just obtaining info related to IP configuration. I wouldn't worry about this.

 

[jzuena]

Technically, the 10 network belongs to nobody. It is one of the address blocks used for private networks. DiG is telling you Answer: 0, which means it didn't find a reverse map. The 68.115.xx.xx address is the DNS server at your ISP that replied that it could not find an answer, even when contacting authoritative DNS servers prisoner.iana.org. and hostmaster.root-servers.org. As LPZ said, it is probably the IP address of the DHCP server that gave you your IP address (DHCP is an extension to and uses the same port as BOOTP - UDP 67).