Well, I recently had a power failure and when I rebooted there was a problem with the startup.* I figured FC would take care of it just like windows does and there'd be no problem.* I'm not so sure it did, a file may have gotten corrupted somewhere.

Anyway,* I am on version 6 and have been meaning to upgrade but I didn't have the time but rather than spend any more time on this I am going to do a fresh install of FC9.* I'm sure that will take care of it.

Thank all,
Jim


> Date: Tue, 24 Jun 2008 12:21:37 -0400
> From: maximilianbianco@gmail.com
> To: fedora-list@redhat.com
> Subject: Re: Network connection issue
>
> Jim Douglas wrote:
> > Cable Modem. It is a valid IP. I have a second HD connected to this computer and when I switch to it I can connect to the internet no problem, I am posting from it right now..
> >
> > I am thinking I may have had the "Services" window open and clicked on something by accident....
> >
> > pinging is fine, a remote Ip times out...
> >
> > Jim
> Your dual booting fedora and windows? Fedora 8 or 9? What are the first
> two numbers of your IP?
>
> An ip that starts with 169.254.x.x is not valid on any network(not
> strictly true), if you have one of these then you are not getting a
> valid ip via dhcp. If your address begins with 192.168.x.x or 172.16.x.x
> then you have a private ip, which seems likely if you can ping the
> gateway but not a remote host. Please copy and paste the commands your
> using to ping from the terminal. Is the network manager service running?
> What is the status of the network service? Look in the services GUI and
> note the icon's color and the plug next to it. Highlight the service and
> you will get the details. So on my f9 box the network manager shows a
> green icon and a plug that looks plugged in( service enabled and
> running), while the network service shows a red icon and a plug that is
> plugged in(service disabled and running).
> On an F8 box the GUI is slightly different and does not show the helpful
> little icons but if you highlight the service it will give you a few
> details. The network manager should be running and the network service
> should show the interfaces that are configured to start at boot time and
> currently active interfaces but there probably/shouldn't be a check in
> the box next to it.
>
> Remember what you do every step of the way or even *better* take notes
> so you don't have to remember :^)
>
> Why did you have the services tab open in the first place?
> Have you been playing with the firewall config?
>
>
> --
> "You don't know the power of the dark side" --Darth Vader
>
> --
> fedora-list mailing list
> fedora-list@redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Earn cashback on your purchases with Live Search - the search that pays you back! Learn More
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

I recently installed a new D-Link DGE-530T 10/100/1000 Gigabit Desktop PCI Adapter card to connect to the internet. It was originally not recognized as there was not a driver available in debian. A new firmware-realtek update installed the driver but I had also installed another 'recognized' 3-com card, just to get the system to work. After I upgraded the driver , Debian did find the new card & set it up as eth1 while the 3-com card which worked was at eth0. As I am not well versed in this area of hardware, I just ignored the issue. I decided to try to get my system to use the new card today so I went into the box & removed the 3-com card, leaving only the D-Link card connected. Well, I was back where I started. Now my system will not connect to the network, & the router that supplies the connection will not see the card. I KNOW the card and connection are OK as the system boots into Windows7 pro and works fine. It does not work on Linux Mint Julia or Ubuntu either even though I have gone in & set the Eth0 connection to the correct intranet address & the MAC address of the card (which I got from the router interface, while Windows was booted).

Now I want to know how to get Linux to reset the network configuration. The router issues the 192.168.1.4 address via DHCP for this card. If there are files I can edit to get it working &/or test the driver to see if it works. It has been years since I had to manually configure a ethernet adapter card, & I am trying to make it as simple as possible. I have Webmin installed along with the gnome tools for network mgmt. None of these seem to get the card to be seen by the kernel.

Thanks!
frosty

On 11/03/2011 09:55 PM, John Foster wrote:
I have Webmin installed along with the gnome tools for
network mgmt. None of these seem to get the card to be seen by the
kernel.


Have you installed the firmware-linux-nonfree package on your
system?

Since Squeeze, a number of known working network cards are not
supported

anymore out-of-the-box and, without checking it though, it seems a
good

track for your problem.

Please send the contents of your /etc/network/interfaces file
here, as well

as the output of the following command:

*** *** lspci | grep Ethernet



Regards,

Victor

Hi John,

On Thu, Nov 03, 2011 at 02:55:51PM -0500, John Foster wrote:
> I recently installed a new D-Link DGE-530T 10/100/1000 Gigabit Desktop PCI
> Adapter card to connect to the internet. It was originally not recognized
> as there was not a driver available in debian.

Support for the DGE-530T revision C1 (Realtek RTL8169 based, PCI ID
1186:4302) was added to the in-tree r8169 driver at Linux 3.0.2. This was
incorporated in Debian's linux-2.6 as of version 2.6.32-36 (part of the
6.0.3 point release).

Firmware from userspace is not required for use of this device.

> I had also installed another 'recognized' 3-com card, just to get the
> system to work.
[...]
> Debian did find the new card & set it up as eth1 while the 3-com card
> which worked was at eth0.
[...]
> I decided to try to get my system to use the new card today so I went into
> the box & removed the 3-com card, leaving only the D-Link card connected.
> Well, I was back where I started. Now my system will not connect to the
> network, & the router that supplies the connection will not see the card.

Your network configuration likely requires adjustment. Through udev, Debian
systems use persistent names for network interfaces; your DGE-530T device
will still be assigned eth1 even when the 3Com card is physically removed.

The output of "ifconfig -a" (as requested by Victor Nitu) would have been
useful to confirm the current interface assignment.

You can either:

* Modify /etc/udev/rules.d/70-persistent-net.rules to assign eth0 to your
DGE-530T device (e.g. NAME="eth0"). The relevant line to adjust should
be present under a comment such as '# PCI device 0x1186:0x4302 (r8169)'.

After modification, save the file and reload the r8169 module using the
command "modprobe -r r8169 ; modprobe r8169" (alternatively, execute
"udevadm trigger"). Run "ifconfig -a" to confirm interface assignment.

* Amend your system's network configuration (/etc/network/interfaces) to
use eth1 instead of eth0, then bring the interface up using "ifup eth1".

The interfaces(5) manual page describes this file's format (execute "man
interfaces" to view this), see also other information available at [1].

Note that other application configuration files (e.g. iptables based
firewall) may require to be similarly updated.

On Fri, Nov 04, 2011 at 08:49:56AM -0500, John Foster wrote:
> It seems the correct driver is being loaded & I changed the etc/network
> interfaces to this now. It is the factory setup for a single card.
[...]
> -----------------------------------
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).

> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> allow-hotplug eth0
> iface lo inet loopback
> ----------------------------------------------

This is incorrect, as two iface stanzas are stated for loopback. It should
contain a line for the eth* network interface (e.g. "iface eth0 inet dhcp").

Geoff

[1] http://wiki.debian.org/NetworkConfiguration


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111105051931.GA9481@chmmr.gsimmons.org">http://lists.debian.org/20111105051931.GA9481@chmmr.gsimmons.org

On Sat, Nov 5, 2011 at 12:19 AM, Geoff Simmons <gsimmons@gsimmons.org> wrote:

Hi John,



On Thu, Nov 03, 2011 at 02:55:51PM -0500, John Foster wrote:

> I recently installed a new D-Link DGE-530T 10/100/1000 Gigabit Desktop PCI

> Adapter card to connect to the internet. It was originally not recognized

> as there was not a driver available in debian.



Support for the DGE-530T revision C1 (Realtek RTL8169 based, PCI ID

1186:4302) was added to the in-tree r8169 driver at Linux 3.0.2. *This was

incorporated in Debian's linux-2.6 as of version 2.6.32-36 (part of the

6.0.3 point release).



Firmware from userspace is not required for use of this device.



> I had also installed another 'recognized' 3-com card, just to get the

> system to work.

[...]

> Debian did find the new card & set it up as eth1 while the 3-com card

> which worked was at eth0.

[...]

> I decided to try to get my system to use the new card today so I went into

> the box & removed the 3-com card, leaving only the D-Link card connected.

> Well, I was back where I started. Now my system will not connect to the

> network, & the router that supplies the connection will not see the card.



Your network configuration likely requires adjustment. *Through udev, Debian

systems use persistent names for network interfaces; your DGE-530T device

will still be assigned eth1 even when the 3Com card is physically removed.



The output of "ifconfig -a" (as requested by Victor Nitu) would have been

useful to confirm the current interface assignment.



You can either:



** Modify /etc/udev/rules.d/70-persistent-net.rules to assign eth0 to your

* *DGE-530T device (e.g. NAME="eth0"). *The relevant line to adjust should

* *be present under a comment such as '# PCI device 0x1186:0x4302 (r8169)'.



* *After modification, save the file and reload the r8169 module using the

* *command "modprobe -r r8169 ; modprobe r8169" (alternatively, execute

* *"udevadm trigger"). *Run "ifconfig -a" to confirm interface assignment.



** Amend your system's network configuration (/etc/network/interfaces) to

* *use eth1 instead of eth0, then bring the interface up using "ifup eth1".



* *The interfaces(5) manual page describes this file's format (execute "man

* *interfaces" to view this), see also other information available at [1].



* *Note that other application configuration files (e.g. iptables based

* *firewall) may require to be similarly updated.



On Fri, Nov 04, 2011 at 08:49:56AM -0500, John Foster wrote:

> It seems the correct driver is being loaded & I changed the etc/network

> interfaces to this now. It is the factory setup for a single card.

[...]

> -----------------------------------

> # This file describes the network interfaces available on your system

> # and how to activate them. For more information, see interfaces(5).



> # The loopback network interface

> auto lo

> iface lo inet loopback

>

> # The primary network interface

> allow-hotplug eth0

> iface lo inet loopback

> ----------------------------------------------



This is incorrect, as two iface stanzas are stated for loopback. *It should

contain a line for the eth* network interface (e.g. "iface eth0 inet dhcp").



Geoff



[1] http://wiki.debian.org/NetworkConfiguration


-----------------------------------------Ha!!*Thanks Geoff. You really hit this out of the park. I,m now up & running with a new learning experience under my belt & a MUCH faster network.
Again Thanks & thanks to all of you who assisted especially Victor.frosty