Re: How to get Fedora 35 to use DNS name as hostname?
by Thomas Cameron
On 1/18/22 04:10, Petr Menšík wrote:
> dhcp server of libvirt is dnsmasq. It would provide hostnames when it
> has matching dhcp-record with IP and name (and hwaddr). With libvirt,
> that would be set by <ip><dhcp><host name='whatever'> in network
> configuration xml. I think it should use also /etc/hosts of the host.
> But dnsmasq can assign lease just by name if hwaddr is not present in
> static leases. But that requires static hostname on Fedora side to be
> sent to the server.
>
> How does virsh net-dumpxml <network> look like?
In this case, I am connecting via bridged network, so the VM is not
getting its name from dnsmasq but from the dhcpd on a RHEL 8 server.
[root@case ~]# virsh net-dumpxml default
<network>
<name>default</name>
<uuid>0082d9c5-2879-47e6-9c1b-cdf6ff060630</uuid>
<forward mode='nat'>
<nat>
<port start='1024' end='65535'/>
</nat>
</forward>
<bridge name='virbr0' stp='on' delay='0'/>
<mac address='52:54:00:b6:9b:91'/>
<ip address='192.168.122.1' netmask='255.255.255.0'>
<dhcp>
<range start='192.168.122.2' end='192.168.122.254'/>
</dhcp>
</ip>
</network>
2 years, 3 months
Re: How to get Fedora 35 to use DNS name as hostname?
by Petr Menšík
On 1/17/22 05:40, Tim via users wrote:
> On Sun, 2022-01-16 at 15:53 -0600, Thomas Cameron wrote:
>> All of a sudden with F35, no matter what the address of the VM is,
>> its hostname is set to fedora. Just fedora. Not
>> fedora.tc.camerontech.com.
> I see your pain, that doesn't really work well when you have several
> Fedora PCs, does it? (I'm Spartacus, and I'm Spartacus, too.)
>
> My quirky humour would have put into the install routine a "name your
> computer" question. And if you didn't, it'd randomly pick a name from
> a list to each computer (George, Fred, Jenny, etc) for you.
>
>
>> I want F35 to have the same behavior as previous versions of Fedora
>> and RHEL and Ubuntu and so on. I don't want to manually set
>> /etc/hostname and monkey with hostnamectl because if the VM gets a
>> new address, I don't want to have to go and change /etc/hostname or
>> anything.
>>
>> I've been poking around with /etc/NetworkManager/NetworkManager.conf
>
> What about customising the dhcp client config? So it accepts the
> hostname name supplied from your DHCP server, or derived from your
> reverse DNS lookup, and passes it to whatever is setting the hostname
> on Fedora these days.
>
> Like you, that's what I expect to happen, *unless* the user specifies
> otherwise.
dhcp server of libvirt is dnsmasq. It would provide hostnames when it
has matching dhcp-record with IP and name (and hwaddr). With libvirt,
that would be set by <ip><dhcp><host name='whatever'> in network
configuration xml. I think it should use also /etc/hosts of the host.
But dnsmasq can assign lease just by name if hwaddr is not present in
static leases. But that requires static hostname on Fedora side to be
sent to the server.
How does virsh net-dumpxml <network> look like?
--
Petr Menšík
Software Engineer
Red Hat, http://www.redhat.com/
email: pemensik(a)redhat.com
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB
2 years, 3 months
Re: How to get Fedora 35 to use DNS name as hostname?
by Petr Menšík
On 1/17/22 11:27, Tim via users wrote:
> On Mon, 2022-01-17 at 08:42 +0100, Peter Boy wrote:
>> The default configuration rather follows the opposite principle. The
>> hostname should be well defined and independent of changing IP
>> addresses.
> I sort-of go along with that. If you've set a hostname, there's sense
> in it not getting changed. On the other hand, if you use a DHCP server
> to centrally manage the allocation of addresses, you might also want it
> (or your DNS server) to control hostnames. I do. Some devices on my
> network obey naming instructions from the DHCP &/or DNS servers, others
> ignore it.
>
I think it might make more sense to correctly detect hostname during
installation. If you define hostname on installation from network, it
should be kept. I expect it should keep the same hostname during
reboots. I think only diskless terminals may want always obtaining
hostname on every boot. Anything storing state on local disk should want
to keep its name.
I think more tight integration with libvirt names would be useful. I
admit I know little of that. I usually define name AFTER installation
for my VMs, which would not work with what I propose. I would like easy
way to set hostname from libvirt during installation. I don't need
always fixed IP, but I want fixed DNS name for given VM. I expect that
is common requirement.
dnsmasq from libvirt would provide hostname to machine in case it has
static lease for given DUID/hwaddr. Is there tool to create static lease
from machine name on VM creation? For example libvirt can detect name of
distribution from ISO image. It would be nice if it could propagate it
forward.
I am afraid I did not help much.
Regards,
Petr
--
Petr Menšík
Software Engineer
Red Hat, http://www.redhat.com/
email: pemensik(a)redhat.com
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB
2 years, 3 months
Re: How to get Fedora 35 to use DNS name as hostname?
by Sam Varshavchik
Peter Boy writes:
> > Am 17.01.2022 um 16:22 schrieb Sam Varshavchik <mrsam(a)courier-mta.com>:
> >
> > Peter Boy writes:
> >
> >> Usually you set the static hostname once using "hostnamectl set-hostname
> <FQDN>“. „fedora“ is the transient hostname. DHCP client uses the static
> hostname to request an IP.
> >>
> >> But maybe I didn't get what exactly you want to do.
> >
> > dhcpd's configuration file uses MAC addresses to assign reserved IP
> addresses to specific DHCP clients. It doesn't matter what hostname the
> client sends.
>
> Yes, my wording was way too short. It uses the static hostname to enter the
> IP generated for the MAC address along with the hostname into the DNS part
> (in dnsmasq, which is used in Fedora KVM/libwirt) that is used to retrieve
> the hostname.
Ok, so this is basically trusted DDNS stacked on top of DHCP.
> But Thomas uses a static host table, so the DNS delivered hostname is
> independent from any MAC address and any transient or static hostname of the
> client.
It should be possible to hack up a script that gets run when an IP address
is assigned that does a reverse IP lookup and sets the hostname. However
that should be done in a manner that does not permanently save the hostname
so that it gets reverted to a static stub name on the next reboot.
2 years, 3 months
Re: How to get Fedora 35 to use DNS name as hostname?
by Peter Boy
> Am 17.01.2022 um 16:22 schrieb Sam Varshavchik <mrsam(a)courier-mta.com>:
>
> Peter Boy writes:
>
>> Usually you set the static hostname once using "hostnamectl set-hostname <FQDN>“. „fedora“ is the transient hostname. DHCP client uses the static hostname to request an IP.
>>
>> But maybe I didn't get what exactly you want to do.
>
> dhcpd's configuration file uses MAC addresses to assign reserved IP addresses to specific DHCP clients. It doesn't matter what hostname the client sends.
Yes, my wording was way too short. It uses the static hostname to enter the IP generated for the MAC address along with the hostname into the DNS part (in dnsmasq, which is used in Fedora KVM/libwirt) that is used to retrieve the hostname.
But Thomas uses a static host table, so the DNS delivered hostname is independent from any MAC address and any transient or static hostname of the client.
> I suppose that the DHCP server might keep track of hostnames and for MAC addresses that don't have fixed IP addresses it might use the client's hostname to keep leasing out the same IP address, if possible. But the same can be done with MAC address entirely, instead of hostnames, too.
At least dnsmasq does not, but relies on the MAC address alone.
Peter
2 years, 3 months
Re: OT: Linux kernel version in fiber modem
by Jonathan Ryshpan
On Sat, 2021-12-25 at 03:15 -0800, Jonathan Ryshpan wrote:
> On a whim I opened up the:
> Legal Disclaimer Open Source Licenses
> in the management page for my fiber modem (ATT installed 2021/03/30)
> and discovered that the kernel is rather old:
Since this seems to have produced a modest amount of interest, I'm
posting a little more of this license file; the whole file is about 0.5
Mbytes, which seems a little long.
The modem was provided to me by ATT when they installed fiber service;
I haven't checked but I suspect that it's the only device that ATT
supports and very likely the only one that works on the ATT network.
This very long list of open source software very likely contains more
vulnerabilities.
----------------------------------------- ATT License File Starts ----
-------------------------------------
# BGW320 version 1.0 OPEN SOURCE SOFTWARE INFORMATION
For instructions on how to obtain a copy of any open source code being
made publicly available by AT&T;
related to open source software used in the BGW320 gateway, you may
send your request in writing to:
AVP, RG Software
Open Source Request
AT&T;
2230 E Imperial HWY
El Segundo CA 90245
This document contains additional information regarding open source
software licenses, acknowledgments
and required copyright notices for open source packages used in the
BGW320 device.
radvd - Version 2.18
libssl - Version 1.1.1k
motopia - ssl_api.c
openssl - Version 1.1.1k
dropbear - Version 2013.62
portmap - Version 6.0
tcp_wrappers - Version 7.6
libtecla - Version 1.6.2
pcre - Version 8.32
dhrystone - Version 2.2
flex - Version 2.5.4
aiccu - Version 20070115
motopia - list.h
mcproxy - mcp_util.c
miniupnpd
voip resolver - resolverapi.h
voip resolver - resolverapi.c
portmap - Version 5beta
SpryAssets
lua - Version 5.4.0
expat - Version 2.1.0
public include - pcp.h
cms_util - pcp.c
dhcp-isc - Version 4.1-ESV-R8
dhcpcd
motopia - md5.h
motopia - list.c
motopia - md5.c
muhttpd - Version 1.1.5
smartdb system - broadcom.c
voip SIP - sha1.c
voip SIP - sha1.h
dhcp - Version 4.1-ESV-R3
mini_httpd - Version 1.19
dhcpcd - ifaddrs.c
ez-ipupdate - md5.c
libmnl - Version 1.0.3
dhcpv6
dhcpv6 - ifaddrs.c
public include - cms_lzw.h
cms_util - base64decode.c
cms_util - base64encode.c
cms_util - lzw_decode.c
voip resolver - resolverprivate.c
widedhcpv6 - Version 20080615
widedhcpv6 - ifaddrs.c
uClibc - Version 0.9.28.3
arptables - Version 0.0.3-4
inetd - inetd.c
kernel - include
motopia-arm
netfilter
zl880 - arris_lt.c
bcmdriver include - adsldrv.h
bcmdriver include - AdslMibDef.h
bcmdriver include - atmapidrv.h
bcmdriver include - bcmadsl.h
bcmdriver include - bcmatmapi.h
bcmdriver include - bcmxdsl.h
bcmdriver include - DiagDef.h
bcmdriver include - VdslInfoDef.h
bdmf
dpi
pcmshim
rdpa_drv
rdpa_gpl
rdpa_mw
opensource include - bcmspucfg.h
opensource include - bcmspudrv.h
opensource include - bcmtypes.h
opensource include - board.h
bcmdrivers - enet
bcmdrivers - wfd
bcmdrivers - xtmrt
linux kernel - Version 3.4.11
bridge-utils - Version 1.2
busybox - Version 1.30.1
conntrack-tools - Version 1.4.1
dnsmasq - Version 2.85
dproxy-nexgen - Version 0.5
ebtables
ez-ipupdate - Version 3.0.11b7
ftpd - Version 1.0.24
haserl - Version 0.9.35
iproute2
iptables - Version 1.4.16.3
mtd-util - flash_eraseall.c
mtd - Version 1.5.0
ntfs-3g - Version 2014.3.15
ntpclient - Version 2010_356
rp-pppoe - Version 3.11
sysstat - Version 9.0.3
urlfilterd - Version 1.0.1
libnetfilter_conntrack - Version 1.0.3
libnetfilter_cthelper - Version 1.0.0
libnetfilter_cttimeout - Version 1.0.0
libnetfilter_queue - Version 1.0.2
libnfnetlink - Version 1.0.1
bcm_boot_launcher.c
bdmf_shell
memaccess.c
ppp - Version 2.3.11
psictl.c
scratchpadctl.c
send_cms_msg.c
simcard
public - include
cms_boardctl
cms_msg
cms_util
motopia
portmirror
prioritytag
udev - Version 136
bridge-utils - Version 1.0.6
iproute2 - Version 2.6.35
mtd - Version 20050122.orig
ntpclient - Version 2010_365
wireless_tools - Version 29
wpa_supplicant - Version 1.1
hostapd
compat.h
bootcfg.ko
pm_interval.ko
emaclib.ko
wlan.ko
wlan_ccmp.ko
wlan_scan_ap.ko
wlan_scan_sta.ko
wlan_tkip.ko
wlan_xauth.ko
xt_mark.ko
queue.h
linux kernel - Version 2.6.35.12
U-Boot - Version 2009.06
PHP - Version 5.0.5
zlib - Version 1.2.11
zlib - Version 1.2.3
dhcpcd - ifaddrs.h
dhcpv6 - ifaddrs.h
radvd - ifaddrs.h
mocana - parseasn1.c
smartdb system - etc53xx.h
widedhcpv6 - ifaddrs.h - Version 1.1.1.1
popt - Version 1.16
Process Control Daemon (PCD) - Version 1.1.6
syslog-ng - Version 3.8.1
eventlog - Version 0.2.12
glib - Version 2.40.0
logrotate - Version 3.11.0
libffi - Version 3.2.1
libuuid - Version 1.0.3
md5.js - Version 2.2
safeclib - Version 10052013
Argon2 - Version 1.3
curl - Version 7.70.0
ncurses - Version 6.1
mtr - Version 0.93
dbus - Version 1.10.8
systemd - Version 243
libfuse - Version 3.10.2
libattr - Version 2.4.48
util-linux - Version 2.36
----------------------------------------- ATT License File Ends ------
-----------------------------------
--
Sincerely Jonathan Ryshpan <jonrysh(a)pacbell.net>
Fiat justitia, ruant coelis!
2 years, 3 months
Re: OT: Linux kernel version in fiber modem
by Jamie Fargen
There was an article that compared linux based DIY routers with off the
shelf home routers and the numbers were pretty conclusive. A basic x86
processor from Intel or AMD is much more powerful than most of the low cost
MIPs processors shipped in consumer routers. Why is something more powerful
needed? Because the low cost MIPs processors cannot more than a few tens of
megabits per second. Here is the article
https://arstechnica.com/gadgets/2016/01/numbers-dont-lie-its-time-to-buil...
.
The ISP in my area installs an ONT on the side of your home, it is
basically a powered fiber optic to ethernet transceiver and a couple of
things, and your home router can be plugged directly into this optical
transceiver via CAT6.
You can run the basic services necessary on the DIY router to run your home
network, for very basic home network just DHCP & DNS server, and that can
be accomplished using the service dnsmasq. If you need wifi you can plug a
port from your DIY router into a LAN port of the wifi router (first disable
the DHCP service on the wifi router) and use it as a wifi bridge to your
DIY router.
This architecture has some other benefits, the main benefit being
flexibility. Since the DIY router is running your favorite linux distro you
can host other services. An key additional service I have tossed on the DIY
router is VPN to provide connectivity back to my home network to provide
better privacy and security when using public/untrusted wifi networks using
Wireguard (could also use Openvpn or IPSec). Though I agree there are some
security implications and running these sevices on an internet connected
device is not suitable for a corporate environment, but for your home usage
can even attach some storage and the DIY router can also act as a CIFS/NFS
server or can run services like OwnCloud/NextCloud.
I've used three APU2* devices from http://pcengines.ch for different
projects and they have worked well. They are low power, I believe they run
at 12 watts max, have 4 core AMD processors (supposed to be powerful enough
to NAT at 1Gb/sec), 4GB ram, a couple of gigabit ports, PCMCIA, USB, and
possibly eSATA. There is no fan or moving parts, I have dropped one or two
APU2s on hard surfaces and they have not shown any failure (just a dead
AC/DC adapter after a severe electrical storm), they are pretty much rock
solid.
Regards,
-Jamie
On Mon, Dec 27, 2021 at 9:16 PM Tim via users <users(a)lists.fedoraproject.org>
wrote:
> On Mon, 2021-12-27 at 17:35 -0600, Roger Heflin wrote:
> > I have always ran my own router behind the ISP's firewall/modem. I
> > usually DMZ my personal router's ip address and then rely on the
> > security of my own newer router that I have full control of.
> >
> > I also forward ports to my server so that it can provide my public ip
> > services via the router I have supplied. I also always turn off the
> > wifi on the vendor's device (or if possible don't get wifi on the
> > vendor's device at all if that is an option).
>
> I had tried that, but performance was dire. That could just be the
> combination of those particular devices. If my old modem/router packs
> it in, I'll just buy a decent one directly from someone other than my
> ISP.
>
> > George:
> > switches will forward just about any underlying packets at the layer
> > 2 level, they don't care about protocols at all, and generally it
> > takes an expensive switch to even look at protocols. But it is
> > possible that the new switch does not support 10base-t and the set
> > top boxes may need something ancient like that.
>
> I was thinking it's more likely to be something like UPnP. Though it
> could be at the remote end.
>
> All the smart devices I have run at 100 mb/s ethernet, none run at 10
> mb/s or 1 gb/s.
>
> All of which went dumb a while ago, for several days, when something at
> Sony stopped working, and they go into stupid-mode when they can't
> authenticate with their mummy. I have a sony TV, and several Sony
> bluray/smart set-top boxes for various TVs. The TV deleted all the
> channels associated with the ABC, no streaming playing from any
> services on any devices, the devices wouldn't store their settings,
> even playing DVDs required mucking around, unplugging the power to be
> able to eject a disc. A few days later on, they all went good again.
>
> You might just want to try switching your network around, now, for the
> set-top boxes, and see if it behaves any differently.
>
> --
>
> uname -rsvp
> Linux 3.10.0-1160.49.1.el7.x86_64 #1 SMP Tue Nov 30 15:51:32 UTC 2021
> x86_64
>
> Boilerplate: All unexpected mail to my mailbox is automatically deleted.
> I will only get to see the messages that are posted to the mailing list.
>
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>
2 years, 3 months
Re: f35 initial impressions
by Tom Horsley
On Fri, 5 Nov 2021 07:28:41 +0800
Ed Greshko wrote:
> Could you provide more detail about that? I've not seen any problems.
> But maybe I'm not using those features that are no longer supported.
If I try to use it basically unaltered other than adding some
forwarding directives, it pays absolutely no attention to my local
zone files. If I copy the older config files that worked at one time, I get
deprecated messages about managed-keys versus trust-anchors. It worked
with those errors in fedora 34, but in 35 copying the old config files
gives me those errors plus bazillions of log messages about things
unreachable on the network and it also doesn't serve any of my local
lan names. I'm unlikely to be any more exact since the 8,721 pages
of documentation were too much to understand.
Instead I now have an 11 line dnsmasq.conf file which together
with an /etc/hosts file does everything I want, so deeper examination
of bind isn't on the horizon :-).
2 years, 5 months
Re: f35 initial impressions
by Clifford Snow
I updated a laptop to Fedora 35 using a Software application after doing a
complete backup. So far everything is working as expected. I'm running
Gnome 41 with wayland. Past upgrades to Postgresql and PostGIS have been
problematic, usually involving moving to the next major release. The minor
upgrade to Postgres from 13.3 to 13.4 was no problem. PostGIS
version stayed the same.
I used the Fedora linux updates indicator on the Gnome Shell on my
workstation. It still doesn't work with wayland which is running on this
laptop.
So far everything else works beautifully. Kudo's to all the developers.
That's why I love Fedora.
Clifford
On Thu, Nov 4, 2021 at 2:43 PM Tom Horsley <horsley1953(a)gmail.com> wrote:
> I installed fedora 35 on one machine using the dnf upgrade
> process and on another machine from scratch followed by manual
> configuration to copy previous install. Both seem to be
> working well. The missing arduino stuff doesn't seem to be
> used as I can still compile the Marlin firmware successfully
> without it.
>
> Had severe problems getting bind to work as my local LAN DNS
> provider, every release seems to have brought more "deprecated"
> messages, so I finally chucked it and switched to dnsmasq.
> Clearly I should have done that long ago, it works great and
> it vastly simpler to configure. Haven't found anything else
> busted yet.
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>
--
@osm_washington
www.snowandsnow.us
OpenStreetMap: Maps with a human touch
2 years, 5 months
f35 initial impressions
by Tom Horsley
I installed fedora 35 on one machine using the dnf upgrade
process and on another machine from scratch followed by manual
configuration to copy previous install. Both seem to be
working well. The missing arduino stuff doesn't seem to be
used as I can still compile the Marlin firmware successfully
without it.
Had severe problems getting bind to work as my local LAN DNS
provider, every release seems to have brought more "deprecated"
messages, so I finally chucked it and switched to dnsmasq.
Clearly I should have done that long ago, it works great and
it vastly simpler to configure. Haven't found anything else
busted yet.
2 years, 5 months
