Hi all,

This is about Fedora 9 but first a little background. Since, the drivers for
the on-board ethernet controller were missing in XP, I had installed a PCI
LAN card. After installing drivers for on-board ethernet, I disabled the PCI
card and now plugged the cable into on-board ethernet controller which is
working fine in XP.
Now when I boot in Fedora, I get a red X indicating problem with the
network. Then I log in as a root, go to Network or Network Device Control
and the following happens.

The PCI card is recognised as eth0 and the on-board is shown as eth1. Then I
deactivate eth0.
Upon activating eth1, it searches for DHCP, gives a beep. Shows Active
status and asks me to restart the pc or the network.
If I do /etc/init.d network restart I get the following error in SELinux
icon.

SELinux is preventing rm (dhcpc_t)"unlink" to ./resolv.conf.Predhclient.eth1
(etc_t)


Even if I manually delete the file resolv.conf.Predhclient.eth1 from /etc
and again do a network restart it gives me an OK message but the red X FAILS
to go away.
Then again the eth1 is shown as INACTIVE.
I physically removed the PCI LAN card.
Did all the steps again but all proved futile.
The SELinux description was too technical for me to understand.

I earnestly request your help to resolve this issue.

Thanks in advance,

Arty

On Thu, 24 Jul 2008 11:18:26 +0530, Artnut wrote:

> Hi all,
>
> This is about Fedora 9 but first a little background. Since, the drivers
> for the on-board ethernet controller were missing in XP, I had installed
> a PCI LAN card. After installing drivers for on-board ethernet, I
> disabled the PCI card and now plugged the cable into on-board ethernet
> controller which is working fine in XP.
> Now when I boot in Fedora, I get a red X indicating problem with the
> network. Then I log in as a root, go to Network or Network Device
> Control and the following happens.
>
> The PCI card is recognised as eth0 and the on-board is shown as eth1.
> Then I deactivate eth0.
> Upon activating eth1, it searches for DHCP, gives a beep. Shows Active
> status and asks me to restart the pc or the network. If I do /etc/init.d
> network restart I get the following error in SELinux icon.
>
> SELinux is preventing rm (dhcpc_t)"unlink" to
> ./resolv.conf.Predhclient.eth1 (etc_t)
>
>
> Even if I manually delete the file resolv.conf.Predhclient.eth1 from
> /etc and again do a network restart it gives me an OK message but the
> red X FAILS to go away.
> Then again the eth1 is shown as INACTIVE. I physically removed the PCI
> LAN card. Did all the steps again but all proved futile. The SELinux
> description was too technical for me to understand.
>
> I earnestly request your help to resolve this issue.
>
> Thanks in advance,
>
> Arty

Just FYI, the issue stands resolved.
Maybe I was being hasty to post the problem some 2 hours back but in the
meantime I kept trying.

**I physically removed the PCI LAN card.

** Selected, the System > Administration > Network option to deleted the
existing eth1. Chose New and the displayed ethernet controller, let it
select the dhcp ip. Saved it and did /etc/init.d network restart.
Yet again it was giving Failed message towards the end but surprisingly
the Network icon rotated, showing some activity and finally displayed
that it found connection!
Checked in XP, as a Root and now as a User. Successful!

Thanks for stopping by.

Regards,

Arty

PS: The restorecon command given in the SELinux message gave a stat error
message during the initial troubleshooting steps.

Artnut wrote:
> Hi all,
>
> This is about Fedora 9 but first a little background. Since, the drivers for
> the on-board ethernet controller were missing in XP, I had installed a PCI
> LAN card. After installing drivers for on-board ethernet, I disabled the PCI
> card and now plugged the cable into on-board ethernet controller which is
> working fine in XP.
> Now when I boot in Fedora, I get a red X indicating problem with the
> network. Then I log in as a root, go to Network or Network Device Control
> and the following happens.
>
> The PCI card is recognised as eth0 and the on-board is shown as eth1. Then I
> deactivate eth0.
> Upon activating eth1, it searches for DHCP, gives a beep. Shows Active
> status and asks me to restart the pc or the network.
> If I do /etc/init.d network restart I get the following error in SELinux
> icon.

