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

Topics - topasio

#1
Hello everybody,

I noticed a strange behavior when upgrading from 22.7.2 to 22.7.9.

Before the update, my interfaces are looking like that:

P101_LAN (igb1) -> v4: 192.168.101.1/24
P100_MGMT (igb0) -> v4: 192.168.100.1/24
P102_DMZ (igb2_vlan102) -> v4: 192.168.102.1/24
P103_SERVER (igb2_vlan103) -> v4: 192.168.103.1/24
VLAN_PARENT_REQUIRED (igb2) ->

You can see, that there is a ip set on every interface but not on igb2, cause that is only used for vlans and I needed to set a blank interface in order to get vlan running after upgrading from version 21 to 22.

After the latest update from 22.7.2 to 22.7.9, I am in trouble. I am forced to setup ip-addresses manually after every reboot cause OPNsense is not able to set the ip for igb1 and igb0 anymore:

P101_LAN (igb1) ->
P100_MGMT (igb0) ->
P102_DMZ (igb2_vlan102) -> v4: 192.168.102.1/24
P103_SERVER (igb2_vlan103) -> v4: 192.168.103.1/24
VLAN_PARENT_REQUIRED (igb2) ->

In the assignment menu I can see on both versions the same output:

igb0             xxxxxxx (I do not want to post my mac adresses here ...)
igb1             xxxxxxx
igb2             xxxxxxx
igb2_vlan102      00:00:00:00:00:00 VLAN tag 102, parent interface igb2
igb2_vlan103     00:00:00:00:00:00 VLAN tag 103, parent interface igb2

What I already tried:
- I checked the config.xml manually for stale interfaces - but looks good
- Removed a old openvpn configuration that was not longer in use
- Because OPNsense is running in a VM (proxmox), I am using virtio (paravirtualized). I changed for testing purpose to e1000 and vmxnet3 but that makes no difference.

Did you experience any similar behavior in virtual OPNsense installations and did you find a fix for that?

Cheers
Topasio
#2
General Discussion / Persistent proxy settings
January 22, 2021, 10:27:39 AM
Hello everyone,

I found many topics about configuring a proxy for OPNsense to access update server, suricata update etc.

- https://forum.opnsense.org/index.php?topic=3833.msg17998#msg17998
- https://forum.opnsense.org/index.php?topic=12098.msg55401

To set a proxy server I needed to configure this files:

/root/.cshrc


setenv HTTP_PROXY http://proxy:8080
setenv HTTPS_PROXY http://proxy:8080
setenv http_proxy http://proxy:8080
setenv https_proxy http://proxy:8080
setenv FTP_PROXY http://proxy:8080
setenv ftp_proxy http://proxy:8080


/usr/local/opnsense/service/conf/configd.conf


[environment]
## at the end of this section
HTTP_PROXY=http://proxy:8080
HTTPS_PROXY=http://proxy:8080
http_proxy=http://proxy:8080
https_proxy=http://proxy:8080
FTP_PROXY=http://proxy:8080
ftp_proxy=http://proxy:8080


/usr/local/etc/pkg.conf


pkg_env : {
    http_proxy: "{http://proxy:8080}"
    https_proxy: "{http://proxy:8080}"
}


This works like a charme and even after a reboot BUT after an update, the settings above are gone (only pkg.conf is not affected) ...

Is there any better or offical method, to use a proxy server?

Or is there a way to keep the settings persistent?

Cheers

Topasio