@sebastian-roth Ahh, I didn’t see that either. Okay, so in DHCP I changed the router to 192.168.22.1 and range starting IP to .20
In fogsettings, I changed both routeraddress and plain router from 192.168.22.11 to 22.1
The test client gets online just fine now.
Thank you again, Sebastian!
@sebastian-roth said in No Subnet Declaration for virbr0 After Upgrade to 1.5.9:
Does this gateway provide DNS as well? Either as a DNS service or by relaying the DNS queries to an upstream DNS server?
It must be, because this Fogserver instance is more than 2 years in production and has always worked great. Before upgrading to 1.5.9, the Fogserver and DHCP clients under it had internet access. After the upgrade, the Fogserver gets internet access/resolves webpages while the DHCP clients under it get LAN with “no internet access” though they can ping external sites.
I just rebooted everything and there’s still no resolution.
@sebastian-roth 192.168.22.1 is the Gateway IP/Subnet for the VLAN 22 this Fogserver is connected to. The main Gateway IP/Subnet/Name Server is 192.168.1.1.
The Fogserver surfs the web just fine, though DHCP clients don’t.
eth0 DNS address is set to Automatic.
@sebastian-roth Yes, I am using eth0 and DHCP works great. The problem is the clients don’t have internet access. They can ping external sites but webpages don’t load/resolve.
Here’s a screenshot of the Windows network diagnostic:
Fogserver is a VM in Synology Virtual Machine Manager and tagged to a VLAN (22)
Message:
No subnet declaration for virbr0 (192.168.122.1). Ignoring requests on virbro. If this is not what you want, please write a subnet declaration in your dhcpd.conf file for the network segment to which interface virbr0 is attached.
Here’s the output of ip a s
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 02:11:32:24:8f:86 brd ff:ff:ff:ff:ff:ff
inet 192.168.22.11/24 brd 192.168.22.255 scope global noprefixroute eth0
valid_lft forever preferred_lft forever
inet6 fe80::9db3:f0a1:fdc2:e7fc/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 52:54:00:a0:be:be brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 1000
link/ether 52:54:00:a0:be:be brd ff:ff:ff:ff:ff:ff
and content of /etc/dhcp/dhcpd.conf
# DHCP Server Configuration file\n#see /usr/share/doc/dhcp*/dhcpd.conf.sample
# This file was created by FOG
#Definition of PXE-specific options
# Code 1: Multicast IP Address of bootfile
# Code 2: UDP Port that client should monitor for MTFTP Responses
# Code 3: UDP Port that MTFTP servers are using to listen for MTFTP requests
# Code 4: Number of seconds a client must listen for activity before trying
# to start a new MTFTP transfer
# Code 5: Number of seconds a client must listen before trying to restart
# a MTFTP transfer
option space PXE;
option PXE.mtftp-ip code 1 = ip-address;
option PXE.mtftp-cport code 2 = unsigned integer 16;
option PXE.mtftp-sport code 3 = unsigned integer 16;
option PXE.mtftp-tmout code 4 = unsigned integer 8;
option PXE.mtftp-delay code 5 = unsigned integer 8;
option arch code 93 = unsigned integer 16;
use-host-decl-names on;
ddns-update-style interim;
ignore client-updates;
# Specify subnet of ether device you do NOT want service.
# For systems with two or more ethernet devices.
# subnet 136.165.0.0 netmask 255.255.0.0 {}
subnet 192.168.22.0 netmask 255.255.255.0{
option subnet-mask 255.255.255.0;
range dynamic-bootp 192.168.22.10 192.168.22.254;
default-lease-time 21600;
max-lease-time 43200;
option routers 192.168.22.11;
option domain-name-servers 192.168.22.1;
next-server 192.168.22.11;
class "Legacy" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000";
filename "undionly.kkpxe";
}
class "UEFI-32-2" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002";
filename "i386-efi/ipxe.efi";
}
class "UEFI-32-1" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006";
filename "i386-efi/ipxe.efi";
}
class "UEFI-64-1" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007";
filename "ipxe.efi";
}
class "UEFI-64-2" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008";
filename "ipxe.efi";
}
class "UEFI-64-3" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009";
filename "ipxe.efi";
}
class "SURFACE-PRO-4" {
match if substring(option vendor-class-identifier, 0, 32) = "PXEClient:Arch:00007:UNDI:003016";
filename "ipxe.efi";
}
class "Apple-Intel-Netboot" {
match if substring(option vendor-class-identifier, 0, 14) = "AAPLBSDPC/i386";
option dhcp-parameter-request-list 1,3,17,43,60;
if (option dhcp-message-type = 8) {
option vendor-class-identifier "AAPLBSDPC";
if (substring(option vendor-encapsulated-options, 0, 3) = 01:01:01) {
# BSDP List
option vendor-encapsulated-options 01:01:01:04:02:80:00:07:04:81:00:05:2a:09:0D:81:00:05:2a:08:69:50:58:45:2d:46:4f:47;
filename "ipxe.efi";
}
}
}
}
@sebastian-roth The kernel update works now and image capture is successful.
I’ll start a new topic on the networking issue.
Thanks Sebastian!
@sebastian-roth Okay, I did misunderstand the fogstorage piece, thank you. I set it back to fagmaster and re-ran the installer. Everything went well and Fog is now up to date, however, now dhcpd has an error:
No subnet declaration for virbr0 (192.168.122.1). Ignoring requests on virbro. If this is not what you want, please write a subnet declaration in your dhcpd.conf file for the network segment to which interface virbr0 is attached.
I updated the TFTP FTP username from fog to fogproject and the kernel update succeeded.
I then re-ran the installer, which updated the database credentials to fogstorage. I re-ran the installer after updating the settings file with the fogstorage credentials, and receive a new error at the end of the install:
HTTP request sent, awaiting response… 500 Internal Server Error
Error 1142 (42000) at line 1: INSERT,UPDATE command denied to user ‘fogstorage’@‘localhost’ for table ‘globalSettings’
I’m still able to login, the database looks good the instance says that everything is up to date.
I don’t have anything on the bench to test with, so will do that a little later today.
@sebastian-roth I used git clone https://github.com/FOGProject/fogproject.git to get the installer.
There is a Linux account named fogproject.
ls -al /images/ shows dates through the end of 2020…apparently I haven’t uploaded any images yet in 2021.
@sebastian-roth I’m currently using 1.5.7 and the installer I used was downloaded today.
The “fog” user is to login to the webGUI and there is a fogproject user in CentOS
When reviewing the article on resyncing FOG’s service account, I do get the ftp login error when attempting to update to the latest kernel, though I can capture images without any errors. The kernel update error is the only one I see. Should I still run through the resyncing procedures?
Thanks!
The Fogserver works great, just trying to update the kernel to work with new clients and receive error:
Type: 2, File: /var/www/html/fog/lib/fog/fogftp.class/php, Line: 464, Message: ftp_login(): Login incorrect,. Host: xxx.xxx.xx.xx, Username: fog
Saw another post that said to update and re-run the installer. When I do that, I receive this error:
The installer was not able to run all the way to the end…
Job for mariadb.service failed because the control process exited with error code.
mariadb.service status is active (running) and I don’t see anything negative in journalctl -xe
Here are the screenshots your requested
I’m still around, sorry for my late reply as well!
My problem is actually the opposite of your test and is in associating multiple images to one DMI value.
For a given DMI value (motherboard model number) we have images for Win 7, 10, Home, Pro…etc.
When I add an image association to a given DMI result, any pre-existing association is removed and the new one is the only one.
I’ll test the database and give the outputs shortly.
Thank You!
I’ve setup a new fog 1.5.5 on Ubuntu 18.04.1 and all is working great other than Capone will not associate more than one image with a given DMI result. When I add an association to a DMI result that already had one, only the new one is displayed and the old one is gone. I’ve tested this on the imaging side just to be sure, and changing the association only changes the image that is automatically deployed to the host.
I used Capone extensively in the past and know it did accept multiple entries and confirmed as much on the wiki:
https://wiki.fogproject.org/wiki/index.php?title=Plugins:_Capone
“It is possible to have multiple matching entries per DMI result. So for example you could have to associations for response 112233. In this case, at the console on the client computer you will be prompted for which image you would like to use.”
This is the behavior I’m used to and need to work again.
How do I make this work again?
Thank You!