Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Kapman

#1
18.1 Legacy Series / Re: DMZ trouble with DNS
March 25, 2018, 08:25:35 PM
Hello everyone,
Adding a screen capture of the rules I setup in my DMZ to help others out and just in case some other folks notice this can be improved.
#2
18.1 Legacy Series / Re: DMZ trouble with DNS
March 25, 2018, 06:08:59 PM
Turns out adding a rule is the correct solution!
This is fixed.

Thanks Bitman!
#3
18.1 Legacy Series / Re: DMZ trouble with DNS
March 25, 2018, 12:32:33 AM
I have Unbound DNS set with "Network Interfaces" set to "All".  I assumed that implied the DNS server (opnsense) should be available on the network.
The DNS server is 192.168.2.1 and the Ubuntu server is 192.168.2.100 in this case.  I'm pinging from 192.168.2.100 to 192.168.2.1.  The reverse works.
I don't think I need a rule for that, do I? 
#4
18.1 Legacy Series / [Solved] DMZ trouble with DNS
March 24, 2018, 11:00:48 PM
Hello,
I have a Ubuntu server on an DMZ I just configured that cannot resolve domain names.

I'm currently running version 18.1.5.
I have the interface enabled and setup with a static ip.
Unbound DNS is being used with the setting "Network Interfaces" set to "All".

There is a single Ubuntu server installed on the DMZ.  I can ping it from the LAN & OpnSense.
The Ubuntu server is set with the correct DNS server (the opnsense server).
The Ubuntu server cannot resolve domain names.  From the Ubuntu server, I cannot ping the OpnSense machine where Unbound DNS is running.

Any ideas about what I'm doing incorrectly here?

Thanks in advance!
#5
17.7 Legacy Series / Re: Can't access GUI via lan ip
January 27, 2018, 09:52:26 PM
I restarted, same issue.  At this point is re-installation the best option?
#6
17.7 Legacy Series / Re: Can't access GUI via lan ip
January 16, 2018, 06:29:30 AM
I also reloaded all services just in case it might help, still the same issue.
#7
17.7 Legacy Series / Re: Can't access GUI via lan ip
January 16, 2018, 06:26:06 AM
Thanks for the tip.  I just tried that and while the ip does change successfully, I still can't access the webgui at that address.  Is there a default when re-assigning that turns off access to the webgui over ip address?
#8
17.7 Legacy Series / Re: Can't access GUI via lan ip
January 16, 2018, 04:10:42 AM
Thanks for the quick reply.
I did assign the lan interface, but that only gave me access to the GUI via a domain name.  What must I do to get 192.168.1.1 to work instead?  I plan on reusing the domain for another use.
#9
17.7 Legacy Series / Can't access GUI via lan ip
January 16, 2018, 03:58:23 AM
Hello everyone,
By mistake, I disabled my lan interface and locked myself out of OPNsense GUI as well as eliminating access to internet. SO I went to the console on the actual pc running OPNsense and re-assigned the the lan interface to the same IP address it was previously.  The internet access came back, but I can no longer access to webgui via ip address. I can use a domain name on the lan (doesn't work when using the same domain external to the lan which is good), but not the ip.  Does anyone know which setting I must change to gain access back using the ip address (192.168.1.1)?