Messages

1

General Discussion / Vigor 130 SKY MER and Opnsense

« on: April 27, 2024, 12:04:03 pm »

Spent all of last Sunday trying to get this to work, and a few hours through the week but made no progress at all.

I have NOW (SKY) broadband currently connected using a TP link router, which I want to migrate across to opnsense via a Vigor 130 ADSL Modem.

it appears that the Vigor needs to be configured as a Bridge thereby letting Pfnsese negociate a DHCP lease.

I have configured the vigor in bridge mode, disabled PPP and enabled MPoA as per this guide: https://www.draytek.co.uk/support/guides/kb-vigor-130-bridge and the DSL light is on (not flashing) so I can only assume it has established a connection.

Then I need to configure the WAN in opnsense to use DHCP Option 61 as per this guide: https://docs.opnsense.org/manual/how-tos/SkyUK.html

I have followed that guide, probably a dozen times starting with a factory reset, but it never is able to get an IP lease.

After configuration and "apply" there's a delay of about 5 minutes when it time outs and of course no connection.

Tried rebooting afterwards but it never gets a lease.

Does anybody have this working with Vigor 130 & SKY/NOW as I am all out of ideas.

2

23.1 Legacy Series / Re: 23.1.11 and zeroteier interface

« on: June 30, 2023, 04:16:28 am »

I just uninstalled completely (including interface) rebooted, all was good.

I then reinstaled zerotier, setup the interface, confirmed that it was connected, and rebooted and same problem, no internet / wan.

So for me at least, zerotier is broken on 23.1.11

3

23.1 Legacy Series / 23.1.11 and zeroteier interface

« on: June 30, 2023, 03:58:48 am »

I updated to 23.1.11 a few hours ago, and after the reboot, lost all WAN / Internet connections.

After spending some time looking at the logs and not seeing any errors, I disabled the zerotier interface and it all came alive again.

During reboot, if the zerotier interface is enabled, all outbound traffic is blocked, as soon as I disable the interface and reboot, everything is back to normal.

If the interface is disabled during boot, and I then manually enable it again after bootup, everything is ok, until the next reboot.

It may be a coincidence that this happened at the same time as the update, but the zerotier install was done a few months ago, and i've not seen any similar issues.

Interested to hear if anyone else is experiencing this or has any ideas on the cause or solution ?

4

Virtual private networks / Wireguard Unable to use hostname as Endpoint

« on: May 12, 2023, 12:02:18 pm »

I need to use a hostname as the host is a dynamic IP.

wireguard supports Peer Endpoints as both IP addresses and hostnames, but if I set a hostname in the opnsense Endpoint, the settings get saved, but when applied, the wg handshake fails.

The hostname:port is saved correctly to the

Code: [Select]

/usr/local/etc/wireguard/wgX.conf file.

I noticed that the pinger fails to start, and if I try and manually restart the wireguard service from the command line I get an error:

Code: [Select]

[#] ifconfig wg create name wg5
[#] wg setconf wg5 /dev/stdin
Name does not resolve: `somedomain.xxx.net:51820'
Configuration parsing error
[#] ifconfig wg5 destroy
ifconfig: interface wg5 does not exist
So my guess is that the script which attempts to resolve the endpoint, is probably configured to only regex filter an ip address and that is why the resolve is failing and the connection never succeeds.

The strange thing is that I have 2 wireguard configs that both use a hostname, one on wg2 and the other on wg5, the one on wg2 starts successfully but wg5 does not.

I have compared the configs between wg2 and wg5, as well as the interface and gateway settings for both and as far as I can tell they are both configured the same way, other than of course the hostname and ip settings.

Is anyone else successfully running multiple wg interfaces using hostnames as the Endpoints ? 

Is there a fix / workaround for this ?