Edit your /etc/sysconfig/newtork-srcipts/ifcfg.ethX and set the eth0 to
onboot=no and eth1 onboot=yes.

Edit your /etc/selinux/config and change your SELINUX to
SELINUX=disabled

Reboot and your eth1 should be working properly.


--

//Aho

"J.O. Aho" <user@example.net> wrote in message
news:6eqoecF8fbgfU1@mid.individual.net...
> Artnut wrote:
>> Hi all,
>>
>> This is about Fedora 9 but first a little background. Since, the drivers
>> for the on-board ethernet controller were missing in XP, I had installed
>> a PCI LAN card. After installing drivers for on-board ethernet, I
>> disabled the PCI card and now plugged the cable into on-board ethernet
>> controller which is working fine in XP.
>> Now when I boot in Fedora, I get a red X indicating problem with the
>> network. Then I log in as a root, go to Network or Network Device Control
>> and the following happens.
>>
>> The PCI card is recognised as eth0 and the on-board is shown as eth1.
>> Then I deactivate eth0.
>> Upon activating eth1, it searches for DHCP, gives a beep. Shows Active
>> status and asks me to restart the pc or the network.
>> If I do /etc/init.d network restart I get the following error in SELinux
>> icon.
>
> Edit your /etc/sysconfig/newtork-srcipts/ifcfg.ethX and set the eth0 to
> onboot=no and eth1 onboot=yes.
>
> Edit your /etc/selinux/config and change your SELINUX to
> SELINUX=disabled
>
> Reboot and your eth1 should be working properly.
>
>

Thank you Aho for the solution. Although the issue was resolved, I have a
question.
You suggest that I should disable the SELinux. Now won't that affect the
system security? Will the entire program of SELinux will be disabled or is
it just a particular module that needs to be disabled.

Thanks again,

Arty

"Artnut" <art@yahoo.com> wrote in message news:g69m8m$r7l$1@aioe.org...
>
> "J.O. Aho" <user@example.net> wrote in message
> news:6eqoecF8fbgfU1@mid.individual.net...
>> Artnut wrote:
>>> Hi all,
>>>
>>> This is about Fedora 9 but first a little background. Since, the drivers
>>> for the on-board ethernet controller were missing in XP, I had installed
>>> a PCI LAN card. After installing drivers for on-board ethernet, I
>>> disabled the PCI card and now plugged the cable into on-board ethernet
>>> controller which is working fine in XP.
>>> Now when I boot in Fedora, I get a red X indicating problem with the
>>> network. Then I log in as a root, go to Network or Network Device
>>> Control and the following happens.
>>>
>>> The PCI card is recognised as eth0 and the on-board is shown as eth1.
>>> Then I deactivate eth0.
>>> Upon activating eth1, it searches for DHCP, gives a beep. Shows Active
>>> status and asks me to restart the pc or the network.
>>> If I do /etc/init.d network restart I get the following error in SELinux
>>> icon.
>>
>> Edit your /etc/sysconfig/newtork-srcipts/ifcfg.ethX and set the eth0 to
>> onboot=no and eth1 onboot=yes.
>>
>> Edit your /etc/selinux/config and change your SELINUX to
>> SELINUX=disabled
>>
>> Reboot and your eth1 should be working properly.
>>
>>
>
> Thank you Aho for the solution. Although the issue was resolved, I have a
> question.
> You suggest that I should disable the SELinux. Now won't that affect the
> system security? Will the entire program of SELinux will be disabled or is
> it just a particular module that needs to be disabled.
>
> Thanks again,
>
> Arty
>

Hi all,

Although a few hours back I declared the issue was resolved after confirming
thrice, the problem is recurring much to my consternation. Despite following
the same steps which I did before, am not successful this time around.
Also, in the SELinux message, the solution command of restorcon comes up
with a Stat Error :File not found.
The red X doesn't go away.
/etc/init.d network restart gives an error but ater a while gives all OK but
NO network is available.

