L0rdRaiden
-
Posts
568 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by L0rdRaiden
-
-
@Squid can we have this or something similar by default in dockerman?
It will help with the docker compose setup with many dockers like mailcow
Also some kind of agregated template would be nice, to replicate what docker compose does in docker man.
-
Yes, that must be, I was trying to setup wireguard, it worked but I was never able to see anything else than 192.168.1.200 which is my unraid machine.
This one of the settings that had to be enable accoding to the guide. I will try again in a couple of months.
-
It doesn't help me really, I am not a pro
What I can tell you is that if I stop the array they disappear, but if I start it again they are created, but I don't know why yet
-
5 minutes ago, johnnie.black said:
They certainly aren't part of a default install, posting the diagnostics might give some clues, you can also try booting in safe mode without any dockers.
Please find attached the diagnostics file.
I will try to troubleshoot it tomorrow to see if I can delete them, but I would like to know what added them
-
Any clue on this? please
I can not delete them.
-
-
3 minutes ago, itimpi said:
Not if I understand you correctly
A docker/VM that uses virbr0 can connect to dockers/VMs using br0, but the converse is not true.
Ok, I read wrong your first explanation. I get it now.
But still I am trying to understand a scenario where this is usefull or makes any difference vs having all in br0 and the use VLANs to control the traffic.
-
So you can go from br0 to virtbr0 but anthing in virtbr0 can go out?
I am thing now a use case to use virtbr0... since I already use Vlans in my fw.
-
I understand that br0 is bridge 0 and virbr0 is virtual bridge 0
But since br0 is linked to eth0 and I can assign br0 to all the dockers and VM I want, what is the purpose and differences with virbr0?
Thanks in advance
-
On 1/24/2020 at 5:34 PM, uek2wooF said:
I just had them mixed up. I don't think it is switching them. All good now thanks.
Not sure why everything is so hard though. Am I really the first person to bridge networks to pfsense? Passing through a 4-port intel nic was a nightmare also. Easy on linux though.
Could you please copy paste your XML configuration?
Maybe a screen shot of the confing, not XML would help me as well, thanks
-
On 2/8/2020 at 4:04 PM, Squid said:
Not going to argue with the basic points, but dockerMan will let you configure everything possible. The extra parameters section on the template.
https://github.com/librenms/docker/blob/master/examples/compose/docker-compose.yml
How do I configure this in the same IP? I don't think you can reproduce any configuation that easily en dockerman. How can I setup the cron Image.
-
On 4/1/2020 at 9:43 PM, Unmax said:
For those coming here, I figured it out!
It's not working because it's missing the "chatid" file in "/boot/config/plugins/dynamix/telegram"
Steps:
- Follow this guide until you have created the bot
- Go to Unraid => Settings => Notification settings and scroll all the way down to Telegram.
-
Fill in the HTTP API of the bot
- Ex: 1216098989:AAGRnTFAKElG1v8pPKuN_RTGW4RTHDxo
- NO "-" at the start!
- Open the terminal, first of five icons at the top right of the screen.
-
Once in the terminal do the following:
- cd ../
- cd /boot/config/plugins/dynamix/telegram
- nano chatid
-
*paste in the channel id where the bot should post, or your own Telegram ID*
- Ex: -1001444111222
- MAKE SURE TO HAVE A "-" AT THE START HERE!
- *CTRL + S to save*
- *CTRL + X to close editor*
- ls *to check if the file has been made*
- No go back to the notification settings, press test underneath the Telegram form and it should work now!
Let me know if you have questions!
This is the easiest way to get your chat ID with 1 click
-
-
On 4/1/2020 at 12:25 AM, ljm42 said:
Did you re-download the latest client config after making any changes via the Unraid interface?
What are the "Allowed IPs" shown on your client?
yes,
and allowed IP's are 10.253.0.1/32 10.10.10.0/24 192.168.1.0/24
I have added 10.253.0.0/24 just in case and it doesn't work either.
-
11 hours ago, ljm42 said:
Can you access any other devices on your network? Ones that are not in any way hosted on your Unraid server? I'm guessing you should be able to.
As I mentioned in my reply to phrozen087 yesterday, I have no trouble accessing my router or a raspberry pi through the tunnel. But I am not able to access VMs running on Unraid. Haven't figured out why yet.
I am able to access Unraid Dockers, but my setup is simpler and I don't have any Dockers on their own IP. Because of this, I have "Local server uses NAT" set to Yes.
No, I have scanned the entire 192.168.1.0/24 (ping) and I only see unraid server while I had several devices connected in the same network that has nothing to do with unraid dockers and VMs
Do I have to create a firewall rule to provice visibility beween 192.168.1.0/24 and 10.253.0.0/24?
-
1 hour ago, ljm42 said:
That is exactly the scenario that this quickstart guide walks through
Depending on your network, you may need to add a static route to handle that. See the "Complex Networks" section of the guide. To make this easier, the WireGuard plugin now includes "remarks" that tell you what IP range to setup the static route for. You may need to switch to advanced mode to see it.
How are you trying to connect to the other devices? You won't be able to connect by name, only by IP address.
I guess I must be doing something wrong in my firewall
I have added a route
I have enabled the host access to custom networks
Still, from phone I only see the unraid machine, I can't see any other web service I have in the dockers using their IP's
-
19 hours ago, ljm42 said:
Then you have misconfigured the "Local tunnel address" in your WireGuard config. You should start over, and leave the local tunnel address at the default. The tunnel is not part of your LAN and cannot share the same IP range.
I have set the tunnel address as default, but once connected I can only see unraid server.
Do I need to create a rule in the firewall to provide connectivity beween my LAN and 10.253.0.0?
Shouldn't I see my LAN once connected without adding any additional rule? is there any step by step example of someone with a Remote access to LAN connection?
-
2 minutes ago, johnnie.black said:
loop2 is the docker image, that's always btrfs, and it's corrupt so you need to recreate it.
Thanks but, Why this happens? could it be due to non ECC RAM?
Is not the first time that it happens to me, is there any way to prevent it?
-
Why do I get this errors? I'm using zfs in all drives. Is there a way to repair it?
I don't have parity.
Mar 30 12:05:13 Unraid kernel: BTRFS error (device loop2): block=5791367168 write time tree block corruption detected
Mar 30 12:05:13 Unraid kernel: BTRFS: error (device loop2) in btrfs_commit_transaction:2344: errno=-5 IO failure (Error while writing out transaction)
Mar 30 12:05:13 Unraid kernel: BTRFS info (device loop2): forced readonly
Mar 30 12:05:13 Unraid kernel: BTRFS warning (device loop2): Skipping commit of aborted transaction.
Mar 30 12:05:13 Unraid kernel: BTRFS: error (device loop2) in cleanup_transaction:1894: errno=-5 IO failure -
I have configure wireguard like this, I pretend to acces my whole LAN from the Peer.
192.168.1.0/24 Is my LAN
In Sophos XG I have configure a FW rule to accept incoming connections from WAN to my public IP in UDP 51820
Then a NAT rule to redirect the incoming connections to that port to UNRAID where wireguard is
So I connecto to wireguard server, and I can reach Unraid Server from my phone but that is all, I can not ping my phone ip 192.168.1.231 from any device in my network, windows pc, etc, or I can't reach with my phone to any other IP.
Regarding Local server uses NAT, if I enable it does it mean that I won't be able to access to any docker with custom IP from my phone?
I would appreciate some help or recommendations to setting up wireguard. I guess it would be cleaner to create the server in another network, disable "local server uses NAT" and then configure the static routing in the firewall.
-
On 2/8/2020 at 4:04 PM, Squid said:
Not going to argue with the basic points, but dockerMan will let you configure everything possible. The extra parameters section on the template.
The problem is when you have something like this
https://github.com/mailcow/mailcow-dockerized/blob/master/docker-compose.yml
It would be nice to have in dockerman a way to configure something the way docker compose does it, as a group.
In the UI all the dockers could be nested in only one, and lets say you will configure all the dockers in the same template. It should be hard since more changes are in the UI.
Somehow dockerman teamplates could be as a dockercompose yml
- 1
-
I want to do the same, does this worked for you at the end?
How did you setup the network?
I dont understand what did you do with docker compose, didn't you install all the dockers separately?
I would appreciate a lot if you can provide a step by step guide with all the details until the creation of each docker, I know how to create each docker manually but I'm confused about the docker compose part and the network config.
Thanks
- 1
-
8 minutes ago, andreidelait said:
Removed everything (container, images, folder from appdata, docker template).
Installed it again and the same: no docker no VMs are shown.
Wait 5 mins then refresh the web.
-
4 minutes ago, andreidelait said:
After switching from the old repo to the official one, the docker containers are not shown in Netdada.
Is there something else that I need to configure?
Delete the docker and use the new template
[Plugin] VFIO-PCI Config
in Plugin Support
Posted · Edited by L0rdRaiden
I have this right now in my syslinux file
If I want to use this new method what do I need to remove from here? just this (vfio-pci.ids=8086:1521) or something else?
I'm doing passthrough of a pcie network card with 2 nics.
If I do the passthrough using this method (vfio-pci.cfg) all the other options of my syslinux config file still applies?
Thanks in advance.