Messages

I had previously made 0 changes to the router but on a whim, or a lack of anything else that could be done, I restored the defaults and now I am seeing the expected behavior.

I can reach the UI but due to another router on the same network they often conflict, since I can not see the console, I cannot change the lan port.

I have set the primary console to VGA/EFI
Legacy boot is defined in the bios already but why would that change the console behavior?

So I changed the Video from Legecy to UEFI and I did not get any output, switched back to Legacy and getting to the same spot.

All I am getting is the point where it loads the kernel then I see a blinking cursor and that's it. From the live image I see the expected menu but once I boot to the image then I do not. From the boot selection mention I can see 5. Console : Video is selected.

I don't have a serial port on this device so I am blind as to what is going on. I have reinstalled about a few times now with the same result.

Due to a failed update I decided to reinstall OPNSense and grabbed the VGA image but I am not getting the same console as I once had, which allowed me to jump into the shell, is there something more I need to configure? I had made changes in Settings->Admin->Primary Console - I selected VGA and EFI and I do not get the menu I am expecting.

Any suggestions?

Original post: https://forum.opnsense.org/index.php?topic=22045.msg104737#msg104737

Need to know how to change the 1600x1200 settings you get on bootup? I have attempted to use tuneables vbe_max_resolution 1080p and screen.textmode 0 but still seems to be using 1600x1200

No one? Someone has to know this.

I have a KVM hooked to a Qotom-Q190G4N and its a garbarled display, is there some way to force it to 800x600 or something lower? Right now its forcing a 1600x1200 display.

I tried this: https://forum.opnsense.org/index.php?topic=12065.0

It did not work, so per the verbiage in that same file I added the info into the .local and it was even worse.

Running: OPNsense 20.7.8_4-amd64

I did look there before posting here. Anyways, @marjohn56 was kind enough to point me where I needed to go

Anyone care to let me know how to make the changes myself then? Or what directory to look into?

As a test I did fire up OpenVPN on my Synology NAS just to see if the behavior was the same and I am able to get to all of the IP's that I cant get to running OpenVPN on opnsense, I am pretty sure that the gateway for each of those is set to 192.168.1.1.

Access = ping, sorry I should have been more clear. Of the IP's I am not able to get to I am also not able to ping/route to those IP's. I can post what my server.conf says but there is hardly anything in it, its mostly default.

Code Select Expand

dev ovpns1
verb 1
dev-type tun
tun-ipv6
dev-node /dev/tun1
writepid /var/run/openvpn_server1.pid
script-security 3
daemon
keepalive 10 60
ping-timer-rem
persist-tun
persist-key
proto udp
cipher AES-256-CBC
auth SHA512
up /usr/local/etc/inc/plugins.inc.d/openvpn/ovpn-linkup
down /usr/local/etc/inc/plugins.inc.d/openvpn/ovpn-linkdown
local MYIP
client-disconnect "/usr/local/etc/inc/plugins.inc.d/openvpn/attributes.sh server1"
tls-server
server 10.0.8.0 255.255.255.0
client-config-dir /var/etc/openvpn-csc/1
username-as-common-name
auth-user-pass-verify "/usr/local/etc/inc/plugins.inc.d/openvpn/ovpn_auth_verify user 'Local Database' 'false' 'server1'" via-env
tls-verify "/usr/local/etc/inc/plugins.inc.d/openvpn/ovpn_auth_verify tls 'OpnSense' 1"
lport 1194
management /var/etc/openvpn/server1.sock unix
push "route 192.168.1.0 255.255.255.0"
push "dhcp-option DNS 10.0.8.1"
ca /var/etc/openvpn/server1.ca
cert /var/etc/openvpn/server1.cert
key /var/etc/openvpn/server1.key
dh /usr/local/etc/dh-parameters.4096.sample
tls-auth /var/etc/openvpn/server1.tls-auth 0
comp-lzo no
persist-remote-ip
float
push "route 192.168.1.0 255.255.255.0"


I take it this isn't a popular theme?

I can access some but not others, I made a xls of ones I cant reach compared to ones I cannot, I don't see a pattern.

I can access 192.168.1.1 but not 192.168.1.2 etc....

[Have you adjusted the priority (1 main and 2 alt) and weight(keep weight at 1 for both) settings in the single gateway options and the tier settings (1 main and 2 alt) in the group?]

@vico1959 I do have 1 question before answering all of the others:

Have you adjusted the priority (1 main and 2 alt) and weight(keep weight at 1 for both) settings in the single gateway options and the tier settings (1 main and 2 alt) in the group?

In my group I have the following:
WAN1 Tier 2
WAN2 Tier 1

Priority for the single's
WAN1 Priority 255
WAN2 Priority 250

Weight
WAN1 - Set to 1
WAN2 - Set to 1

However the verbiage in the docs are to set the weight to 1 on the lower link and set the weight to 2 on the higher link.

I have trigger level set to Packet Loss, High Latency. I did not choose the Member Down option because the link in the past, never goes down just stops routing due to upstream issues.

My question is, whats the advantage of setting the weight to 1 for both? And will this achieve what I am looking for which is to have my larger bw link be the primary (WAN2)

So with no one answering, does that mean no one is actually using OpenVPN?