Two Interfaces Connecting to FreeNAS UI

Status
Not open for further replies.
O

omerome

Dabbler
Joined
Apr 24, 2014
Messages
17
I have a weird problem. I have an Asrock E3C226D2I motherboard with 16GB of ECC ram and I am connecting only one ethernet cable and one cable connecting to the IPMI interface. However, what I have noticed is that FreeNAS seems to think that I am connecting to both of my ethernet connections and what happens is one goes DOWN and the other comes UP rather often.

For example:

Aug 10 23:47:56 OMMIE-NAS bridge0: Ethernet address: 02:cf:0d:2f:b8:00
Aug 10 23:47:56 OMMIE-NAS kernel: bridge0: link state changed to UP
Aug 10 23:47:56 OMMIE-NAS kernel: bridge0: link state changed to UP
Aug 10 23:47:56 OMMIE-NAS kernel: igb0: promiscuous mode enabled
Aug 10 23:47:56 OMMIE-NAS epair0a: Ethernet address: 02:ff:e0:00:05:0a
Aug 10 23:47:56 OMMIE-NAS epair0b: Ethernet address: 02:ff:30:00:06:0b
Aug 10 23:47:56 OMMIE-NAS kernel: epair0a: link state changed to UP
Aug 10 23:47:56 OMMIE-NAS kernel: epair0a: link state changed to UP
Aug 10 23:47:56 OMMIE-NAS kernel: epair0b: link state changed to UP
Aug 10 23:47:56 OMMIE-NAS kernel: epair0b: link state changed to UP
Aug 10 23:47:56 OMMIE-NAS kernel: igb0: link state changed to DOWN
Aug 10 23:47:56 OMMIE-NAS kernel: igb0: link state changed to DOWN
Aug 10 23:47:56 OMMIE-NAS kernel: epair0a: promiscuous mode enabled
Aug 10 23:47:57 OMMIE-NAS epair1a: Ethernet address: 02:ff:e0:00:06:0a
Aug 10 23:47:57 OMMIE-NAS epair1b: Ethernet address: 02:ff:30:00:07:0b
Aug 10 23:47:57 OMMIE-NAS kernel: epair1a: link state changed to UP
Aug 10 23:47:57 OMMIE-NAS kernel: epair1a: link state changed to UP
Aug 10 23:47:57 OMMIE-NAS kernel: epair1b: link state changed to UP
Aug 10 23:47:57 OMMIE-NAS kernel: epair1b: link state changed to UP
Aug 10 23:47:57 OMMIE-NAS kernel: epair1a: promiscuous mode enabled
Aug 10 23:47:59 OMMIE-NAS kernel: igb0: link state changed to UP
Aug 10 23:47:59 OMMIE-NAS kernel: igb0: link state changed to UP
Aug 10 23:48:00 OMMIE-NAS epair2a: Ethernet address: 02:ff:e0:00:07:0a
Aug 10 23:48:00 OMMIE-NAS epair2b: Ethernet address: 02:ff:30:00:08:0b
Aug 10 23:48:00 OMMIE-NAS kernel: epair2a: link state changed to UP
Aug 10 23:48:00 OMMIE-NAS kernel: epair2a: link state changed to UP
Aug 10 23:48:00 OMMIE-NAS kernel: epair2b: link state changed to UP
Aug 10 23:48:00 OMMIE-NAS kernel: epair2b: link state changed to UP
Aug 10 23:48:00 OMMIE-NAS kernel: epair2a: promiscuous mode enabled
Aug 10 23:48:04 OMMIE-NAS epair3a: Ethernet address: 02:ff:e0:00:08:0a
Aug 10 23:48:04 OMMIE-NAS epair3b: Ethernet address: 02:ff:30:00:09:0b
Aug 10 23:48:04 OMMIE-NAS kernel: epair3a: link state changed to UP
Aug 10 23:48:04 OMMIE-NAS kernel: epair3a: link state changed to UP
Aug 10 23:48:04 OMMIE-NAS kernel: epair3b: link state changed to UP
Aug 10 23:48:04 OMMIE-NAS kernel: epair3b: link state changed to UP
Aug 10 23:48:04 OMMIE-NAS kernel: epair3a: promiscuous mode enabled
Aug 10 23:48:58 OMMIE-NAS dhclient: New IP Address (igb0): 192.168.1.53
Aug 10 23:48:58 OMMIE-NAS dhclient: New Subnet Mask (igb0): 255.255.255.0
Aug 10 23:48:58 OMMIE-NAS dhclient: New Broadcast Address (igb0): 192.168.1.255
Aug 10 23:48:58 OMMIE-NAS dhclient: New Routers (igb0): 192.168.1.1

Here is what is happens on the console.

multple_interfaces_freenas.PNG


When I run ifconfig -a, here is the result:

igb0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 15 00
options=2400b9<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN _HWTSO,RXCSUM_IPV6>
ether d0:50:99:c1:b6:85
inet 192.168.1.53 netmask 0xffffff00 broadcast 192.168.1.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
igb1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=6403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCS UM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
ether d0:50:99:c1:b6:86
inet 192.168.1.54 netmask 0xffffff00 broadcast 192.168.1.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
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 0x3
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
groups: lo
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 02:cf:0d:2f:b8:00
nd6 options=9<PERFORMNUD,IFDISABLED>
groups: bridge
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: epair3a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 8 priority 128 path cost 2000
member: epair2a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 7 priority 128 path cost 2000
member: epair1a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 6 priority 128 path cost 2000
member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 5 priority 128 path cost 2000
member: igb0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 1 priority 128 path cost 20000
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:ff:e0:00:05:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
groups: epair
epair1a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:ff:e0:00:06:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
groups: epair
epair2a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:ff:e0:00:07:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
groups: epair
epair3a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:ff:e0:00:08:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
groups: epair

Is there a setting I need to change somewhere so only one interface is being used and only one IP is accessing the FreeNAS UI?

Thanks!

-omerome
 
O

omerome

Dabbler
Joined
Apr 24, 2014
Messages
17
Wow. So I just realized that all this time the ethernet cable was actually plugged into the wrong port. Once I disconnected the cable that was in the second ethernet port, now I only get one interface connecting to the FreeNAS UI.

I feel like a noob...
 
P

pschatz100

Guru
Joined
Mar 30, 2014
Messages
1,184
No worries. There isn't an experienced poster on this site that hasn't done something stupid or silly along the way.

It's part of life.
 
Status
Not open for further replies.

Similar threads

I
  • Locked
Various Plugins' Remote Access Stopped Working (Plex,ownCloud, etc)
Replies
5
Views
2K
I3lackR0se
I
R
Link state changed to UP / DOWN continuously
Replies
13
Views
3K
SweetAndLow
SweetAndLow
zey
  • Locked
SOLVED Intermittent loss of connection
Replies
5
Views
4K
zey
zey
S
  • Locked
epair interfaces
Replies
1
Views
3K
Nukama
N
I
  • Locked
kernel: arp: 192.168.1.3 moved from 02:11:e8:00:0e:0a to 00:22:15:a1:db:e8 on epair1b
Replies
9
Views
2K
panz
panz
Top