I followed along and had all the traffic go through that connection. Is it possible to create an alias so I can state which devices go through and which ones don't?
@crazyvanilla03Ай бұрын
Why am I not getting Tailscale as translation address?
@ronaldvargo4113Ай бұрын
This has provided a great getting started with dealing with CGNAT with 5G and StarLink ISP's. Setting up a cloud hosts VPS and then creating a site-to-site VPN with Wireguard to bring traffic into my network for hosted services is my goal.
@boomtown7190Ай бұрын
Helped me out, Thank you
@anand-nb4bbАй бұрын
Hi Bro can you please make a detailed step by step video on configuring Pfsense OpenVPN with split tunneling & configure Ubuntu as a VPN client. Please, it's a request. Kindly reply Thanks & regards,
@RobertoRubio-ij3msАй бұрын
Awesome video mate. Thanks heaps.
@thomashong72 ай бұрын
Absolutely the best video on wireguard and pfsense! I have re-watched it several times because your teaching of routing, interface, firewall rules, wireguard config, and how it all relates is explained so clearly and thorough. Thank you!
@Ginita122 ай бұрын
we missed you and your videos.
@TheK0tYaRa2 ай бұрын
God dammit man i always forget AllowedIPs
@JohnFilion3 ай бұрын
Thanks for putting this video together. Is it still necessary to create the outbound NAT rules? I tried setting this up, and I can't specify "Tailscale address" for the NAT Address. Has the procedure changed, or did I do something wrong?
@John-zs5nw4 ай бұрын
How do I get the tailscale address option for the NAT address?
@MegaVorian4 ай бұрын
That's great! But what if I need to access both networks from outside using a WireGuard client? How should I approach this solution?
@danygagnon84465 ай бұрын
This is amazing !
@jocelyn-n-tech5 ай бұрын
why did you stop making videos??? this one was excellent!
@cheooo075 ай бұрын
Great video. Thank you. A tip would be that when working with internet dynamic IP we can use a dynamic DNS for endpoint IP, that way if our public IP changes we should be good establishing the tunnel. I've been using Duck DNS and so far so good.
@dotnetfx40i936 ай бұрын
why pfsense will not control traffic tailscale...WTF, i should trust to tailscale .....by fact i will not trust, and by that reason rules on tailscale admin panel will not help me to trust 22:00
@fbifido26 ай бұрын
How does one backup & restore Koha database or Koha system itself to restore just incase something happen? How often should one backup?
@fbifido26 ай бұрын
Can you do a video on upgrading from Koha 20.5 to 23.11?
@fbifido26 ай бұрын
Do you know how to convert WinISIS 1.53 Database into Koha system ???
@fbifido26 ай бұрын
Hi, Can you please do an updated setup video of Koha ? Debian 12.5 or/& Ubuntu 24.04 Koha 23.11 with Latest supported versions of ElasticSearch, Plack, Memcached, and MariaDB. Please & Thanks.
@danroberts20557 ай бұрын
i'm at my wits end. I have two pfsense devices 1. PFSense Plus behind StarLink and 2. PFSense CE behind T-Mobile. I have tailscale running on both with nat rules on both and I can get from the Tmobile device to the StarLink device but I can't get from the StarLink device to the TMobile device. both show routes correctly in pfsense and both ping using tailscale ping but when I tried to reach the Tmobile router from the StarLink Router I get nothing. HELP! I have scanned the web and watched every YT video I can... don't know what's happening. ... only thing I can think is starlink is a 100. network....$ This doesn't happen if i'm on a phone using tailscale and try to get to either. I can get to both via my phone just not from the starlink device to the tmobile device.
@PeterNordin8 ай бұрын
Maybe I'm stupid or I miss somethinh essential. When I try to set up the Hybrid Outbound NAT I stumble on some problem. I set Interface to Tailscale as you showed, I set Source to Network or Alias and insert the subnet of my LAN interface Then down at Translation when I try to set Address to Tailscale address I can't find it in the dropdown list. I first thought you made an alias, but I see a space. Why can't I see the Tailscale Address under Translation Address?
@nathansalt57658 ай бұрын
I have the same problem. Under routes the Tailscale subnets show up there but the gateway is listed as link# and not tailscale. So there is no tailscale gateway to point to
@RafedwinAbreu8 ай бұрын
Use network or alias and put the tailscale ip address 100.xx.xx.xx it should work fine.
@PeterNordin8 ай бұрын
@@RafedwinAbreu thanks, and what subnetmask to us /24 /32
@ks313-g8o8 ай бұрын
nice.. helped a lot to get my head around this topic!
@allaboutcomputernetworks8 ай бұрын
Excellent video.....👍
@inside0ut9 ай бұрын
THE BEST WireGuard video on KZbin. Not only does everything get explained perfectly, but the walkthrough was the only one to get it working for me.
@darkenaxe9 ай бұрын
You are a very good teacher ! Thank you for this.
@manofwar93079 ай бұрын
For anyone following this guide still, make sure you use different listening ports for each tunnel. When you make the config file, after generating the private key, you should be able to enter a custom listening port by clicking "advanced settings." If you don't use different listening ports, one of the tunnel gateways will remain offline.
@vlaktorbb9 ай бұрын
Thanks for this awesome indepth video. But how can you ping devices on the tailscale network from behind the pfSense? I tried to setup a outbound NAT rule but the nat alias is missing. I've tried to setup it via an network alias, but this isn't working sadly. Seems this part is broken in the latest 23.09.1 update.
@RafedwinAbreu9 ай бұрын
Use network or alias and put the tailscale ip address 100.xx.xx.xx it should work fine.
@briane97299 ай бұрын
Fantastic Guide! and with well delivered insights into the workings of pfsense and the pitfalls one could encounter. Thank you for all your hard work creating the wireguard package and this great video!
@Hi5ist9 ай бұрын
Great video! Still having something wrong... If I test with ping in the pfsense diagnostic tool it works perfect, but it doesn't work if i do ping from y pc, I do research with no success, do yo have some clue?
@mistakek9 ай бұрын
24:57 I couldn't do this part. When I went to NAT, select hybrid, and then create the mapping, on the interface, I could select Mullvad(interface group), but for the Translation Address the option to select the interface address wasn't there, so I just had to create 2 maps, 1 for each of the tunnels but still using Mullvad(interface group) for the interface, and use each Mullvad interface for the translation address. It works, just annoying to have to create 2 mappings per vlan
@Djinn1129 ай бұрын
@Christian McDonald We haven't seen any updates to WireGuard in a long time. Could you please provide information on the current status? Are you still actively working on it??
@ko_3x33510 ай бұрын
Thanks for this Video. It helped a lot to unverstand the basics of wireguard and to finish my project.
@systemofapwne10 ай бұрын
Wait a minute: Aren't you supposed to add "Site 2"-IPs to the "Site 1 AllowedIPs" in order to make sure, that "When calling an IP in the range of Site2 on Site 1, it goes through the tunnel"? At around 19:00, you add "Site 1 IPs" to the "Allowed IPs" of "Site 1". Nevermind: I skipped over your explanation that "white theme = Site 1 & dark theme = Site 2". You did all correct and I was just confused/skipped too much.
@andersostlund11 ай бұрын
Excellent!
@nodd8511 ай бұрын
Awesome video. I used this setup for a Wiregaurd VPN connection from my phone to my home, and my mobile laptop to my home. When I connect to my home via the wireguard vpn from my laptop, on the interface statistics widget I get around 20-40 "errors out" per minute. I don't get the same result when connecting via wireguard vpn from my phone, that doesn't give me any "errors out" on the interface statistics widget on the dashboard. The connection works from my laptop, but I'm not sure why I'm getting these errors. Running the VPN for about a half hour gives me 1000 "errors out." Any idea where I can start to try and fix this?
@StefanWeichinger11 ай бұрын
Is the Outbound NAT rule still necessary or maybe set under the hood by the package already? testing this in dec-2023 and I can't even choose "Tailscale address" as NAT interface in a new Outbound NAT rule. Trying to route to a subnet connected via IPSEC ...
@809594508811 ай бұрын
Use network or alias and put the tailscale ip address 100.xx.xx.xx it should work fine.
@LordDemonos11 ай бұрын
Every time I break Wireguard I come back and this video helps me fix it. Thanks again!!
@geepriest Жыл бұрын
brilliant stuff...but how do I access shared resources on my LAN via hostname and not IP
@wawesh254 Жыл бұрын
Amazing video. Keep up the great work!
@mikeclites8407 Жыл бұрын
Two years later and your effort is still paying off. Thank you sir. You explained the /32 interface in a way no one else had for me. Much appreciated!
@gdewey1 Жыл бұрын
seems like on pfsense new version (23.09) you cannot assign NAT translation to Tailscale IP / 32. anyone experience this or am I missing something. I was able to follow instructions with out a problem on the last version
@Jooohn64 Жыл бұрын
same for me :(
@809594508811 ай бұрын
did you find any solution for this issue?
@gdewey111 ай бұрын
@@8095945088 I reported this to netgate and they admit is was abug that was going to be cover in the next release. the solution is to manually add the 100.x.x tailscale IP /32 to the fields. They released a new update and now it shows tailscale networks but its wrong, I still need to use a direct (hardcoded) value in the field. hope this helps.
@Shabba-k2x4 ай бұрын
Stumbled across a thread on netgate forums , for the latest version you only need to create a wan rule for udp destination port 41641, for any source and any destination (could play about with exact addresses if you want to make more secure). This allowed all my clients roaming to have a direct connection to my home network, especially my jellyfin server for on the go streaming.
@21Lettere Жыл бұрын
An IPv6 tutorial would be great, maybe with a method to avoid IPv6 traffic leak to the WAN interface instead of going into the VPN tunnel.
@4Covenant Жыл бұрын
You can do the same scheme but with a third site. greetings
@marktomlinson6922 Жыл бұрын
great explanation, I have one question for yourself or anyone else reading this, so in this site1 to site2 setup pfsense1 to pfsense2 for a device behind pfsense 1 router how do you get it to be able to use the DNS from pfsense 2 to resolve and connect to a device behind pfsens2 router
@swikkvibes6145 Жыл бұрын
How would I migrate my koha instance from 14 on ubuntu to Koha 23
@dogbreath7777 Жыл бұрын
Excellent video.....finally somebody who explains tunnel routing.....gets a like subscribe bell and a share !!!
@MEConcepcionP Жыл бұрын
Hey. How can you use a wan failover on one side of the wireguard tunnel?
@gdewey1 Жыл бұрын
Excellent work Chris!! loved your material and detail on the explanation