What's really missing here? I have already physically removed the PCI LAN
card.
The /etc/sysconfig/network-scripts/ifcfg-eth1 has all requisite settings.
Onboot=yes
IPv6=no
Bootproto=dhcp

TIA,

Arty

Artnut wrote:
> "J.O. Aho" <user@example.net> wrote in message
> news:6eqoecF8fbgfU1@mid.individual.net...
>> Artnut wrote:
>>> Hi all,
>>>
>>> This is about Fedora 9 but first a little background. Since, the drivers
>>> for the on-board ethernet controller were missing in XP, I had installed
>>> a PCI LAN card. After installing drivers for on-board ethernet, I
>>> disabled the PCI card and now plugged the cable into on-board ethernet
>>> controller which is working fine in XP.
>>> Now when I boot in Fedora, I get a red X indicating problem with the
>>> network. Then I log in as a root, go to Network or Network Device Control
>>> and the following happens.
>>>
>>> The PCI card is recognised as eth0 and the on-board is shown as eth1.
>>> Then I deactivate eth0.
>>> Upon activating eth1, it searches for DHCP, gives a beep. Shows Active
>>> status and asks me to restart the pc or the network.
>>> If I do /etc/init.d network restart I get the following error in SELinux
>>> icon.
>> Edit your /etc/sysconfig/newtork-srcipts/ifcfg.ethX and set the eth0 to
>> onboot=no and eth1 onboot=yes.
>>
>> Edit your /etc/selinux/config and change your SELINUX to
>> SELINUX=disabled
>>
>> Reboot and your eth1 should be working properly.
>>
>>
>
> Thank you Aho for the solution. Although the issue was resolved, I have a
> question.
> You suggest that I should disable the SELinux. Now won't that affect the
> system security? Will the entire program of SELinux will be disabled or is
> it just a particular module that needs to be disabled.

SELinux is great, when used in the right place, but on a desktop machine
without top secret documents, it's just overkill, a firewall (iptables rules)
and the sense to not surf the net as root are in most cases more than enough.

IMHO SELinux requires an admin who know how to use it, or else there will just
be too much trouble with it and the SELinux should also be compiled so that
you can't disable it from a running environment (which you can do in Fedora).

--

//Aho

On Thu, 24 Jul 2008 13:37:54 +0200, J.O. Aho wrote:

> Artnut wrote:
>> "J.O. Aho" <user@example.net> wrote in message
>> news:6eqoecF8fbgfU1@mid.individual.net...
>>> Artnut wrote:
>>>> Hi all,
>>>>
>>>> This is about Fedora 9 but first a little background. Since, the
>>>> drivers for the on-board ethernet controller were missing in XP, I
>>>> had installed a PCI LAN card. After installing drivers for on-board
>>>> ethernet, I disabled the PCI card and now plugged the cable into
>>>> on-board ethernet controller which is working fine in XP. Now when I
>>>> boot in Fedora, I get a red X indicating problem with the network.
>>>> Then I log in as a root, go to Network or Network Device Control and
>>>> the following happens.
>>>>
>>>> The PCI card is recognised as eth0 and the on-board is shown as eth1.
>>>> Then I deactivate eth0.
>>>> Upon activating eth1, it searches for DHCP, gives a beep. Shows
>>>> Active status and asks me to restart the pc or the network. If I do
>>>> /etc/init.d network restart I get the following error in SELinux
>>>> icon.
>>> Edit your /etc/sysconfig/newtork-srcipts/ifcfg.ethX and set the eth0
>>> to onboot=no and eth1 onboot=yes.
>>>
>>> Edit your /etc/selinux/config and change your SELINUX to
>>> SELINUX=disabled
>>>
>>> Reboot and your eth1 should be working properly.
>>>
>>>
>>>
>> Thank you Aho for the solution. Although the issue was resolved, I have
>> a question.
>> You suggest that I should disable the SELinux. Now won't that affect
>> the system security? Will the entire program of SELinux will be
>> disabled or is it just a particular module that needs to be disabled.
>
> SELinux is great, when used in the right place, but on a desktop machine
> without top secret documents, it's just overkill, a firewall (iptables
> rules) and the sense to not surf the net as root are in most cases more
> than enough.
>
> IMHO SELinux requires an admin who know how to use it, or else there
> will just be too much trouble with it and the SELinux should also be
> compiled so that you can't disable it from a running environment (which
> you can do in Fedora).

