Description of problem:
Yesterday while setting up a system for SR-IOV testing I realized that system-config-network-* is gone and there seems to be no replacement for it on the commandline. In short this means there's no way of configuring network interfaces on the commandline apart from editing /etc/sysconfig/network-scripts/ifcfg-eth* by hand. It's a big step backwards from RHEL5. What's even worse is the case where one adds network hardware to the system and has no graphical NetworkManager at hand. In that case the only way to get your network card setup is by creating a ifcfg-eth file by hand. Seriously, it's a big problem.
Here's a sample ifcfg-eth0, that the user would have to write for every added network card. There's a lot of stuff you can get wrong.
Maybe there is a tool to do this configuration, so far I spoke to gospo and prarit but they didn't know of any.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
*** Bug 602265 has been marked as a duplicate of this bug. ***
At least the CLI part of system-config-network is coming back; reassigning to system-config-network to get Fixed In Version updated.
system-config-network-tui is back in the trees, so given Devel ACK, added Fixed in Version and put to modified.
Thanks & regards, Phil
I do not think that this report is a dulicate of Bug 602265.
Like I see at RHEL5 system-config-network-tui the tui do not allow configure
DSL. ISDN can only configure a connection to an internet provider.
We need for ISDN D-cannel callback and use static ip configurations for our
All this options allow the system-config-network gui to configure.
system-config-network-tui is only helpful for ethernet interfaces.
Basic sanity test done.
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.