RE: Problems doing a ks over NFS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



From: kickstart-list-bounces@xxxxxxxxxx
[mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Philip Rowlands
[snip]

> Are you sure the DHCP relay is working? What happens outside of a
kickstart 
> install?

> Are you sure that NFS is working? What happens outside of a kickstart
install?

> [repeat as necessary; try doing a manual install and note at which
point it breaks]

Well I would think that since I see messages on the kickstart server
FROM the dhcprelay server, that this would imply things are kinda sorta
working, yes. As for NFS, yes I know that's working as I can do a 'same
vlan' kickstart over NFS and that works fine. I just keep seeing this on
the dhcp/kickstart/repo server whenever I attempt to do a box on another
subnet:

Dec 19 09:22:03 yum1 dhcpd: DHCPDISCOVER from 00:30:48:29:c9:55 via
192.168.20.58: unknown network segment
Dec 19 09:22:05 yum1 dhcpd: DHCPDISCOVER from 00:30:48:29:c9:55 via
192.168.20.58: unknown network segment
Dec 19 09:22:06 yum1 dhcpd: DHCPINFORM from 192.168.20.160 via eth1:
unknown subnet 192.168.20.58
Dec 19 09:22:09 yum1 dhcpd: DHCPDISCOVER from 00:30:48:29:c9:55 via
192.168.20.58: unknown network segment
Dec 19 09:22:14 yum1 dhcpd: DHCPINFORM from 192.168.20.160 via eth1:
unknown subnet 192.168.20.58
Dec 19 09:22:17 yum1 dhcpd: DHCPDISCOVER from 00:30:48:29:c9:55 via
192.168.20.58: unknown network segment
Dec 19 09:22:22 yum1 dhcpd: DHCPINFORM from 192.168.20.160 via eth1:
unknown subnet 192.168.20.58
Dec 19 09:22:30 yum1 dhcpd: DHCPINFORM from 192.168.20.160 via eth1:
unknown subnet 192.168.20.58

The server 20.58 is a dhcp-relay server.

Thanks again for any assistance
Michael Weiner


[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux