Bridge Interface

[sg4rb0]

Why does FreeNAS auto-create a bridge interface and include everything in it? In the output below, it seems to think it needs a bridge with these epair interface. I asked in another post what they are, but I don't get why I need any form of any bridge at all. I don't want it & if i delete it using the cmd line then FreeNAS freaks out and the network side of things breaks. Can someone explain why:

• I need a bridge interface. I don't want it, so can you explain why it appears to be required?
• The bridge interface adds all NIC's to it?
• Why FreeNAS will not sync changes I make from the FreeBSD shell to my network interfaces to FreeBSD iteslf? I set an IP on a network interface from the shell & FreeNAS couldn't sync with it. FreeNAS still thought it had the old IP. And when I reboot, this stupid bridge interface joined back onto the interface I statically configured, as well as reset the IP's on all my interfaces.

Provided ifconfig below.

[root@freenas] ~# ifconfig
ale0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 7500
options=c3098<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MCAST,WOL_MAGIC,VLAN_HWTSO,LINKSTATE>
ether 00:23:54:14:5e:73
inet 192.168.1.100 netmask 0xffffff00 broadcast 192.168.1.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
ipfw0: flags=8801<UP,SIMPLEX,MULTICAST> metric 0 mtu 65536
nd6 options=9<PERFORMNUD,IFDISABLED>
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 0xb
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 7500
ether 02:30:53:39:38:00
nd6 options=1<PERFORMNUD>
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: epair1a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 14 priority 128 path cost 2000
member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 13 priority 128 path cost 2000
member: ale0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 5 priority 128 path cost 20000
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 7500
options=8<VLAN_MTU>
ether 02:50:15:00:0d:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
epair1a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 7500
options=8<VLAN_MTU>
ether 02:56:43:00:0e:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active

 

[Nukama]

Have you set your interfaces manually "Network -> Interfaces -> Add Interface", or is this the stock configuration?

I've setup my interface manually and I've no bridge. But I also created my jails without VIMAGE support.

Configurations are done on the WebGUI and console setup and not inside FreeBSD CLI.

FreeNAS consists of two read-only root-image under /dev/ufs (FreeNASs1a and FreeNASs2a).
These are used for easy upgrading and fallback for a working system.
FreeNASs3 contains /cfg and FreeNASs4 contains /data.

 

[sg4rb0]

I don't know anything about vimage, but I did create jails. Anyway I decided I don't like jails, vimage, the fact the file system is read only for root, the fact a stupid bridge interface gets created, the fact that these epair interfaces get created, the fact I can't change freeBSD network settings & FreeNAS doesn't adjust/sync itself, the fact that in zfs you can't add a disk to an existing raid-z, the fact that many specific options for network settings aren't available in FreeNAS (they might be available in the options text box or something, but I'm done putting any more effort into FreeNAS).

The amount of sheer effort you have to put into anything you want to do in FreeNAS makes it unusable. I'd rather run my own debian server and do everything & anything I want to without limitation. I'm a network engineer and I want to play with the network stuff on a "Network" attached storage device. What a waste of effort this software was. I'm done with it.

 

[Whattteva]

Lol, someone needs to take a chill pill...
Sent from my RM-820_nam_att_100 using Tapatalk

 

[MunkaySteve]

Wow. What a rant. I am also a network engineer. You don't see me going off on one!

Get switches and routers if you want to do networking.

Freenas is a network attached storage system with some bells and whistles. The clue is in the name. Treat it like a server and you are kind of there.

 

[Whattteva]

Yeah, I think he walked into FreeNAS thinking it's OpenBSD or even PFSense, lol.