setting up a bridge network on truenas scale is this Broken?

[Mkubiak402]

yeah I Bricked it again can't access the server.. I'm lost and getting no where I'm just going to give it a brake for now..

maybe some one will make a video on youtube on how to do it some day

 

[sretalla]

What I see you doing in that video is starting with eno1 having an IP address.

You add a bridge first, then add back an IP address to eno1.

I don't know how many times, but it must be at least once each from me and Patrick, we said you need to assign the IP address to the bridge.

The correct order of steps:

1. remove the IP address from eno1
2. create the bridge interface and add the members, adding an IP address to the bridge (which will now be the IP address of your NAS).
3. test/save changes.

I am not surprised you lose access to the NAS having done what you did.

 

[Mkubiak402]

What I see you doing in that video is starting with eno1 having an IP address.

You add a bridge first, then add back an IP address to eno1.

I don't know how many times, but it must be at least once each from me and Patrick, we said you need to assign the IP address to the bridge.

The correct order of steps:

1. remove the IP address from eno1
2. create the bridge interface and add the members, adding an IP address to the bridge (which will now be the IP address of your NAS).
3. test/save changes.

I am not surprised you lose access to the NAS having done what you did.

i have done it that way too ill make a video of that today the same thing will happen..
i added the IP address to BR0 I added the 192.168.10.26/24 it locked up and reset its self.

I just did not make a video of that i was trying to rush and get dinner.

i got most of this working even had PLEX and even had next cloud running and syncing 2 phones to the cloud.

apologize for any misunderstanding the help is appreciated.

 

[Mkubiak402]

ok I got it working sometimes you can lead a horse to water... that horse being me.. i was just real stressed out to get it going. the help is appreciated.
sorry for the trouble I not really this dumb in person

doing some Flow tests and every one is able to pull a fill gig from this thing now.

 

[sretalla]

All's well that ends well.

Glad to see you got it going.

 

[camsrv]

This post helped me figure out part of my issues; but if anyone sees this and still has issues / I found using the console made it finally work for me.

Also keep in mind that the bridge will have a new Mac Address, so if you have static ip configs on your firewall based on Mac addresses that was also breaking my setup until i enabled DHCP. More info here

End result:

(Pictured above is after I enabled the Bridge, my network had two duplicate 'cam-server.lan' connections which I had to rename; and my ip reservation is also what broke it before since the Mac requesting that IP did not match up the old Mac Address until I gave in and enabled DHCP)


For the console method,


Select (1) Network Interfaces


Move the Settings (DHCP / Reserved IPs to the New Bridge)


Since my network uses DHCP I turned ipv4_dhcp to ON on the old interface and made sure the IP Aliases were empty.

(If you DON’T USE DHCP, keep track of your IP Aliases since you will need to copy them over to the bridge)

Then on my bridge network ‘br0’ I set ipv4_dhcp to ON; and if you don’t use DHCP copy your IP Aliases here from your old network interface.

Be sure to add your old network interface as Bridge Member!



Then quit and save, and if needed reboot!

 

[jke]

Just another note to future users. If you are having trouble making the bridge work and you are running truenas inside a VM in ESXi you should check the security settings of the vSwitch. See this post: https://www.truenas.com/community/t...ms-with-bridged-interface.101134/#post-696780

 

[Andy_walker]

Hi guys. May I join this party with my silly question please?
I have TrueNas Scale installed on a physical server. With one physical network interface with static IP.
Besides few apps I have a VM hosted on TrueNAS which I want to share NFS folder with.
I was following article @sretalla referred to which says that in order to access NAS from a VM I need to create a bridge interface.
That is what I'm trying to do.
My problem is that my TrueNAS has only one physical interface.
So article says I need to remove assigned IP from the interface before I can create bridge and assign it there.
Problem №1. It seems I cannot remove IP from network interface in TrueNAS. I click on remove alias, then hit Save. It seems it is saved it but IP address is still there. If I refresh list of interfaces it is shown there again.
Consequently I cannot add that IP to the bridge. It says "network is already used by another interface"
And Question №2 I have only one interface and I use its IP to access my TrueNAS. If I remove it I'll lost access to NAS. So how I suppose to do it? Should I connect to the NAS console first? And only then makes these changes? Assuming that removing IP from the interface will be working.

Thank you

 

[sretalla]

