Messages

1

20.7 Legacy Series / Re: Enabled ssh / can't ssh

« on: September 12, 2020, 01:59:39 am »

I thought so too.

And yes to both your questions.

The PC I am trying to access from is in the VPN alias group to have its traffic go out to VPN, but I have connected to my wifi network as well (not in VPN group) and the same happens.

I'm assuming it's a rule somewhere, but I'm not sure how to troubleshoot it.

2

20.7 Legacy Series / Enabled ssh / can't ssh

« on: September 11, 2020, 05:45:51 pm »

Hi all,

I'm newer to OPNSense and pulling my hair out on something.

I enabled ssh yesterday to login from my local LAN to do a speed test directly from the CLI.  I'm having speed issues and am trying to gather data to utilize in my negotiations with my ISP. 

When I pull up putty and try to connect, it just times out.  This morning, I occasionally (probably 1 out of 5 attempts) get a "connection was closed by 192.168.1.1" message instead. 

How do I start looking at this?  To my knowledge, I have enabled ssh as specified (checked password auth and listen on all interfaces -- this is to be temporary). There are no firewall rules I can see out of the norm that might be blocking such action.  When I look at the logs, I see a pass from the anti-lockout rule, but no blocks.

I reinstalled ssh on opnsense, still same issues.

I would be very grateful for any assistance anyone could provide on this one!

3

20.1 Legacy Series / Re: Cannot set DNS to PiHole

« on: February 29, 2020, 01:36:05 pm »

First off, thanks so much for leading me to the resolution.  I'm very appreciative!

So I got to thinking about what you said, and I had an epiphany right as I was falling asleep last night that the gateway address for my pf box is different than what I set for this opn box!  So this morning I logged into the pi, did a repair, and set the static IP settings correctly. 

It still did not work.  Hmmm.

Eventually I had to manually edit the dhcpcd.conf file in /etc to get it to click -- but it did!  Maybe I'll open a bug for the pi-hole guys.  I would figure the static assignment screen in the setup/repair config would take care of it.

I've used the 5 beta and enjoyed, I'll set it up on this one soon too.

Once again, thanks so much for your help!

4

20.1 Legacy Series / Re: Cannot set DNS to PiHole

« on: February 29, 2020, 02:24:18 am »

It's the pihole.

It can't ping. 

I haven't set up any rules, it's only using the auto-generated rules at the moment.  Should I need a rule to allow outbound access from LAN?  Internet works fine with 1.1.1.1 -- do I need a rule to allow outbound on 53 from a source IP other than the firewall itself?

Thanks!

5

20.1 Legacy Series / Re: Cannot set DNS to PiHole

« on: February 29, 2020, 01:37:23 am »

one more for system

6

20.1 Legacy Series / Re: Cannot set DNS to PiHole

« on: February 29, 2020, 01:34:02 am »

Hey!

I appreciate your response.  I think this is what I'm doing.

The PI IP is on the same subnet.  I can ping it, and view the webgui.

I attached some screenshots in the hope they can shed some light where I'm going wrong.

Thanks!

7

20.1 Legacy Series / Cannot set DNS to PiHole

« on: February 28, 2020, 07:52:20 pm »

Hello all,

I'm brand new to OPNSense as of 3 hours ago, but had been using PFSense for about 2 years.

Some hiccups in getting started, mostly because I was moving too fast I think, but I have internet and DHCP leases working now for the basics, as long as I utilize a public resolver first.

I've been using Pi Hole for years as well, and have it configured on my network with a StaticIP, but every time I try to change OPNSense to utilize it, my name resolution (and therefore internet access) break.

How can I start to troubleshoot this?  I would appreciate any guidance!  I can see the queries leave the box in the firewall, and I can see them get forwarded successfully in pihole, but it's not making it back to the clients somehow?

Also, I have no gateway setup for my LAN, I can't remember if that's right -- I think it is.