samba_69

Members
  • Posts

    23
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

samba_69's Achievements

Noob

Noob (1/14)

2

Reputation

  1. I faced this issue for the first time today, and it was solved by just restarting the Docker from Settings menu I shall try using -i br0 in WSD Options under SMB settings. I am running docker on VLAN br0.150, so not very sure if that will work. I shall report back once I get the issue solved.
  2. Follow up repost! Any senior member here who can address this? I cannot connect to qbittorrent APIs when using custom open vpn as vpn of choice!
  3. Hey! I have been using binhex-qbittorrent for a month and it was butter smooth! I was using Custom Wireguard config to connect to my VPN network. Everything was okaish, except the speed, for which I decided to move to a new VPN provider (Surfshark) The new VPN provider provides openvpn configurations to users which gives acceptable speed for me. Thus I changed VPN_CLIENT to openvpn, and uploaded the .opvn file in config/openvpn (/mnt/user/appdata/binhex-qbittorrentvpn/openvpn) folder. In short I made the following change: VPN_CLIENT changed from wirequard to openvpn. I have also change the vpn files, but With the following change: 1. I can access WebUI and download using my new VPN configuration 2. I cannot connect qbittorrent from sonaar/radaar. They always fails if VPN_CLIENT is set ot openvpn The problem gets resoved once I switch back to wiregurad. Any solution to this?
  4. I did all as instructed, but all fails You may be right! May be virtio is the culprit here which is not passing vlans let me deep-dive into this in pfSense's forum
  5. was working on VLAN id 1 right now for test, now I switched to VLAN id 15 Everything is configured for vlan 15, as well as unraid Am also testing vms on br0.15 now unraid on br0 is 10.10.10.10 unraid on br0.15 is 10.10.15.1 Vlan 15 is have opt3 as parent interface, which connects to br0 Tried pinging 10.10.15.10 (Unraid on br0.15), but failed Am epecting br0 (virtual bridge within Unraid) to be a VLAN enabled bridge which can move tagged messages in to their respective VLANs
  6. I have followed all the 3 steps. I have independent networks created for each VLAN, with their own Static IPv4 and DHCP Here are the screenshots for VLAN 1 Unraid settings: pfSense pings:
  7. Things are working when am passing a dedicated nic (virtio <-->br0.xxx) to pfSense on br0.xxx. With this config I am able to ping Unraid on br0.xxx VLAN. But, things are falling apart when am not passing a dedicated nic to pfsense, and I define VLAN on opt3 (virtio <--> br0) But is it not possible to do this without passing a dedicated nic to pfSense?
  8. I can ping unraid from pfSense on br0, But cannot ping on Vlan/br0.150 What I believed was br0 behaving as a trunk, and any tagged packets in trunk would be untagged and moved to own switch, but this is definitely not the case here
  9. Am quite new here, hense pardon me if I ask silly questions! Let me consider a standalone scenario where I have just my Unraid server, pfSense VM and Unraid Dockers. Based on this I would like to handle the vlans as you have said . I probably did exactly the same as you instructed earlier: 1. virtio is set as trunk/parent interface for VLAN 150 2. virtio connects to br0 Even on doing this I cannot reach (ping) the dockers on br0.150 lan neither can dockers can reach internet This is not firewall vlan 150 have pass all rule defined What am I doing wrong?
  10. Yes, pfSense VM is my primary router/firewall and sole source to connect to internet! I have 4 port NIC passed (vfio) to pfSense, of which 3 ports are used as load balanced WAN port! 2 ports (1 from 4port NIC and 1 form Motherboard) connect to a network switch (to load balance some local and internet traffic) 1 virtio passed to pfSense which connects to br0. I want this virtio to handle vlan traffic for docker container, as I want to allow only selected local user to connect to docker, but all can connect to unraid What I want to do is pass a single virtio to pfsense, on which I want to create multiple vlans from pfSense settings, which will eventually be used unraid's bridge to distribute the traffics. I understand that adding virtual interface for pfsense on for each vlan will solve the problem, but adding new interface and managing them from pfsence will become problem as In future I have plans to assign individual vlan for a group of VMs for security reasons as they may be used by different guest. Having separate interfaces for each vlan will be similar to creating a virtual bridge for each network.
  11. I have been trying for some time to utilize VLANs to put dockers on a separate VLAN on br0 (instead of different ports on localhost) I have pfSense VM connected to Unraid's br0 via virtio (VNET0) on the same interface I have VLAN setup with id 150, which I intend to use with docker and VMs on Unraid. Setup: Setings within pfSense: pfSense VM connect VNET0 to br0 (no virtual nic br0.150): Unraid network setup: But whenever I connect VMs / Docker container to bridge br0.150, they become isolated from all other networks. How to pass VLAN from pfSense VM to Unraid bridge br0/br0.150 without adding extra nic to pfSense for each VLAN?
  12. Not very sure how DHCP is blocked, as whenever I connect a device to Unraid's port (on br0), pfSense's DHCP successfully allocates ip to the new device via virtio/br0. Its just the Unraid that cannot get the IP
  13. I was able to connect to Unraid by providing static IPv4 to Unraid in Settings >> NetworkSettings >> IPv4 address assignment <-- static ip Thanks all for your co-operations and help! @SimonF looking forward for E1000 and vmxnet3 in upcoming release! It will make life much easy!
  14. Thanks @SiNtEnEl Based on your feedback, I was able to enable virtio from pfSense setting, as you can see in the image below: I had to manually check the enable interface that eventually marked the virtio port up! I have set the vnet interface as static IPv4 with gateway 192.168.2.1 (my laptop is on LAN interface with 192.168.1.1 gateway) But now I ran into another problem now! I cannot Unraid obtain dhcp lease on this port, and hence cannot reach Unraid. Even I dont see Unraid in DHCP lease table as you can see! Only my laptop is have a DHCP lease Note: Unraid gets DHCP allocation successfully from eth0 on br0 ref: I am probably doing something wrong! Any guidance?