Messages

1

General Discussion / Re: 19.1 in VirtualBox - WAN never picks up an address (0.0.0.0)

« on: June 05, 2019, 12:06:10 pm »

Thanks for the reply but I ended up using the pfsense VM that worked and copied my settings to it.  (It wasn't what I wanted to do but, I didn't see a lot of activity on this post so I wasn't going to sit around and wait for a reply that may never come.)  From there, I installed another SSD into my router, installed OPNsense and did my side-by-side config.

2

General Discussion / 19.1 in VirtualBox - WAN never picks up an address (0.0.0.0)

« on: May 29, 2019, 10:59:49 pm »

So, I'm attempting to move from pfsense to opnsense and I'm trying to load opnsense into a virtual environment so I can do a side-by-side transfer of most or all of my custom settings.  I've found videos and looked at various write-ups but nothing seems to be working.

I load the OS via the ISO and it comes up with what you see in the screen-shot.  The WAN interface either never shows IP or it shows an IP of 0.0.0.0.  In my troubleshooting, I've unplugged the LAN interface in the VM's settings and that's why the screen-shot shows nothing for the WAN.  I've installed it anyway and went into the CLI config and verified that the interfaces' MAKs match up with the vNICs I'm using so they're correct....  What am I missing?

Side note:
The same (cloned) VM will install and run pfsense without issue.

3

18.7 Legacy Series / Re: Cannot get Port Forward to Work - TCP-8443 to TCP-443

« on: October 06, 2018, 04:00:01 pm »

None that I can see but, the filtering on the live view is less than ideal.  I'm able to filter by "WAN" and I see everything hitting the WAN.  I can also filter by ":443" and see some traffic but it looks like it's all outbound.  If I filter by ":8443", I get nothing at all.

4

18.7 Legacy Series / Cannot get Port Forward to Work - TCP-8443 to TCP-443

« on: October 06, 2018, 02:38:11 pm »

I'm trying to forward TCP-8443 to a web server, listening on the standard HTTPS port, inside my home network.  The ISP blocks incoming TCP-80 and TCP-443 hence, I'm using that alternative port.  Again, I'm new to opnsense but this should be straigh forward; this used to work on my old pfsense setup

I followed this well written and concise tutorial. 

I went to Firewall > NAT > Port Forward and set it up.  I allowed it to create its own firewall rule in Firewall > Rules > WAN. See the following screen shots.

The browser, when I go to visit the site, says the following which leads me to believe I'm actively getting blocked:

Code: [Select]

ERR_CONNECTION_REFUSED

5

18.7 Legacy Series / Re: Dynamic DNS - Google Domains - Not Updating

« on: October 06, 2018, 12:46:06 pm »

Figured it out...

6

18.7 Legacy Series / Dynamic DNS - Google Domains - Not Updating

« on: October 06, 2018, 04:19:14 am »

Is anyone else having trouble with getting the Google Domains dynamic DNS service to work?  I've just moved from pfsense to opnsense and I'm trying to duplicate my settings. 

My notes don't show that I need anything special...

• Service type
• WAN
• Hostname
• Username
• Password

I hit up the Google Domains site and reset the creds for the user and pass so I know they're correct.  When I save and force the update, it shows a cached IP of 0.0.0.0.  The logs show:

Code: [Select]

opnsense: /usr/local/etc/rc.dyndns: Dynamic DNS: (Error) Hostname does not exist or does not have dynamic DNS enabled
What's worse is I have several dynamic DNS services running and the one for Google Domains is the only one not working.  Any ideas?