Re: [DNG] Wicd + dhclient no longer sends the correct host name and doesn't request search domains anymore in ascii.
On Mon, 12 Mar 2018 13:03:50 +0100 Arnt Karlsenwrote: > On Mon, 12 Mar 2018 10:17:05 +, Rowland wrote in message > <20180312101705.7dca7...@devstation.samdom.example.com>: > > > Hi Didier, all of what you say is true, but if there is a wicd > > package, then it needs to work as expected. > > ...and if it doesn't, a nice big warning should wake up the user > and recommend a viable work-around. Is apt-listbugs part of the default installation? In this case this could be easily accomplished with a bug report with severity >serious that includes the work-around. libre Grüße, Florian pgpGEPGQ3R7Wk.pgp Description: OpenPGP digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Wicd + dhclient no longer sends the correct host name and doesn't request search domains anymore in ascii.
On Mon, Mar 12, 2018 at 01:03:50PM +0100, Arnt Karlsen wrote: > On Mon, 12 Mar 2018 10:17:05 +, Rowland wrote in message > <20180312101705.7dca7...@devstation.samdom.example.com>: > > > Hi Didier, all of what you say is true, but if there is a wicd > > package, then it needs to work as expected. > > ...and if it doesn't, a nice big warning should wake up the user > and recommend a viable work-around. > OK, message got, we inherited a bug from Debian stretch, we are sorry for that, but having a Beta of ASCII was intended to identify and solve such glitches :) Would you please mind testing the wicd package available in ascii-proposed, and report any regression and any success, so that we can include it in the forthcoming ASCII RC? Thanks KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Wicd + dhclient no longer sends the correct host name and doesn't request search domains anymore in ascii.
On Mon, 12 Mar 2018 10:17:05 +, Rowland wrote in message <20180312101705.7dca7...@devstation.samdom.example.com>: > Hi Didier, all of what you say is true, but if there is a wicd > package, then it needs to work as expected. ...and if it doesn't, a nice big warning should wake up the user and recommend a viable work-around. -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Wicd + dhclient no longer sends the correct host name and doesn't request search domains anymore in ascii.
On Mon, Mar 12, 2018 at 10:17:05AM +, Rowland Penny wrote: [cut] > > Hi Didier, all of what you say is true, but if there is a wicd package, > then it needs to work as expected. > > As for anybody using wicd on Devuan and having slight problems, just > feel glad you are not using Ubintu 18.04. This has something called > 'systemd.resolved', which, for some unknown reason, puts yet another > layer in the resolv stack and refuses to let you change > /etc/resolv.conf > Dear Rowland, please try the wicd package available in ascii-proposed. It should work OOTB. The only change is a hard dep on net-tools, which should solve your issue. Please report any problem. HND KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Wicd + dhclient no longer sends the correct host name and doesn't request search domains anymore in ascii.
On Mon, 12 Mar 2018 10:41:09 +0100 Didier Krynwrote: > This is just to remind everyone that wicd isn't necessary - at > least if it doesn't provide anything more than wifi config. > > I've been living without it - and without network-manager - for > many years. All I need is wpa_spplicant and wpa_gui. > > Put the following line in wpa_supplicant.conf: > > ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=dialout > update_config=1 > > Then make yourself a member of group dialout > > Put the following in your /etc/network/interfaces - I know it's > deprecated, but it just works. > > allow-hotplug wlan0 > auto wlan0 > iface wlan0 inet manual > wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf > > iface default inet dhcp > > Now everytime you want to connect to a new wifi station, open > wpa_gui; it's intuitive. If you want wpa_supplicant to remember that > station, then save the config. > > If you have both Ethernet and wifi, then you also need ifplugd. > I know it's potterware, but it works and is still not infected by the > disease. > > Done. > > Didier Hi Didier, all of what you say is true, but if there is a wicd package, then it needs to work as expected. As for anybody using wicd on Devuan and having slight problems, just feel glad you are not using Ubintu 18.04. This has something called 'systemd.resolved', which, for some unknown reason, puts yet another layer in the resolv stack and refuses to let you change /etc/resolv.conf Rowland ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Wicd + dhclient no longer sends the correct host name and doesn't request search domains anymore in ascii.
This is just to remind everyone that wicd isn't necessary - at least if it doesn't provide anything more than wifi config. I've been living without it - and without network-manager - for many years. All I need is wpa_spplicant and wpa_gui. Put the following line in wpa_supplicant.conf: ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=dialout update_config=1 Then make yourself a member of group dialout Put the following in your /etc/network/interfaces - I know it's deprecated, but it just works. allow-hotplug wlan0 auto wlan0 iface wlan0 inet manual wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf iface default inet dhcp Now everytime you want to connect to a new wifi station, open wpa_gui; it's intuitive. If you want wpa_supplicant to remember that station, then save the config. If you have both Ethernet and wifi, then you also need ifplugd. I know it's potterware, but it works and is still not infected by the disease. Done. Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Wicd + dhclient no longer sends the correct host name and doesn't request search domains anymore in ascii.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I don't have time to do something about this at the moment, so I'll just inform everyone here about this problem and add the debian maintainers to the CC of this mail, so whomever has time or needs to know about this at least knows about this issue. In devuan/debian jessie, wicd does send the hostname and requests the search domains in the DHCP reply, but in ascii/stretch, it no longer does so. I believe it uses dhclient with a different dhclient.conf than before, but I don't know what exactly changed. There is an option to set the hostname in wicd, but using it doesn't have any effect and it's off by default. The hostname option is often used by dhcp servers to notify the local dns resolver about new clients, which makes it possible to use their hostname instead of their IP to access them. I think the default should be for the hostname to be sent, because it used to be that way, it may break existing setups and cause a lot of troubleshooting otherwise, and I don't think not having it helps with anything. The domain search option is important to get all search domains. A lot of networks, mine too, are split into different parts. One for lan and one for dmz for example. In that case, it's quiet common to have both in the search domain list. My search domains are "dmz.abrecht.li lan.abrecht.li". This way, I can access both, local clients and my servers using just the hostname and don't have to write out the whole domain. There are some other use cases too. I've only ever seen Windows machines not requesting search domains before, but I alway took for granted that they work everywhere else. They work by default on iOS, Android, Mac, and usually Linux, except if using wicd+dhclient in ascii/stretch. Not requesting the option also won't add any security benefits, because in that case the domain name is used as search domain. But that's insufficient for multiple domains. I'm still on wicd version 1.7.4+tb2-4, which is the same in debian and devuan, and not on the devuan version from backports, but that shouldn't make a difference since these versions only differ in some dependencies and nothing else. I've used "tcpdump -vvv port 68 or port 67" on my dhcp server to capture the DHCP requests. Here is one when using wicd: tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes 18:46:58.202250 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328) 0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 60:36:dd:26:4a:bc (oui Unknown), length 300, xid 0x9160d35, Flags [none] (0x) Client-Ethernet-Address 60:36:dd:26:4a:bc (oui Unknown) Vendor-rfc1048 Extensions Magic Cookie 0x63825363 DHCP-Message Option 53, length 1: Discover Requested-IP Option 50, length 4: 10.60.10.188 Hostname Option 12, length 10: "$_HOSTNAME" Parameter-Request Option 55, length 7: Subnet-Mask, BR, Time-Zone, Default-Gateway Domain-Name, Domain-Name-Server, Hostname END Option 255, length 0 PAD Option 0, length 0, occurs 29 18:46:58.202649 IP (tos 0xc0, ttl 64, id 8355, offset 0, flags [none], proto UDP (17), length 336) dog.bootps > 10.60.10.188.bootpc: [udp sum ok] BOOTP/DHCP, Reply, length 308, xid 0x9160d35, Flags [none] (0x) Your-IP 10.60.10.188 Server-IP dog Client-Ethernet-Address 60:36:dd:26:4a:bc (oui Unknown) file "legacy/pxeboot.0"[|bootp] 18:46:58.206962 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328) 0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 60:36:dd:26:4a:bc (oui Unknown), length 300, xid 0x9160d35, Flags [none] (0x) Client-Ethernet-Address 60:36:dd:26:4a:bc (oui Unknown) Vendor-rfc1048 Extensions Magic Cookie 0x63825363 DHCP-Message Option 53, length 1: Request Server-ID Option 54, length 4: dog Requested-IP Option 50, length 4: 10.60.10.188 Hostname Option 12, length 10: "$_HOSTNAME" Parameter-Request Option 55, length 7: Subnet-Mask, BR, Time-Zone, Default-Gateway Domain-Name, Domain-Name-Server, Hostname END Option 255, length 0 PAD Option 0, length 0, occurs 23 18:46:58.269305 IP (tos 0xc0, ttl 64, id 8357, offset 0, flags [none], proto UDP (17), length 336) dog.bootps > 10.60.10.188.bootpc: [udp sum ok] BOOTP/DHCP, Reply, length 308, xid 0x9160d35, Flags [none] (0x) Your-IP 10.60.10.188 Server-IP dog Client-Ethernet-Address 60:36:dd:26:4a:bc (oui Unknown) file "legacy/pxeboot.0"[|bootp] Here we see that "$_HOSTNAME" was sent as hostname, instead of the real hostname. I think this is clearly a bug. Also Option 119 wasn't requested, which is the