using a local computer for a remote install of F22...

[Martin Cigorraga]

Why not just install Fedora via the command line?
The installation should be quite straightforward:
1. Partition your remote computer's drive(s)
2. Install Fedora there - for example using systemd-nspawn
3. Generate the GRUB menu

On Mon, Jun 22, 2015 at 1:56 PM Rick Stevens <ricks at alldigital.com> wrote:

> On 06/19/2015 08:36 PM, dwoody5654 wrote:
> > I would like to perform a remote install for F22 but use a computer on
> > the local network for the vnc connection.
> > I have the following in grub:
> >
> > linux /boot/vmlinuz-remote
> > repo=hd:sda4:/Fedora-Server-netinst-i386-22.iso noselinux
> > ks.device=00:00:00:00:000:05 ks=hd:sda4:/ks.cfg --noip6 vnc
> > vncconnect=10.10.1.1 vncpassword=xxxxxx ramdisk_size=8192 panic=30
> >
> > It goes to the internet to find 10.10.1.1.
> > I have 2 nic cards, 1 goes to the internet and the other is for local
> > computers.
> >
> > I have not been able to find the setting I need for the vnc connection
> > to use the local network nic.
> >
> > Is the setting I need go in grub.cfg or in ks.cfg?
>
> Having never done this before, my guess is that with two NICs, you
> need to assign an IP to the NIC that's connecting to the VNC client.
>
> As it stands now, both NICs are going to try to get DHCP IPs. I'm going
> to assume that one NIC is actually seeing a DHCP server and will get
> an IP, DNS and route, the other one (the one connected to the VNC
> client) doesn't get an IP. So the kernel routing table only knows about
> one NIC being up and all traffic is going through it.
>
> I suspect you'll need to add an "ip:" parameter for the NIC connected to
> the VNC client to your boot line. The generic form of the option is:
>
>         ip=<ip>::<gateway>:<netmask>:<hostname>:<interface>:none
>
> So, assuming the NIC's name is "p4p1", something like:
>
>         ip:10.1.1.2:::255.255.255.0::p4p1:none
>
> should set that NIC's IP to 10.1.1.2 with no route, a /24 netmask and
> no hostname. VNC should then know that 10.1.1.1 is connected to that NIC
> and should route accordingly. The other NIC should pick up a DHCP as
> normal.
>
> Again, I've never done this, so this is just a wild guess but seems
> likely.
> ----------------------------------------------------------------------
> - Rick Stevens, Systems Engineer, AllDigital    ricks at alldigital.com -
> - AIM/Skype: therps2        ICQ: 226437340           Yahoo: origrps2 -
> -                                                                    -
> -     I was married by a judge.  I should have asked for a jury.     -
> -                                                   -- Groucho Marx  -
> ----------------------------------------------------------------------
> --
> users mailing list
> users at lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20150623/d4bba1eb/attachment.html>