K45 PCI NIC Conflict?

IHateShuttle · 07-23-2009, 08:45 AM

I have a shuttle K45. The on-board NIC is recognized by UT by itself. If I plug in this Intel 10/100 PCI NIC it is also recognized but then the on-board NIC shows up as "connected unknown" in UT and there are no lights blinking on the back of the on-board card. Using the same cat-5 cable the router will light up with the PCI NIC but not the on-board.

I checked the BIOS, tried enabled and disabled. I called Shuttle and they are not helpful at all.

I know people use K45's for Untangle, what am I doing wrong? Only one NIC works at a time?

tbrown · 07-23-2009, 11:53 AM

I use a Shuttle K45 with a dual port intel 10/100 NIC for our Untangle server. The only problem I had was that Untangle would only work when the onboard nic was used for the external interface. If I tried to swap interfaces and use the intel nic for the external interface it would not work. I gave up trying to get Untangle to work that way and just used the onboard nic for the external interface. Which intel nic are you trying to use?

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.

tbrown · 07-24-2009, 06:43 AM

You might try reinstalling Untangle. When you see rename on the interface names it means you have tried to change the nics after you have installed Untangle. I have had much better luck getting Untangle to work when you have the nics set before you install Untangle than trying to fix or change them after Untangle has been installed.

IHateShuttle · 07-24-2009, 08:10 AM

Wow, that is bad news but thank you. I guess that is where I am heading.

IHateShuttle · 07-24-2009, 01:03 PM

FINAL UPDATE: The only fix I was able to find was "Restore factory defaults" from the recovery menu on the Untangle console. I am not happy that it came to this after a bunch of time wasted.

So if you change network adapters and you get the dreaded "eth0_rename" take the easy way out:

1. make a backup on the local HD
2. Restore factory defaults
3. Restore from the backup

This forces the OS to clear out and reload the hardware profile, I couldn't figure out any other way to do this manually.

07-23-2009, 08:45 AM	#1 (permalink)
IHateShuttle Untanglit Join Date: Jul 2009 Location: Left Coast Posts: 27	K45 PCI NIC Conflict? I have a shuttle K45. The on-board NIC is recognized by UT by itself. If I plug in this Intel 10/100 PCI NIC it is also recognized but then the on-board NIC shows up as "connected unknown" in UT and there are no lights blinking on the back of the on-board card. Using the same cat-5 cable the router will light up with the PCI NIC but not the on-board. I checked the BIOS, tried enabled and disabled. I called Shuttle and they are not helpful at all. I know people use K45's for Untangle, what am I doing wrong? Only one NIC works at a time?

07-23-2009, 12:53 PM	#3 (permalink)
IHateShuttle Untanglit Join Date: Jul 2009 Location: Left Coast Posts: 27	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..

07-23-2009, 11:53 AM	#2 (permalink)
tbrown Untanglit Join Date: Jan 2009 URLs submitted: 6 Posts: 10	I use a Shuttle K45 with a dual port intel 10/100 NIC for our Untangle server. The only problem I had was that Untangle would only work when the onboard nic was used for the external interface. If I tried to swap interfaces and use the intel nic for the external interface it would not work. I gave up trying to get Untangle to work that way and just used the onboard nic for the external interface. Which intel nic are you trying to use?

07-24-2009, 06:43 AM	#4 (permalink)
tbrown Untanglit Join Date: Jan 2009 URLs submitted: 6 Posts: 10	You might try reinstalling Untangle. When you see rename on the interface names it means you have tried to change the nics after you have installed Untangle. I have had much better luck getting Untangle to work when you have the nics set before you install Untangle than trying to fix or change them after Untangle has been installed.

07-24-2009, 08:10 AM	#5 (permalink)
IHateShuttle Untanglit Join Date: Jul 2009 Location: Left Coast Posts: 27	Wow, that is bad news but thank you. I guess that is where I am heading.

07-24-2009, 01:03 PM	#6 (permalink)
IHateShuttle Untanglit Join Date: Jul 2009 Location: Left Coast Posts: 27	FINAL UPDATE: The only fix I was able to find was "Restore factory defaults" from the recovery menu on the Untangle console. I am not happy that it came to this after a bunch of time wasted. So if you change network adapters and you get the dreaded "eth0_rename" take the easy way out: 1. make a backup on the local HD 2. Restore factory defaults 3. Restore from the backup This forces the OS to clear out and reload the hardware profile, I couldn't figure out any other way to do this manually.