Korshakov

Members
  • Posts

    38
  • Joined

  • Last visited

Everything posted by Korshakov

  1. Most VPN services are running on port 1194. Wireguard is different port and also actually as well different standard.
  2. Would it be possible to add inverted option? EG: Allow only IPs specified and block everything else.
  3. Hi Guys, so i've found solution to my issue with pfSense router running as VM on Unraid. This however requires NIC with at least 3 sockets with pass through properly enabled. In overall: I've moved unraid onto completely separated network (physically). I am pretty sure that this solution applies to OpenVPN etc. Network Setup: My pfSense VM has intel NIC with 4 sockets. Socket 1 - Wan connection from ISP Socket 2 - LAN1 (192.168.1.0/24) on this network i have pfSense. (DHCP Enableb) Socket 3 - LAN2 (10.0.0.0/24) on this network i have unraid. (DHCP Disabled) Socket 4 - Currently empty. VLAN 20 (DHCP Disabled) on LAN2 (10.0.20.0/24) - Used for Unraid Dockers VLAN 30 (DHCP Disabled) on LAN2 (10.0.30.0/24) - Used for Unraid VMs I have literally short patch cable going from my Intel NIC to my Unraid Motherboard. PF Sense - If you are NOT using NAT in Wireguard. 1. Settings to enable: 1.1 - Go to: System -> Advanced -> Tab Firewall & NAT 1.2 - Checkbox: Static route filtering: checked-in. 2. Create gateway with your unraid's static IP in my case (10.0.0.10) 3. Create static route: 3.1 - Destination to wireguard network (from default its 20.253.0.0/24) 3.2 - Choose gateway (10.0.0.10) Issue to overcome: No internet access at all, everything on network is accessible and works (dockers, VMs, everything) Solution to that is to enable NAT in wireguard. (everything then works perfectly). If you dont want NAT enabled in Wireguard: I think this is a manner of finding the right setting in pfSense and hookup the wireguard network to have access to the internet. Unraid: I've followed guides from posts in here written in the past, credits for this goes to @Can0nfan and @craftsman when it comes to setups dockers and vms. Unraid IP is 10.0.0.10 Enable VLANS in net. settings and set them up in my case vlan tag 20 (dockers) and 30 (VMs) go to docker settings and setup vlan network there, do not set DHCP pool and leave it blank. go to VM settings and setup vlan network there. NOW i won't be lying to you, there is much easier way to get VPN to your network by simply using build in pfSense OpenVPN and you don't have to go through any of these issues at all, but for sake of experimenting i think this was fun and this gave me a backup option if for some reason OpenVPN fails, because Wireguard is completely different solution than OpenVPN and i want to avoid using L2tp with IPsec. (i dont like L2tp with IPsec just from personal preference).
  4. Edit: I dont think this has anything to do with the plugin itself. I signed in on unraid localhost and tried to ping anything on network, nothing would get reply other than reply from from router. I dont understand.... I can access unraid from any network, but unraid cant access any network other than gateways. Edit: so I've tried to replace my pfsense VM with my old physical router. When I tunnel to unraid I can now ping onto any device in network. Because my old router doesn't support vlans or multiple networks I can't really try out dockers on different network or vlan. Any suggestions?
  5. Hi Guys, I've spent hours on this to work this out when it comes to dockers on custom IP, but no joy at all. (this is not really wireguard issue as openVPN has same issue) Here is my setup: PF Sense router as VM from unraid. Currently has Intel NIC with 4 ports bypassed. Socket 0 - WAN Socket 1 - LAN1 (192.168.1.0/24) Socket 2 - LAN20 (192.168.20.0/24) Socket 3 - Not used uPnP - Disabled Port forwarding 51820 to 192.168.1.10 UDP enabled. Socket 1 goes to switch to feed my house and one wire back to Unraid to ETH1. Socket 2 goes to unraid to ETH2. (i know i just could do VLAN instead, but I like physical wire instead) UNRAID SERVER ETH0 - unraid server running on this socket using static IP 192.168.1.10 ETH1 - used for docker containers only using static IP 192.168.20.10 ETH0 and ETH1 are not anyhow connected to each other (bounding what I mean). See routing table below as well. Firewall rule on LAN20 is simple for sake of troubleshooting. Everything allowed from any source to any destination any port or protocol. Firewall rule on LAN1 allows 10.253.0.0/24 to 192.168.1.0/24. I have 192.168.1.10 setup as simple gateway in PF Sense. I am static routing anything from 10.253.0.0 to 192.168.1.10 as i have NAT in Wireguard DISABLED. See screenshot. If i missed something from my setup please do not hesitate to ask. Docker has two networks setups. br0 and br1. So what works in terms of local network only. My PC is on LAN1 (192.168.1.50), i can access all dockers on LAN20 i can access router gateway on LAN20 as well so locally everything works perfectly on local network. Whats working: When i connect with wireguard android app to my unraid from my phone using remote tunneled access over 4G network. I can: Access unraid on 192.168.1.10 Access unraid on 192.168.20.10 Access router admin page on 192.168.1.1 Access router admin page on 192.168.20.1 I can browse internet using Unraid's WAN IP. I can't from my phone over 4G: All dockers on LAN20 network (bridged dockers are working) Ping my PC from on 192.168.1.50 Trace route is same like in the past posts basically it stops at 10.253.0.2 and doesn't go further. What is really funny and weird is that i can ping my router on both LAN1 and LAN20 but i cannot ping my PC on 192.168.1.50 so it clearly indicates that not just dockers but any devices on network (except PFsense and Unraid, because basically one physical BOX) What i believe i have correct: LANs on router (if not i wouldn't be able to access dockers locally) Firewall rules (same as above i wouldn't be able to access anything in between network LAN1 and LAN20) Docker network settings. (If this wouldn't be right i wouldn't be able to access dockers locally from LAN1 to LAN20) What i didn't try yet: VMs are on br0 and trying to move them to br1 instead, but I am not sure what it will do to PFSense since its my main router. I am not afraid to try anything as i can access unraid on localhost. Any suggestions are welcome.
  6. It was the fan controller. The USB part was used to monitor power state plus the rgb bit i guess. I simply connected the plus +5V wire from usb cable to +5V molex to bypass the need of USB connection to the motherboard. The case is solved. Thank you for the hint about the USB part.
  7. I have 3 usb devices plugged in. 1 - Unraid USB stick 2 - Wireless keyboard receiver 3 - fan controller (Aerocool ACFC-P755910.01 Project 7 P7H1 RGB PWM Fan Hub - Black ) this is used only for the fans not rgb. I didn't really wanted to have this connected but it doesnt work if i dont plug the usb cable to motherboard. Hope any of this helps, thank you for your time.
  8. { "irq 16: nobody cared found on your server": "true" }
  9. Hi There, Fix common problem is spamming me with this warning and i keep pressing ignore but it always appear again. It says i should seek help on forum. Please see attached syslog and diagnostics. Any help much appreciated. Thank you tower-syslog-20190910-1931.zip tower-diagnostics-20190910-1930.zip