Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Configuring iptables to allow communication between docker and virbr0

Featured Replies

Hi all,

 

I have Guacamole VNC/RDP proxy running in a docker container to connect to machines on my LAN.  I have VM's running in the virbr0 bridged network segment. 

 

I have added a FORWARD rule to allow port 3389 to a Windows VM with IP address 192.168.122.2:

 

iptables -I FORWARD 3 -p tcp --dst 192.168.122.2 --dport 3389 -j ACCEPT

 

And can now successfully connect to it from physical machines on my LAN directly, but cannot do so via Guacamole.  What do I need to add/change/remove to allow this to work?

 

Here is iptables output:

 

 

Chain INPUT (policy ACCEPT 3253 packets, 632K bytes)
pkts bytes target     prot opt in     out     source               destination         
   25  1729 ACCEPT     udp  --  virbr0 any     anywhere             anywhere             udp dpt:domain
    0     0 ACCEPT     tcp  --  virbr0 any     anywhere             anywhere             tcp dpt:domain
   18  5955 ACCEPT     udp  --  virbr0 any     anywhere             anywhere             udp dpt:bootps
    0     0 ACCEPT     tcp  --  virbr0 any     anywhere             anywhere             tcp dpt:bootps

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target     prot opt in     out     source               destination         
4810  851K ACCEPT     all  --  any    virbr0  anywhere             192.168.122.0/24     ctstate RELATED,ESTABLISHED
4362 1952K ACCEPT     all  --  virbr0 any     192.168.122.0/24     anywhere            
    4   232 ACCEPT     tcp  --  any    any     anywhere             192.168.122.2        tcp dpt:rdp
    0     0 ACCEPT     all  --  virbr0 virbr0  anywhere             anywhere            
   11  7852 REJECT     all  --  any    virbr0  anywhere             anywhere             reject-with icmp-port-unreachable
    0     0 REJECT     all  --  virbr0 any     anywhere             anywhere             reject-with icmp-port-unreachable
31714 8481K DOCKER     all  --  any    docker0  anywhere             anywhere            
6274 4881K ACCEPT     all  --  any    docker0  anywhere             anywhere             ctstate RELATED,ESTABLISHED
38076   13M ACCEPT     all  --  docker0 !docker0  anywhere             anywhere            
    0     0 ACCEPT     all  --  docker0 docker0  anywhere             anywhere            
   11  5444 ACCEPT     all  --  any    any     192.168.0.0/24       192.168.122.0/24    

Chain OUTPUT (policy ACCEPT 2716 packets, 361K bytes)
pkts bytes target     prot opt in     out     source               destination         
    4  1321 ACCEPT     udp  --  any    virbr0  anywhere             anywhere             udp dpt:bootpc

Chain DOCKER (1 references)
pkts bytes target     prot opt in     out     source               destination         
    0     0 ACCEPT     tcp  --  !docker0 docker0  anywhere             172.17.0.1           tcp dpt:8080
21792 3374K ACCEPT     tcp  --  !docker0 docker0  anywhere             172.17.0.2           tcp dpt:https
   23  1230 ACCEPT     tcp  --  !docker0 docker0  anywhere             172.17.0.2           tcp dpt:http
    0     0 ACCEPT     tcp  --  !docker0 docker0  anywhere             172.17.0.3           tcp dpt:8000
  326 23039 ACCEPT     tcp  --  !docker0 docker0  anywhere             172.17.0.4           tcp dpt:9999
    0     0 ACCEPT     tcp  --  !docker0 docker0  anywhere             172.17.0.5           tcp dpt:64443
3299  201K ACCEPT     tcp  --  !docker0 docker0  anywhere             172.17.0.5           tcp dpt:4242
    0     0 ACCEPT     tcp  --  !docker0 docker0  anywhere             172.17.0.6           tcp dpt:6501

 

I have also tried running the VM in br0 with DHCP assignment from my router but the issue is the same; Guacamole running inside docker cannot connect to its IP, even though physical machines can.

  • Author

My bad, just needed to disable NLA on the VM

  • 3 weeks later...

I have a feeling this is something similar to what i want to do.

 

I have multiple unraid machines and i want to be able to see drives/storage folders between them

 

e.g  Sickbeard on server 1 to download to folder on server 2

 

or ftp share - shares files from server 1 and 2..

 

Im not too great with linux commands etc

 

is this similar? or should i go looking elsewhere?

 

Im not sure where to start plus im about to create a new v6 server (i have a 4 hdd limitation on each server due to hardware and size of machine)

 

Thanks in advance

 

Thanks

 

Ric

  • Community Expert

I have a feeling this is something similar to what i want to do.

 

I have multiple unraid machines and i want to be able to see drives/storage folders between them

 

e.g  Sickbeard on server 1 to download to folder on server 2

 

or ftp share - shares files from server 1 and 2..

 

Im not too great with linux commands etc

 

is this similar? or should i go looking elsewhere?

 

Im not sure where to start plus im about to create a new v6 server (i have a 4 hdd limitation on each server due to hardware and size of machine)

The Unassigned Devices plugin should allow you to do this relatively easily.  It provides the ability to mount network shares on the server it is running on.  Once that has been done you can (optionally) map those to docker containers.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.