| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Rewrite disabled network configuration scripts in loader if we ask the
user to retry network configuration. nm-system-settings will pick up
the change to those files and down those interfaces.
|
|
|
|
|
|
| |
In kickstartNetworkUp(), call is_nm_connected() to see if we are in
NM_STATE_CONNECTED. If we are in any other state, prompt for network
configuration and start NetworkManager.
|
|
|
|
|
|
| |
This reverts commit 5a0189827c1c6db21ecbfd01f00ee1f5edbb7a77.
gcc-4.4.0-0.31 in rawhide fixes the problem we were seeing.
|
|
|
|
|
|
|
|
|
| |
Problem with -O2 and some string functions with the latest version of
gcc in rawhide. Work around the problem for now so we can compile,
ideally we can revert this patch in the future.
gcc bug:
https://bugzilla.redhat.com/show_bug.cgi?id=492973
|
|
|
|
|
| |
If we need to ask the user which NIC to use and are in cmdline mode,
tell them we cannot do that and exit.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes network bringup in loader.
In a normal env, something like GTK processes all the dbus messages
as part of it's main loop. We don't have anything like that in
loader so we have to turn that crank manually, and enough times to
clear out all the pending messages.
Signed-off-by: David Cantrell <dcantrell@redhat.com>
|
|
|
|
|
|
|
| |
If asprintf() errors, it returns -1. Check for that correctly and
return 20 on error.
[rawhide]
|
|
|
|
|
|
| |
Rather than getting the NetworkManager state over D-Bus, use the
libnm_glib library to get the same information. Less verbose
code that way.
|
| |
|
|
|
|
|
|
| |
In NetworkManager-world, we want the GATEWAY to be store per device
rather than for the entire system, so what ifcfg-fedora is reading
is the correct thing to do.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Restores functionality we had before the NM changeover. This was
originally requested by gurulabs.com. Instead of sending just
'anaconda' as the vendor class identifier, send something like:
anaconda-Linux 2.6.27.5-117.fc10.i686 i686
Of course, if we fail to collect that information, fall back on
'anaconda'. Guru Labs wanted this functionality for PXE booting
as it allowed them to more easily control per-client/per-release
settings from the DHCP server. My fault for not adding this back
when the NM changeover happened.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This one has been around for a while. If a user selects the wrong
network interface in loader and waits for the failure message to
appear, they are taken back to the 'select an interface' screen.
They select the right interface, but loader used the TCP/IP settings
entered the first time around.
On network configuration failure and if we are doing an interactive
install, blank out ipv4method and ipv6method so that we take the
user to the TCP/IP configuration screen. I use ipv4method and
ipv6method to figure out if a kickstart installation is beginning,
so by blanking them out for the interactive install case, we get to
take the user back to the TCP/IP settings screen.
|
|
|
|
|
|
| |
Make the loader code match the behavior of the anaconda Python
code. Only write NM_CONTROLLED=no. If a device is controlled
by NM, don't write an NM_CONTROLLED line.
|
|
|
|
|
|
| |
Was using DEBUGLVL for all of the D-Bus messages. Make sure error
messages are at the ERROR log level and info-type messages are at
the INFO log level.
|
|
|
|
|
|
| |
If the user passes dhcpclass= at the boot prompt, write the value
to /etc/dhclient-DEVICE.conf as 'send vendor-class-identifier %s'
so that NM will use those settings when sending the DHCP request.
|
| |
|
|
|
|
|
|
| |
Kickstart installs should work again like they did at one point.
If you do not specify IP configuration parameters on the boot:
line, loader assumes DHCP (which is what we've done forever).
|
|
|
|
|
|
| |
Writing to /.tmp proved to work, now to move the temporary files to a
better location. Using /etc/sysconfig/network-scripts, but writing
the files as ".ifcfg-DEVICE" and then renaming to ifcfg-DEVICE.
|
|
|
|
|
|
| |
Clean up the loop termination and return value handling. Currently
the configureTCPIP() function returns LOADER_NOOP if the user
chose dhcp and LOADER_OK if the user chose manual configuration.
|
|
|
|
|
|
|
|
|
| |
I was told by upstream that NM_CONTROLLED= should be sufficient
for nm-system-settings to pick up an interface for control. But
the parsing in the ifcfg-fedora plugin for nm-system-settings is a
little strange (shvar.c) and what happens when NM_CONTROLLED is
empty isn't entirely clear. Set it to yes to avoid any possible
problems.
|
|
|
|
|
| |
The ipv4method and ipv6method variables are in use now, remove
flags that are not used anymore.
|
|
|
|
|
|
|
| |
Rather than writing new config files directly in /etc/sysconfig
in writeEnabledNetInfo(), write them to /.tmp first and then move
them in place using rename(2). Why /.tmp? rename() fails across
different filesystems and this was the path of least resistance.
|
| |
|
|
|
|
|
|
|
|
| |
Back with libdhcp, we needed to call pumpDhcpClassRun() in several
locations. Moving to NM, I converted those calls to be calls to
get_connection() instead. In this patch, the call to get_connection
in configureTCPIP() has been eliminated because we should only be
calling it from readNetConfig().
|
| |
|
|
|
|
|
|
|
|
| |
If you pick the wrong interface in anaconda and NM times out, you
are placed at the configure TCP/IP screen again. If you select
Back, you can go back and pick another interface (if you have more
than one). Users going back to select a new interface were seeing
segfaults, which is not what we want.
|
|
|
|
|
| |
This correctly brings over static IP settings. Went ahead and
added code for more IPv6 values, but those are disabled for now.
|
|
|
|
| |
Call res_init() after NetworkManager says we are connected.
|
|
|
|
|
|
|
|
|
|
| |
Fix some problems with the interaction between kickstartNetworkUp()
and setupNetworkDeviceConfig(). Do not assume dhcp and do not
assume that a setting has been provided. Hopefully this will let
people specify manual settings when doing a ks install.
Renamed setupNetworkDeviceConfig() to setupIfaceStruct(), since
that's really what it's doing now.
|
|
|
|
|
| |
Wrapping more IPv6 code in ENABLE_IPV6 since NM does not yet
support IPv6.
|
| |
|
|
|
|
|
|
|
| |
NetworkManager lacks IPv6 support at the moment, so disable the
IPv6 interface widgets in loader for now. We're string frozen, so
the manual IP entry screen in loader still tells you to enter an
IPv4 or IPv6 address. Ooops.
|
|
|
|
|
|
| |
For static network configuration, make sure we write out
the netmask and broadcast correctly (was writing out IP
address for those settings) to the ifcfg-DEVICE file.
|
|
|
|
|
|
|
| |
Correct the manual settings form loop in loader. Do not tell
users they must have IPv6 settings when they disabled IPv6.
Also, do not tell users they are missing IPv4 information when
they filled in all fields.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This patch does two things: (1) It makes sure that NM doesn't run more than
once, though we still need to figure out why it's being asked to start up
several times. (2) Block the rest of the network configuration process from
running until after NM is up and we can talk to it. This fixes the traceback
where nothing is providing the .services file.
We still need to investigate whether static network configuration works and
how the UI flows in error cases.
|
|
|
|
|
|
| |
No need to pass iface_t to iface_start_NetworkManager().
Remove unnecessary else { exit(0); } from the child process.
Increase wait loop to 45 iterations.
|
| |
|
|
|
|
|
| |
Remove debugging functions and DNS code that we don't
need anymore.
|
|
|
|
|
| |
Give NetworkManager a fair amount of time to finish doing
things.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
should be fine since I had originally just copied them into hampton from head :)
|
|
|
|
| |
about these will be coming soon
|
| |
|
| |
|