SOLVED Need a network expert to answer question, PLEASE HELP

Status
Not open for further replies.

BigDave

FreeNAS Enthusiast
Joined
Oct 6, 2013
Messages
2,479
Here are all the details of the hardware.
First I will explain what I have that works without issue:

ONT with an ethernet cable (Cat6) providing approx 10 Megabytes per second (up and down)
into my home, and you are to assume it's NOT a cable issue.
The current Network Appliance (pfSense) that I built with Intel NICs and functions at 1Gb speeds without issue.

Introducing new hardware:
Supermicro X10SDV-2C-TLN2F (embedded Pentium D1508 SOC).
This board has NO 1Gb ethernet ports, it only has 2 - 10GBase-T ports and I ASSUMED
the ethernet ports would perform auto-negotiation. Here's is where I become a Network
Newbie and now have need of your expertise.

So I built this new firewall/router and installed the latest version of pfSense on it, no problems,
I have done this dozens of times...
When I attempt to install my new network appliance in my system the cable from the ONT never
interfaces with the motherboard port that is set up as the WAN (from the console).
My guess is that the speed coming from the ONT is 10MB and the 10GBase-T port on
the motherboard will not auto-negotiate it's speed that low???
I tested this theory by using other 1Gig connections in my home, in that case, the motherboard
port has no issues with connecting with them.
Just to give as much info as possible, the 10Gig ports are Intel X552 / X557-AT,
confirmed here at STH website.
I've read a lot of stuff before posting this, but it's all over my head for sure.
Thanks for taking the time to read this.
Dave
 

BigDave

FreeNAS Enthusiast
Joined
Oct 6, 2013
Messages
2,479
Paste the output of ifconfig within code tags.
If I can manage to get into the pfSense shell, it will take some time.

This output is from the current appliance which is 100% functional.
Code:
igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
   options=6400bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
   ether 00:30:18:cb:3c:bd
   hwaddr 00:30:18:cb:3c:bd
   inet6 fe80::230:18ff:fecb:3cbd%igb0 prefixlen 64 scopeid 0x1
   inet 47.183.253.10 netmask 0xffffff00 broadcast 47.183.253.255
   nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
   media: Ethernet autoselect (100baseTX <full-duplex>)
   status: active
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
   options=4209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWTSO>
   ether 00:30:18:cb:c2:34
   hwaddr 00:30:18:cb:c2:34
   inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255
   inet6 fe80::1:1%em0 prefixlen 64 scopeid 0x2
   nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
   media: Ethernet autoselect (1000baseT <full-duplex>)
   status: active
em1: flags=8c02<BROADCAST,OACTIVE,SIMPLEX,MULTICAST> metric 0 mtu 1500
   options=4209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWTSO>
   ether 00:30:18:cb:c2:37
   hwaddr 00:30:18:cb:c2:37
   nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
   media: Ethernet autoselect
   status: no carrier
em2: flags=8c02<BROADCAST,OACTIVE,SIMPLEX,MULTICAST> metric 0 mtu 1500
   options=4209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWTSO>
   ether 00:30:18:cb:c2:35
   hwaddr 00:30:18:cb:c2:35
   nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
   media: Ethernet autoselect
   status: no carrier
em3: flags=8c02<BROADCAST,OACTIVE,SIMPLEX,MULTICAST> metric 0 mtu 1500
   options=4209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWTSO>
   ether 00:30:18:cb:c2:36
   hwaddr 00:30:18:cb:c2:36
   nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
   media: Ethernet autoselect
   status: no carrier
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
   options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
   inet6 ::1 prefixlen 128
   inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6
   inet 127.0.0.1 netmask 0xff000000
   nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
   groups: lo
enc0: flags=0<> metric 0 mtu 1536
   nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
   groups: enc
pflog0: flags=100<PROMISC> metric 0 mtu 33160
   groups: pflog
pfsync0: flags=0<> metric 0 mtu 1500
   groups: pfsync
   syncpeer: 224.0.0.240 maxupd: 128 defer: on
   syncok: 1


The new appliance's output will follow shortly (I hope).

Ok, after great effort, here is the output of the new appliance.
BTW, I have heard it said that most 10GbE cards do not go slower than 1GbE speeds.
I wonder if this is my problem?

Code:
ix0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=e400bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
	ether 0c:c4:7a:c9:44:be
	hwaddr 0c:c4:7a:c9:44:be
	inet6 fe80::ec4:7aff:fec9:44be%ix0 prefixlen 64 scopeid 0x1
	nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
	media: Ethernet autoselect
	status: no carrier
ix1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=e407bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
	ether 0c:c4:7a:c9:44:bf
	hwaddr 0c:c4:7a:c9:44:bf
	inet6 fe80::ec4:7aff:fec9:44bf%ix1 prefixlen 64 scopeid 0x2
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
	media: Ethernet autoselect
	status: no carrier
cxgbe0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=ec00bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
	ether 00:07:43:10:e2:b0
	hwaddr 00:07:43:10:e2:b0
	inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255
	inet6 fe80::1:1%cxgbe0 prefixlen 64 scopeid 0x3
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
	media: Ethernet 10Gbase-Twinax <full-duplex>
	status: active
cxgbe1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=ec07bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
	ether 00:07:43:10:e2:b8
	hwaddr 00:07:43:10:e2:b8
	inet6 fe80::207:43ff:fe10:e2b8%cxgbe1 prefixlen 64 scopeid 0x4
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
	media: Ethernet none
	status: no carrier
enc0: flags=0<> metric 0 mtu 1536
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
	groups: enc
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
	options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
	inet6 ::1 prefixlen 128
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6
	inet 127.0.0.1 netmask 0xff000000
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
	groups: lo
pflog0: flags=100<PROMISC> metric 0 mtu 33160
	groups: pflog
pfsync0: flags=0<> metric 0 mtu 1500
	groups: pfsync
	syncpeer: 224.0.0.240 maxupd: 128 defer: on
	syncok: 1
 
Last edited:

BigDave

FreeNAS Enthusiast
Joined
Oct 6, 2013
Messages
2,479

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
Yeah, looks like Xeon-D doesn't support 100Mb/s Ethernet from the integrated NICs.

https://ark.intel.com/products/91558/Intel-Pentium-Processor-D1508-3M-Cache-2_20-GHz

If igb0 is connected to your ONT, things aren't going to work. But I'm surprised that the ONT doesn't do GbE - could it be that the cable is defective?

A lot of 10GbE gear doesn't support 10/100 anymore. I assume it's because vendors can't be bothered to implement the little bit of software/firmware needed, because 100BaseTX operates at the same frequency as 1000BaseT.
 

BigDave

FreeNAS Enthusiast
Joined
Oct 6, 2013
Messages
2,479
Yeah, looks like Xeon-D doesn't support 100Mb/s Ethernet from the integrated NICs.
This is what I expected was the issue, and it's my fault for not checking that out prior to my purchase.
If igb0 is connected to your ONT, things aren't going to work.
igb0 is actually a 1GbE port and is part of my current appliance that works.
ix0 is the 10GBase-T port on the new motherboard that does not, and thanks to you, I now know why.
But I'm surprised that the ONT doesn't do GbE - could it be that the cable is defective?
At this point I will test a temporary cable, since the existing cable is a couple of years old. It certainly can't hurt.

If the cable turns out to be good, I will solve my issue with one of these...
chelsio422-cr.jpg
This will allow me to connect the WAN to a 1GbE port AND
use the SPF+ port for the LAN, which BTW was my whole
reason for building this
 
Last edited:
Status
Not open for further replies.
Top