Networking :: bootpc? n

While playing around with netstat I notice that a port was listening for tcp bootpc on port 68. After doing some research I get conflicting
answers. Some sites/people says bootpc is has to do with dynamic ip addresses and dhcp name servers and others say its for network booting of diskless pc's. I have ran netstat a few times before to see whats running when the net is slow and bootpc is something new. I don't remember configuring anything of the sort.(the only thing new is a lynksys wireless adapter with speed booster(as a side note I finaly got it running by copying the inf files to /home/dsl) would that be whats bringup the bootp protocall?

It, port 68, is used by pump to get a dynamic ip.
If you don't use dynamic ip, which is the default, you can boot dsl with the nodhcp boot code.

If you do use dynamic ip, after you have you net connection working you may wish to close port 68. You can easily do this with the command

sudo pkill pump

thanks

out of curiousity how does the bootp protocalls help with booting diskless workstations? as I have seen this referenced on other sites.

Quote (meltdown_override @ Dec. 17 2006,00:28)

thanks

out of curiousity how does the bootp protocalls help with booting diskless workstations? as I have seen this referenced on other sites.

try "netstat -ntp" as super user to get info about which program uses what port.

bootp is an older version of DHCP, don't bother with it it's arcane^W Archaic knowledge. The only thing DHCP does is to hand some info to clients, e.g. What the client should have as IP address, the internet router the licent should use and perhaps the location of the TFTP server from which you can download your "network disk".

This is all handled by PXE on intel platforms, try /etc/init.d/knoppix-terminalserver on the real Knoppix CD if you want to have a working diskless boot environment.

original here.