| crhylove | Yo! How do I solve the daedalus repo issue? Release file for http://deb.devuan.org/merged/dists/daedalus/InRelease is not valid yet (invalid for another 9h 33min 39s). Updates for this repository will not be applied. | 00:29 |
|---|---|---|
| crhylove | nm. My clock was way off. | 00:37 |
| * crhylove shrugs | 00:37 | |
| ibanja | . | 01:39 |
| ibanja | I have two modem wan ports. My router is hooked up to one as a firewall and access point for most of my LAN. I just hooked up a computer to the second wan port which now gets it's DHCP from my ISP. The problem is it getting assigned a weird hostname such as c09963002e81-000004. How can I pass my hostname to my ISP's DHCP server? | 01:39 |
| Xenguy | ibanja, Idle awhile, and see if you get any feedback forthcoming | 01:40 |
| ibanja | I have a that says "send host-name = gethostname();" in my /etc/dhcp/dhclient.conf file. Shouldn't that send my correct hostname? | 01:40 |
| ibanja | I have a line that says... | 01:41 |
| ibanja | idling | 01:41 |
| rrq | check with "dhclient -cf /etc/dhcp/dhclient.conf -v" for errors | 01:46 |
| ibanja | I get the following output: https://paste.debian.net/1266266/ but I have semicolons in my dhclient.conf file: https://paste.debian.net/1266267/ | 01:55 |
| rrq | line 16 is mising the "s" ? | 01:56 |
| ibanja | rrq: oops... that was not the original problem though. I deleted the s by mistake while editing the file and trying the line: send host-name "myhost.com" | 04:06 |
| rwp | ibanja, I have never seen Debian/Devuan set the hostname from DHCP. But RHEL does this routinely. Just confirming this is a Debian/Devuan system? (I'll help either way.) | 05:00 |
| rwp | The /etc/dhcp/dhclient.conf send host-name = gethostname(); sets the hostname that is *sent* to the DHCP server. | 05:01 |
| rwp | If the hostname is changing after that point then it is something else that is receiving the hostname from the DHCP server and then setting it. | 05:01 |
| rwp | I always found that truly Evil but a lot of corporate sites do diskless servers that way routinely. | 05:02 |
| buZz | my devuan&debian machines have zero issue configuring their DNS hostnames on my mikrotik with plain normal DHCP | 10:15 |
| gnarface | there's an optional extension to the DHCP protocol that allows the server to set the hostname of the client along with the other network setup info, and some ISPs require your client to accept their assigned hostname to work, i'm not completely sure both the dhcp clients support it | 11:47 |
| buZz | some (many) consumer ISPs dont allow configuring DNS name at all | 11:48 |
| gnarface | yea i remember with comcast much earlier i was able to get it to work by simply figuring out their server-assigned dhcp hostname and setting it manually at the client end | 11:49 |
| gnarface | (at the time they were claiming linux couldn't work with their system but it turns out that was the only barrier) | 11:49 |
| buZz | hmhm | 11:50 |
| gnarface | during the later incident when i was setting up both server and client ends, i recall having to add a shell script to a hook in the clients to make it work, but i'm not sure that's still required | 11:50 |
| gnarface | the thing is, it's not part of the base standard it's some microsoft extension | 11:51 |
| gnarface | (dhcp wasn't meant to be a security feature but some ISPs are using it that way anyway) | 11:59 |
| tomtmym | Hello | 12:35 |
| tomtmym | i have problem with running virtualbox 6.1 on devuan | 12:36 |
| tomtmym | yesterday i installed virtualbox 6.1, it ran perfectly, today i start to run a VM it gives me error | 12:36 |
| ibanja | rwp: Yes, I'm running Devuan GNU/Linux 4 (chimaera). | 12:54 |
| gnarface | tomtmym: what is the error? | 15:29 |
| tomtmym | gnarface: "kernel driver not installed (rc=-1908)", but as i said before, it was working fine yesterday, only today i get this error | 19:19 |
| rwp | ibanja, With package isc-dhcp-client using dhclient? That's my standard configuration too and it does not set the host's hostname for me. | 19:23 |
| rwp | Have you perhaps (just brainstorming) installed something else that would have installed a hook which would set the hostname? | 19:23 |
| rwp | You might try running this "dpkg -S /etc/network/" looking at what packages install files there as a hint for possibilities. | 19:24 |
| gnarface | tomtmym: the host OS is linux? or just the guest? | 19:30 |
| tomtmym | gnarface: the host is linux | 19:30 |
| tomtmym | devuan | 19:30 |
| gnarface | did you upgrade the kernel between then and now? | 19:31 |
| gnarface | tomtmym: my best guess based on google results (i don't use virtualbox) is that it's either a permissions problem or the vboxdrv isn't loaded | 19:39 |
| gnarface | vboxdrv kernel module that is | 19:40 |
| ibanja | rwp:yes "with package isc-dhcp-client"... Looking at "dpkg -S /etc/network/" as you suggested doesn't show anything unusual installed, and nothing recent. I was getting a proper hostname when behind a router. I think it might be something to do with the ISP. | 19:48 |
| rwp | ibanja, I don't see how an ISP would have any special access to set a hostname, or not, on the DHCP client side of things. That's all client side software. | 20:00 |
| rwp | The /etc/dhcp/dhclient.conf sets up what data is exchanged in the request. But then dhclient or other client side software acts upon it. | 20:02 |
| gnarface | rwp: it's a real thing, it can be sent as part of the dhcp response it's just not a part of the core standard | 20:02 |
| rwp | And normally that does not include changing the local hostname to match what was returned. | 20:02 |
| rwp | It's definitely a real thing. dhclient has a "host-name" attribute which is requested from the dhcp server. But that doesn't mean it actually changes the hostname. | 20:03 |
| rwp | And dhclient sends the hostname. Because doing things like dual booting with different hostnames requires the dhcp server to offer different IP addresses. | 20:03 |
| rwp | In the end though it is happening on ibanja's system and so whatever is happening must be debugged there. | 20:04 |
| gnarface | no you can also have the dhcp client request a host name | 20:04 |
| gnarface | some dhcp clients may use it out of the box, some may ignore it, some may require using a script hook | 20:05 |
| tomtmym | gnarface: no, i did not upgrade the kernel | 20:06 |
| gnarface | rwp, ibanja: https://askubuntu.com/questions/104918/how-to-get-the-hostname-from-a-dhcp-server | 20:07 |
| gnarface | some disagreement here, but if you read all the posts and fill in the blanks you should be able to figure it out | 20:07 |
| gnarface | it's an ancient post so like i said, you might not need to make your own script hook anymore | 20:09 |
| gnarface | but i definitely had to do that at one point | 20:09 |
| gnarface | some ISPs use an optional extension to the DHCP protocol where the server actually assigns a hostname but it's not default behavior for most linux distros to obey it | 20:10 |
| gnarface | the functionality tends to be buggy, missing, or just off by default | 20:10 |
| gnarface | but you can make it work and it's not the same thing as sending a hostname with the dhcp request | 20:11 |
| ibanja | gnarface: having a look at the link now | 20:18 |
| ibanja | "hostname -d" returns "hostname: Name or service not known" | 20:23 |
| ibanja | not sure if that is meaningful | 20:24 |
| gnarface | hostname -d returns the domain name | 20:27 |
| gnarface | domain name and host name are not the same thing in this context | 20:27 |
| gnarface | and you should have both but it is possible to have neither | 20:27 |
| gnarface | ibanja: you should try to find a more recent discussion on this matter somewhere out there that will take into account updates in the dhcp client you're using | 20:29 |
| gnarface | (if there were any relevant ones) | 20:29 |
| gnarface | at the very minimum, you should have this line in your /etc/hosts file for things to work properly: 127.0.0.1localhost.localdomainlocalhost | 20:30 |
| gnarface | and the output of /sbin/ifconfig should show device lo set to 127.0.0.1 | 20:31 |
| gnarface | it's also possible for that to be wrong, but hopefully you're not so far off the path | 20:31 |
| gnarface | ibanja: (also note that if you have moved the machine to a different location with a different dhcp server, you can't necessarily rely on any hostname or domain name being assigned and may have to set one yourself manually) | 20:40 |
| gnarface | (in that case you can just add it to /etc/hosts) | 20:41 |
| gnarface | (changes to that file take effect immediately but firefox may have to be restarted) | 20:41 |
| rwp | As ibanja explained things the problem is the opposite of the current suggestions. As I understand it, it is a problem that the system is setting the hostname to the DHCP'd hostname. That's what needs to stop. | 20:42 |
| ibanja | gnarface: should localhost.localdomain be localhost.localdomain or localhost.mydomain ? | 21:01 |
| ibanja | I have: "myhostname.domainname.com hostname in /etc/hosts | 21:02 |
| ibanja | yes, rwp is correct. | 21:02 |
| rwp | ibanja, /etc/hosts should have a line "127.0.0.1 localhost" no .localdomain attached. That's also the default install value. | 22:01 |
| rwp | A strategy adopted by Debian forever ago was to have an line "127.0.1.1 foo.example.com foo" for the local hostname and domain. | 22:02 |
| rwp | (Sidebar: That was proposed by Thomas Hood an eon ago.) | 22:02 |
| rwp | It's a strategy and there are alternatives sometimes needed. But that one works for most people. | 22:03 |
| rwp | The localhost.localdomain thing is a different strategy for a generic machine configuration. Generic without a customized hostname and without a customized domain. | 22:03 |
| ibanja | I have that correct then. | 22:04 |
| rwp | When installing postfix, exim, sendmail, whatever, (for example) they can use that as the packaged default name and everything will be self consistent. | 22:04 |
| rwp | And if you don't have anything to set those too then they can continue to be used and things continue to work as installed. | 22:04 |
| rwp | I have a domain name that I use. I like assigning names to my systems. So when installing I tell the installer my hostname and domain name | 22:05 |
| rwp | and the installer will set up 127.0.1.1 angst.proulx.com angst" for my system for example at install time. | 22:05 |
| rwp | But that's the story on the .localdomain thing. It's a working placeholder for a generic system without a different domain name. | 22:06 |
| rwp | The idea with 127.0.1.1 is that it is always available even when eth0/wlan0 is offline. And so network daemons like sshd, ntpd, are happy regardless. | 22:07 |
| rwp | The case where that sometimes does not work is most often corporate CAD/EDA design labs with software that runs across a distributed cluster of systems | 22:08 |
| rwp | and that passes what it thinks is it's own IP address around to other systems in the cluster. | 22:08 |
| rwp | Software that looks at the IP address associated with the hostname will see 127.0.1.1 and pass that to the sibling computer farm system in the collective | 22:09 |
| rwp | and that system will talk to itself instead of the sibling. So in that particular type of environment we must revert back to the classic | 22:09 |
| rwp | way of setting up static IP address assignments and assigning that in /etc/hosts associated with the hostname hard coded. | 22:09 |
| ibanja | OK, thanks for the explanation. | 22:12 |
| ibanja | I don't know if this is meaningful, but when I run: "dig @myISP-DNS-server mydomain.com" on my desktop that is behind a router-firewall I get "mydomain.com IN A" When I run the same command from the edge computer I get "mydomain.com IN A 173.18.xx.xx" | 22:15 |
| ibanja | the desktop behind the firewall doesn't return the IP address. | 22:16 |
| rwp | Is the DHCP server registering a dynamic DNS name for the address negotiated? And you get that address when talking to the DHCP servers DNS server but not otherwise? | 22:19 |
| rwp | Honestly you redacted information which made looking at it confusing. So I might have missed the mark by a lot there. | 22:19 |
| Helenah | Hi | 22:21 |
| rwp | ibanja, Is mydomain.com actually your real domain name? Or is it an example. If you are going to use examples please use one of example.com, example.net, example.org and then we know what they are since those are designated for that purpose. | 22:21 |
| rwp | Hello Helenah. Welcome to #devuan. This is the community support channel. Social chatter in #devuan-offtopic is welcome! :-) | 22:21 |
| Helenah | I see | 22:22 |
| ibanja | it is an example... example.com | 22:24 |
| rwp | Note that dig only looks at DNS information. It does not look at files, does not look at /etc/hosts at all. It's a DNS query tool only. | 22:34 |
| Helenah | What rwp said | 22:47 |
| Helenah | It's accurate advice. :) | 22:47 |
| Helenah | Okay so at the Devuan installer I get "The exchange of keys and association with the access point failed. Please check the WPA/WPA2 parameters you provided" so I check the WPA/WPA2 parameters I provided against the router, they match so I try again, same problem, this has to be some non-free situation surely. | 22:51 |
| rrq | did you chose an https mirror ? | 22:53 |
| rwp | WiFi problems! Sigh. Surely the weakest link in installer. Which install image are you trying? netinst? Or one of the others? | 22:53 |
| * rrq ah, right. | 22:53 | |
| rwp | Note install documentation is here https://www.devuan.org/os/documentation/install-guides/chimaera/install-devuan | 22:53 |
| Helenah | rwp: *-server.iso | 22:53 |
| Helenah | yes that release | 22:53 |
| Helenah | rrq: Not at that stage yet and rightly so. | 22:54 |
| rwp | Then I would recommend completing the install completely from the included iso without a network connection. Booting. Then sorting out the WiFi afterward. | 22:54 |
| Helenah | Not necessary, I'll plug into Ethernet to continue, that way I'm not having to mess with sources.list later. | 22:55 |
| rwp | Also knowing which WiFi device you have is useful as some are supported and some like Broadcom unfortunately have no working Linux kernel drivers. | 22:55 |
| rwp | Definitely installing with a wired connection is most reliable. | 22:55 |
| Helenah | Don't worry, I've used GNU/Linux since 2005, I've learned to avoid broadcom wifi. :) | 22:56 |
| rwp | Awesome! I'll just say in passing that wicd is python2 and no longer supported on the python3 based Devuan 4 Chimaera. So connman is the heir apparent to wicd now. | 22:59 |
| rwp | Or there is, ahem, NetworkManager, which I hate it having screwed me over too many times. So I avoid it. But others do use it. | 23:00 |
| rwp | And of course there is the old standby way of configuring wpa_supplicant directly. Which is mostly what I do these days. But that's the deep detail method. | 23:00 |
| Helenah | I use NetworkManager on laptops. | 23:01 |
| rwp | Then you will be set. :-) | 23:01 |
| Helenah | Yeah, any system which is portable, I found things like nettools, systemd-networkd, etc to be tedious when things need to change dynamically so NetworkManager is perfect here for me. :D | 23:04 |
| Helenah | But yeah it has its problems like you pointed out. | 23:04 |
| Helenah | rwp: I ran a shell from the installer, I'm wanting to shrink a partition as small as possible. | 23:14 |
| Helenah | se7en: Great movie. :D | 23:15 |
| fsmithred | Helenah, try setting the wireless password to all lower-case alpha with no special characters. I've had that problem in the installer. After install, you can switch it back to lower/upper/special characgters. | 23:56 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!