Messages

1

Virtual private networks / Unable to connect to my domain when connected via Wireguard

« on: May 25, 2021, 10:23:29 pm »

So I have my Unraid server running with NGINX and I have all the correct port forwarding done where I can access my Organizr docker through my domain (https://mydomain.net).  Whenever I connect to Opnsense through Wireguard, I am no longer able to access the Organizr page, but I am able to still access any subdomains that I have setup (plex.mydomain.net, sonarr.mydomain.net, etc.) just not the default domain.  I can also access the Organizr page through it's local IP (192.168.1.2:8282).

I'm assuming I need to setup some rules within the firewall to route to the correct docker, I just don't know where to start.

Any help is appreciated!

2

21.1 Legacy Series / Re: Opnsense not receiving updated WAN from modem DHCP

« on: May 18, 2021, 02:18:43 am »

So I had an extended power outage and when everything powered back on, I ran into the same issue with Opnsense not able to get a DHCP offer from the modem/ISP.  Not sure what to do now.  I can attach my system log but it wasn't able to resolve the WAN IP until I spoofed my Opnsense router MAC onto my laptop, connected to the CM, and then connected Opnsense computer to CM.

Code: [Select]

2021-05-17T18:11:45 dhclient[78122] No DHCPOFFERS received.
2021-05-17T18:11:28 dhclient[78122] DHCPDISCOVER on em0_vlan99 to 255.255.255.255 port 67 interval 17
2021-05-17T18:11:14 dhclient[78122] DHCPDISCOVER on em0_vlan99 to 255.255.255.255 port 67 interval 14
2021-05-17T18:11:01 dhclient[78122] DHCPDISCOVER on em0_vlan99 to 255.255.255.255 port 67 interval 13
2021-05-17T18:10:54 dhclient[78122] DHCPDISCOVER on em0_vlan99 to 255.255.255.255 port 67 interval 7
2021-05-17T18:10:51 dhclient[78122] DHCPDISCOVER on em0_vlan99 to 255.255.255.255 port 67 interval 3
2021-05-17T18:10:49 dhclient[78122] DHCPDISCOVER on em0_vlan99 to 255.255.255.255 port 67 interval 2
2021-05-17T18:10:48 dhclient[78122] DHCPDISCOVER on em0_vlan99 to 255.255.255.255 port 67 interval 1
2021-05-17T18:10:48 dhclient[78122] DHCPDISCOVER on em0_vlan99 to 255.255.255.255 port 67 interval 1
2021-05-17T18:10:48 dhclient[8012] Starting delete_old_states()
2021-05-17T18:10:48 dhclient[39362] Removing states through old gateway '192.168.100.1' (new gateway '')
2021-05-17T18:10:48 dhclient[12880] Comparing Routers: Old: 192.168.100.1 New:
My CM IP is 192.168.100.1; I've tried refusing leases from that IP but it didn't correct the issue.

Code: [Select]

2021-05-17T18:18:46 dhclient[52446] No DHCPOFFERS received.
2021-05-17T18:18:42 dhclient[52446] DHCPOFFER from 192.168.100.1 rejected.
2021-05-17T18:18:42 dhclient[52446] DHCPDISCOVER on em0_vlan99 to 255.255.255.255 port 67 interval 4
2021-05-17T18:18:30 dhclient[52446] DHCPOFFER from 192.168.100.1 rejected.
2021-05-17T18:18:30 dhclient[52446] DHCPDISCOVER on em0_vlan99 to 255.255.255.255 port 67 interval 12
2021-05-17T18:18:28 opnsense[63780] /widgets/widgets/dyn_dns_status.widget.php: Aborted IPv4 detection: no address for em0_vlan99
2021-05-17T18:18:17 opnsense[29828] /widgets/widgets/dyn_dns_status.widget.php: Aborted IPv4 detection: no address for em0_vlan99
2021-05-17T18:18:15 dhclient[52446] DHCPDISCOVER on em0_vlan99 to 255.255.255.255 port 67 interval 15
2021-05-17T18:18:01 dhclient[52446] DHCPDISCOVER on em0_vlan99 to 255.255.255.255 port 67 interval 14
2021-05-17T18:17:51 dhclient[52446] DHCPDISCOVER on em0_vlan99 to 255.255.255.255 port 67 interval 10
2021-05-17T18:17:47 dhclient[52446] DHCPDISCOVER on em0_vlan99 to 255.255.255.255 port 67 interval 4
2021-05-17T18:17:45 dhclient[52446] DHCPDISCOVER on em0_vlan99 to 255.255.255.255 port 67 interval 2
This is the log after I spoofed the Opnsense computer MAC on my laptop.

Code: [Select]

2021-05-17T18:27:20 dhclient[52446] DHCPACK from 98.XXX.XXX.XXX
2021-05-17T18:27:20 dhclient[52446] DHCPREQUEST on em0_vlan99 to 255.255.255.255 port 67
2021-05-17T18:27:18 dhclient[52446] DHCPOFFER from 98.XXX.XXX.XXX
2021-05-17T18:27:18 dhclient[52446] DHCPDISCOVER on em0_vlan99 to 255.255.255.255 port 67 interval 16
2021-05-17T18:27:03 dhclient[52446] DHCPDISCOVER on em0_vlan99 to 255.255.255.255 port 67 interval 15
2021-05-17T18:26:56 dhclient[52446] DHCPDISCOVER on em0_vlan99 to 255.255.255.255 port 67 interval 7
2021-05-17T18:26:49 dhclient[52446] DHCPDISCOVER on em0_vlan99 to 255.255.255.255 port 67 interval 7
2021-05-17T18:26:44 dhclient[52446] DHCPDISCOVER on em0_vlan99 to 255.255.255.255 port 67 interval 5
2021-05-17T18:26:41 dhclient[52446] DHCPDISCOVER on em0_vlan99 to 255.255.255.255 port 67 interval 3
2021-05-17T18:26:39 dhclient[52446] DHCPDISCOVER on em0_vlan99 to 255.255.255.255 port 67 interval 2
2021-05-17T18:26:37 dhclient[52446] DHCPDISCOVER on em0_vlan99 to 255.255.255.255 port 67 interval 2

3

21.1 Legacy Series / Re: Opnsense not receiving updated WAN from modem DHCP

« on: May 12, 2021, 09:00:13 pm »

Well my system has been running fairly well so far; only one random disconnection but I was able to release/renew DHCP and get back up and running.

Thanks again for your help!

4

21.1 Legacy Series / Re: Opnsense not receiving updated WAN from modem DHCP

« on: May 11, 2021, 05:03:10 pm »

The graphic looks right, but the details in the tutorial are wrong.  The tutorial shows all ports also living in VLAN 1 (attached graphic).  That needs to be stripped out of Port 2.

Ok, I removed Port 2 from VLAN 1 as seen below.  I've also attached graphic of the PVID settings to make sure these are correct as well.

Assuming that these are both correct, I should be able to power cycle my modem and make sure that the Opnsense computer is receiving a WAN IP address from the CM, correct?

5

21.1 Legacy Series / Re: Opnsense not receiving updated WAN from modem DHCP

« on: May 11, 2021, 02:30:32 pm »

Remove VLAN 1 from Port 2.  The port to the cable modem needs to be isolated.

I thought the port for the modem needed to be connected to the same VLAN as the Opnsense computer.

My setup looks like the following:

A cable modem will only provide an address to the first MAC it sees.  Since you have a managed switch, it can be seeing the MAC of the switch management IP first.

This is what I thought the problem might be.

6

21.1 Legacy Series / Opnsense not receiving updated WAN from modem DHCP

« on: May 11, 2021, 12:14:16 am »

Had a ton of issues getting Opnsense setup correctly.  Ended up having to spoof the MAC address of a my TP link router to get an accurate WAN IP address.

Still getting intermittent connections that cause Opnsense to drop the WAN connection.  I tried spoofing the MAC address of the Opnsense computer for a laptop that I connected directly to the modem and that worked briefly as well.

My current setup is as follows:

1. Opnsense computer - connected to port 1 of TP link managed switch
2. Motorola MB8600 cable modem - connected to port 2 of TP link managed switch
3. TP Link Archer C7 w/ OpenWRT firmware (setup as a dumb AP) - connected on port 2 of port 3 of TP link managed switch
4. TP link TL-SG108E managed switch - used this tutorial to setup VLANs Link

I have Opnsense logs and screenshots if that will help deduce what I can do to fix this issue.