Even though the SELinux icon gets active to show a message while starting
network service, I wonder if indeed its related to SELinux. Because, see
now am using PAN in Fedora to reply. Now the network is fine. However,
sometime back, the network came up, I logged into ISP site but couldn't
go any further. No other site was opening. Logged out, booted into XP and
all was fine. So what exactly prevents Fedora to get the network working
properly? Any ideas?

Regards,

Arty

Artnut wrote:

> Even though the SELinux icon gets active to show a message while starting
> network service, I wonder if indeed its related to SELinux. Because, see
> now am using PAN in Fedora to reply. Now the network is fine. However,
> sometime back, the network came up, I logged into ISP site but couldn't
> go any further. No other site was opening. Logged out, booted into XP and
> all was fine. So what exactly prevents Fedora to get the network working
> properly? Any ideas?

SELinux sets up a lot of restrictions, and can easily disturb your day to day
usage on a desktop system where you install new applications and so on, which
isn't intendant whith SELinux, where you are supposed to have a final
installation from the beginning.

You did remove the PCI card, the state of the system changed (back?) and from
SELinux point it can be back on a normal state.

Next time you have problem, just disable SELinux and I'm sure the trouble most
likely will disappear at once. I have experienced troubles with SELinux, a
system that should work didn't work at all as expected and not much of a hint
when services where tried to start, just diablin the SELinux which ain't
needed in the system, everything was solved, but we had waisted kind of a day
on trying to track the problem why we cloudn't connect to the local mysql server.

If you still think you should use SELinux, read at least this HOWTO:
http://www.lurking-grue.org/selinuxHOWTO.html
and this about RedHat SELinux:
http://www.cyberciti.biz/tips/rhel5-...wto-guide.html

If you feel it's to much, then turn off SELinux at once.

--

//Aho

On Thu, 24 Jul 2008 19:09:51 +0200, J.O. Aho wrote:

> Artnut wrote:
>
>> Even though the SELinux icon gets active to show a message while
>> starting network service, I wonder if indeed its related to SELinux.
>> Because, see now am using PAN in Fedora to reply. Now the network is
>> fine. However, sometime back, the network came up, I logged into ISP
>> site but couldn't go any further. No other site was opening. Logged
>> out, booted into XP and all was fine. So what exactly prevents Fedora
>> to get the network working properly? Any ideas?
>
> SELinux sets up a lot of restrictions, and can easily disturb your day
> to day usage on a desktop system where you install new applications and
> so on, which isn't intendant whith SELinux, where you are supposed to
> have a final installation from the beginning.
>
> You did remove the PCI card, the state of the system changed (back?) and
> from SELinux point it can be back on a normal state.
>
> Next time you have problem, just disable SELinux and I'm sure the
> trouble most likely will disappear at once. I have experienced troubles
> with SELinux, a system that should work didn't work at all as expected
> and not much of a hint when services where tried to start, just diablin
> the SELinux which ain't needed in the system, everything was solved, but
> we had waisted kind of a day on trying to track the problem why we
> cloudn't connect to the local mysql server.
>
> If you still think you should use SELinux, read at least this HOWTO:
> http://www.lurking-grue.org/selinuxHOWTO.html and this about RedHat
> SELinux:
> http://www.cyberciti.biz/tips/rhel5-...wto-guide.html
>
> If you feel it's to much, then turn off SELinux at once.

Thanks indeed Aho for the two very helpful links. Luckily, for some
reason, I haven't yet had any issue about no network in Fedora :-)

Regards,
Arty