Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

udhcpc: always send DHCP hostname #14

Merged
merged 1 commit into from
Dec 6, 2014
Merged

udhcpc: always send DHCP hostname #14

merged 1 commit into from
Dec 6, 2014

Conversation

filippog
Copy link

this makes it easy for a local router/server to identify clients and update for example its internal DNS resolver (also matching dhclient behavior in jessie)

so e.g. dnsmasq can update its local DNS resolver

also honour -H if "hostname" option is set in /etc/network/interfaces
@filippog
Copy link
Author

upon further testing passing :::: seems to change ipconfig behavior and it'll probe all interfaces, I'll need to dig into it more. anyways you get the general idea, I think it'd be good to send along the hostname

@mk01
Copy link
Member

mk01 commented Dec 6, 2014

@filippog

yes, with ipconfig it is usage of parameters or the compiled setting in :::::: format. but net interface is one of the parameters also in the compiled list. I'm going to merge this and will try to correct that one line. can you retest then ?

mk01 added a commit that referenced this pull request Dec 6, 2014
udhcpc: always send DHCP hostname
@mk01 mk01 merged commit bce7c1d into xbianonpi:master Dec 6, 2014
@mk01
Copy link
Member

mk01 commented Dec 6, 2014

I pushed the update ... with the change this was result, so probably ok but please test.
90bbdee

root@cubox ~ # ipconfig -t 60 "::::cubox.private:eth0:dhcp"
IP-Config: eth0 hardware address d0:63:b4:00:1e:a0 mtu 1500 DHCP
hostname cubox.private hostname cubox.private IP-Config: eth0 guessed broadcast address 192.168.1.255
IP-Config: eth0 complete (dhcp from 192.168.1.252):
 address: 192.168.1.12     broadcast: 192.168.1.255    netmask: 255.255.255.0   
 gateway: 192.168.1.1      dns0     : 192.168.1.104    dns1   : 192.168.1.252   
 domain : private                                                         
 rootserver: 192.168.1.252 rootpath: 
 filename  : 

@filippog
Copy link
Author

filippog commented Dec 6, 2014

ok thanks! I should be able to test it in the next few days, what's the
easiest way I can do that? Is it already in a package I can install?

thanks

On Sat, Dec 6, 2014 at 1:00 AM, Matus Kral notifications@github.com wrote:

I pushed the update ... with the change this was result, so probably ok
but please test.

root@cubox ~ # ipconfig -t 60 "::::cubox.private:eth0:dhcp"
IP-Config: eth0 hardware address d0:63:b4:00:1e:a0 mtu 1500 DHCP
hostname cubox.private hostname cubox.private IP-Config: eth0 guessed
broadcast address 192.168.1.255
IP-Config: eth0 complete (dhcp from 192.168.1.252):
address: 192.168.1.12 broadcast: 192.168.1.255 netmask: 255.255.255.0

gateway: 192.168.1.1 dns0 : 192.168.1.104 dns1 : 192.168.1.252

domain : private

rootserver: 192.168.1.252 rootpath:
filename :


Reply to this email directly or view it on GitHub
#14 (comment).

@mk01
Copy link
Member

mk01 commented Dec 7, 2014

it is not. pull from git, run gen.package.sh from root repo dir (assuming you have fakeroot, binutils(armhf) and dev-scripts packages installed.

(binutils is not required (so ignore warnign/errros) - you get xbian-updateXXXX.deb. install with dpkg -i

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants