Untangle Forums - View Single Post

IHateShuttle · 07-23-2009, 12:53 PM

Thank you for your response. I am using the on-board NIC for WAN.
The PCI Intel NIC is not the problem. I think the problem is related to a MAC address conflict now. The on-board NIC is referred to as eth0_rename. I looked that up and found some information about editing persistent net rules. From what I have read this is common when people change NIC cards in various flavors of Linux. I am a n00b with this Linux stuffs but I am trying to hack it right now.

The PCI card is reported by "lspci" as:

Intel 82557/8/9/0/1 Pro 100/S Desktop Adapter

The problem NIC is the on-board Marvell 88E8056

Does it matter that both of the adapters are on IRQ 17? I can only control 1-15 in the BIOS.

07-23-2009, 12:53 PM	#3 (permalink)
IHateShuttle Untangler Join Date: Jul 2009 Location: Left Coast Posts: 70	Thank you for your response. I am using the on-board NIC for WAN. The PCI Intel NIC is not the problem. I think the problem is related to a MAC address conflict now. The on-board NIC is referred to as eth0_rename. I looked that up and found some information about editing persistent net rules. From what I have read this is common when people change NIC cards in various flavors of Linux. I am a n00b with this Linux stuffs but I am trying to hack it right now. The PCI card is reported by "lspci" as: Intel 82557/8/9/0/1 Pro 100/S Desktop Adapter The problem NIC is the on-board Marvell 88E8056 Does it matter that both of the adapters are on IRQ 17? I can only control 1-15 in the BIOS. Last edited by IHateShuttle; 07-23-2009 at 01:49 PM..