Well to clarify usually your spacewalk server itself is expected to have at least limited internet access, even if the rest of your servers don't. One method you could use if you don't want to give you spacewalk server full internet access is use a squid proxy to limit what URL's it can access.
Additionally if you are referring to the spacewalk client repo I mirror that to a channel on my spacewalk server and simply include that channel in all my kickstarts and my bootstrap scripts. On Mon, Jan 19, 2015 at 8:52 AM, Joe Belliveau <[email protected]> wrote: > This can be done easily. > > I mirror the packages to a local apache redirect on the spacewalk server… > > It can easily be done. > > —Joe > > > On Jan 19, 2015, at 8:32 AM, Edsall, William (WJ) <[email protected]> wrote: > > Hello list, > > Just a general question about clients. > > > > One reason for my investigation into satellite/spacewalk is due to network > security and lack of internet access to our linux machines. I was surprised > when the spacewalk documentation mentioned external yum installs in order to > get spacewalk ready; was really hoping this was done 100% internal with the > spacewalk server. > > > > So my question is – what’s the best practice to move everything internal? > Can it be done? Should I look further into the bootstrap procedure? > > > > > > > > Thanks, > > William > > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list > > > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
