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 - weswitt

#1
20.7 Legacy Series / 20.7 Install Won't Boot
October 10, 2020, 05:09:58 PM
Currently running 19.7 and decided it is time to move forward. Created a USB boot device and attempted the install. The USB device boot up to the menu but then when I continue and the kernel starts to boot in hangs. I get the blue "booting" message and then it hangs every time.

My hardware is a QOTOM Q190G4-S02 with a Intel J1900 processor.
#2
19.7 Legacy Series / HAPROXY HTTP Rewrite
July 30, 2020, 07:02:37 PM
I have configured HAPROXY for my network and I'm seeing an issue that I don't know how to resolve.

When I issue an HTTP GET request to my address using HTTP OpnSense rewrites the request to HTTPS:

* Connected to weather.wittfamily.com (24.16.42.2) port 80 (#0)
> GET / HTTP/1.1
> Host: weather.wittfamily.com
> User-Agent: curl/7.64.0
> Accept: */*
>
< HTTP/1.1 301 Moved Permanently
< Location: https://weather.wittfamily.com/
< Content-Length: 0
< Date: Thu, 30 Jul 2020 16:48:47 GMT
< Server: OPNsense
<
* Connection #0 to host weather.wittfamily.com left intact

Is there a way that I can disable this?

My guess is that this is happening in the HAPROXY public service definition.
#3
Development and Code Review / Dev OPNSense Hosting
December 13, 2019, 11:02:22 PM
What is the recommended way to host a dev version of OPNSense for local dev work?  I tried setting up OPNSense in a VM but the presence of the VM on my network seemed to cause havoc with the traffic on my LAN.  Clearly something I'm doing wrong but some guidance as to how other approach this would be great.
#4
+1 I'm encountering the same problem. I cannot get NAT reflection for HTTP/S working.
#5
General Discussion / NAT Reflection Not Working
August 11, 2019, 06:17:07 PM
Thanks,

I've enabled NAT reflection in Firewall // Settings // Advanced and in the specific rule for HTTP & HTTPS. The behavior is different, but still does not work correctly. Now when I try to browse to the URL the browser just times out. Seems that the address is not being re-written correctly. Possibly there is another setting that I need to change?
#6
I have a web server on a machine in my LAN, IP address 192.168.1.176. This address is forwarded from the outside WAN by the URL http://wittfamily.com. Access to the web server from the WAN works perfectly. If I access that URL from inside my LAN it appears to be redirecting to router's website.

What config setting allows this to work??
#7
19.7 Legacy Series / Re: Won't Boot
August 02, 2019, 08:21:44 PM
thanks so much for the help. i have 19.7 opnsense installed, configured and running.
#8
I'm trying to install 19.7 and am hitting this bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172

According to the thread in the bug this has been fixed in the 11.3 kernel but you can work around it by changing the /boot/loader.conf to include kern.vty="sc".

My question is how can I change this file on the USB install media?
#9
19.7 Legacy Series / Re: Won't Boot
August 01, 2019, 12:18:56 AM
thanks unipacket, that seems like the *EXACT* problem I'm having. So I need to modify the /boot/loader.conf file on the bootable USB thumb drive. I've tried to do that but I cannot seem to mount the boot partition. When I try to mount the boot partition in Linux I get "wrong fs type, bad option, bad superblock on /dev/sdb2, missing codepage or helper program, or other error". When I try to mount the boot partition in FreeBSD I get the error: "error = 5".

What is the right way to mount the boot partition?
#10
19.7 Legacy Series / Won't Boot
July 31, 2019, 12:32:28 AM
I''ve been running pfSense for a few years and I would now like to move to opnSense. So I downloaded the latest 19.7 release, installed into a USB thumb drive and attempted to boot it on my firewall hardware. No joy. The system boots off the USB drive, loads the kernel modules and then displays the blue "booting" message. At this point the system hangs and makes no further progress.

My hardware is the QOTOM-Q190G4-S02. Again this hardware runs the latest pfSense perfectly. This is an Intel J1900 x86 system that I would think is perfectly acceptable.

Is this a known bug? Are there required BIOS changes necessary?