Almost without exception, the issues I see here on the process shown in the documentation (https://www.truenas.com/docs/scale/scaletutorials/virtualization/accessingnasfromvm/) are related to services using the network connection that prevent it from being changed by the system.

You need to stop all your apps and VMs (and in some cases, even manually stop Kubernetes (but try without that first), and maybe any services like SMB/NFS that might be using the IP address, then do the changes to the network.

If you make and save (but don't test) all the needed changes, you don't lose connectivity to your NAS after removing the IP address (since until it's tested and "confirmed/saved, it's not actually changed).

Once you have the IP saved on the bridge, then test the changes and make sure you make it back to actually confirm the changes and save (or all changes will revert back to how it was before).

 

[Andy_walker]

Thank you @sretalla
Indeed what it takes to make it work was to disable Kubernetes.
Shut downed VM, stopped apps, even stopped all sharing services didn't help.
So I had to manually stop Kubernetes service.
Only then it let me remove IP from the network interface and get it assigned to the new bridge. :)

 

[Slovak]

in some cases, even manually stop Kubernetes

what it takes to make it work was to disable Kubernetes

What is the recommended way to do that?

 

[Andy_walker]

Guys could correct me what is a right way to do it. I did it from system settings/shell then sudo systemctl k3s.service stop

 

[sretalla]

sudo systemctl k3s.service stop

That's certainly appropriate.

 

[Walter Lite]

Setting Up a Network Bridge

Provides instructions on setting up a network bridge interface on TrueNAS CORE.

www.truenas.com

does not work cannot create bridge

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether ac:1f:6b:93:50:5b brd ff:ff:ff:ff:ff:ff
altname enp3s0
inet 192.168.0.85/24 brd 192.168.0.255 scope global dynamic eno2
valid_lft 604126sec preferred_lft 604126sec
inet6 2604:b000:a158:a08:ae1f:6bff:fe93:505b/64 scope global dynamic mngtmpaddr
valid_lft 299sec preferred_lft 299sec
inet6 fe80::ae1f:6bff:fe93:505b/64 scope link
valid_lft forever preferred_lft forever
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether ac:1f:6b:93:50:5a brd ff:ff:ff:ff:ff:ff
altname enp0s31f6
inet 192.168.0.84/24 brd 192.168.0.255 scope global dynamic eno1
valid_lft 604117sec preferred_lft 604117sec
inet6 2604:b000:a158:a08:ae1f:6bff:fe93:505a/64 scope global dynamic mngtmpaddr
valid_lft 299sec preferred_lft 299sec
inet6 fe80::ae1f:6bff:fe93:505a/64 scope link
valid_lft forever preferred_lft forever
4: kube-bridge: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 3a:18:63:eb:10:20 brd ff:ff:ff:ff:ff:ff
inet 172.16.0.1/16 brd 172.16.255.255 scope global kube-bridge
valid_lft forever preferred_lft forever
inet6 fe80::f447:2dff:fe13:665f/64 scope link
valid_lft forever preferred_lft forever
5: kube-dummy-if: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default
link/ether ca:9b:13:8d:16:24 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.10/32 scope link kube-dummy-if
valid_lft forever preferred_lft forever
inet 172.17.248.170/32 scope link kube-dummy-if
valid_lft forever preferred_lft forever
inet 172.17.0.1/32 scope link kube-dummy-if
valid_lft forever preferred_lft forever
inet6 fe80::78f3:7bff:fe99:2766/64 scope link
valid_lft forever preferred_lft forever
6: vethfc4ac530@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master kube-bridge state UP group default
link/ether fa:6b:35:67:1c:24 brd ff:ff:ff:ff:ff:ff link-netns cni-80a50250-1fbb-ee5c-0d25-a1ccfece4090
inet6 fe80::44f7:bff:fe04:37d2/64 scope link
valid_lft forever preferred_lft forever
7: vethf1e842b3@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master kube-bridge state UP group default
link/ether 6a:5f:83:5f:d2:b4 brd ff:ff:ff:ff:ff:ff link-netns cni-2fce3b2b-5731-ef1e-a669-ee188ae1f737
inet6 fe80::38df:f4ff:fe4d:32cf/64 scope link
valid_lft forever preferred_lft forever
8: veth628d823d@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master kube-bridge state UP group default
link/ether 02:0b:d6:d8:62:ae brd ff:ff:ff:ff:ff:ff link-netns cni-cb59d663-856b-4937-a23d-cf3380618c43
inet6 fe80::106a:d3ff:fec8:d9b3/64 scope link
valid_lft forever preferred_lft forever
9: veth107f6a8c@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master kube-bridge state UP group default
link/ether 12:ab:6d:db:b8:e1 brd ff:ff:ff:ff:ff:ff link-netns cni-a17c94af-59e2-ad6b-13d2-ef3157e1de6b
inet6 fe80::4c6:8eff:fe1f:6750/64 scope link
valid_lft forever preferred_lft forever
10: veth95405a4d@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master kube-bridge state UP group default
link/ether 52:f2:ab:c2:85:9a brd ff:ff:ff:ff:ff:ff link-netns cni-0585d9b5-ffe3-f79d-7969-4a35a806ca30
inet6 fe80::9cf7:59ff:fe57:c00b/64 scope link
valid_lft forever preferred_lft forever

 

[sretalla]

There are a number of things in your post that indicate you're using SCALE, but you have linked the CORE version of the documentation...

Perhaps use the SCALE version:

Accessing NAS From a VM

Provides instructions on how to create a bridge interface for the VM and provides Linux and Windows examples.

www.truenas.com

But also take note of the posts above yours which mention some things that may need stopping (which aren't mentioned in the doc) for it to work.

 

[Walter Lite]

staert sep 9 to step

 

[Walter Lite]

followed steps does not work

 

[Walter Lite]

to add to the issue
admin@truenas[~]$ ip link add name br0 type bridge
RTNETLINK answers: Operation not permitted

not nice --- a crippled Linux system as well

who is RTNETLINK???

 

[Patrick M. Hausen]

You probably need to be root for that command.

 

[Walter Lite]

admin@truenas[~]$ sudo apt install bridge-utils
Package management tools are disabled on TrueNAS appliances.

Attempting to update SCALE with apt or methods other than the SCALE web
interface can result in a nonfunctional system. guess that's a no no as well