Messages

1

General Discussion / Re: Power outage, results in IP address errors

« on: September 25, 2024, 09:06:06 am »

Thanks Greg,

No, I don't need 10gbps today. This network card is to my 2 WANs (200mbps and 600mbps), but if my ISP provide more  throughput, I want be a bit prepared to new increase. The network cards price (1gbps and 10gbps) are very simillar.

Best regards,

2

General Discussion / Re: Power outage, results in IP address errors

« on: September 23, 2024, 11:57:56 pm »

Hello,

Thanks for help.

Yes, my Intel dual Intel Pro/1000 82576 have in a issue a one port and I will swap.

The i350 card is only accessible in my country in 1 GB, but I can buy Intel X540-t2 10GB. This network card can be works fine in last verison of opnSense?

Best regards,

3

General Discussion / Power outage, results in IP address errors

« on: September 19, 2024, 03:04:53 pm »

Hello,

I Have the latest version of OPNsense (24.7).

I had a power outage and when power was reapplied, my opnsense box came back up, but my WAN NICs (Intel dual Intel Pro/1000 82576) are not recognize. Then I tick the "Prevent Interface Removal" on all used interfaces option and all NICs are recogized, but after the automatic return of the energy fault, my WANs interfaces are not  load your respective configuration.

This issue only accour on power outage. If I restart or shutdown with GUI opnsense, works fine.


My NICs are:

- Realtek PCie GbE Family - onboard (Re0) -> Not in use
- Realtek PCie GbE Family - single network card (Re1) -> LAN
- Intel dual Intel Pro/1000 82576 (igb0, igb1) -> WAN1 (DHCP), WAN2 (PPoe)


I appreciate anyone who can help!

Regards,

4

23.7 Legacy Series / Re: forced reboot results in IP address errors

« on: September 18, 2024, 11:07:40 pm »

Greetings

Totally new to opnsense - - still running system without it being 'the system' (opnsense is running but another router is doing my work at present).
Had a power outage - - that means a forced reboot (power goes down and I have a short time using a ups to shut down all systems active). Power was just terminated (not a clean shutdown - - - using a system shutdown).
When power was reapplied the system came back up but some things that had been set were incorrect.
System had been set with igc0 and igc1 activated.
igc0 was WAN and set to IPV4/DHCP
igc1 was LAN and set to IPV4/192.168.1.1/24

After reboot igc0 was listed as LAN and 192.168.1.1
igc1 was listed but had no ip address

So I used 1) Assign interfaces to change igc0 to WAN and igc1 to LAN
then I used 2) Set interface ip address to set igc0 to  IPV4/DHCP

presently see LAN (igc1) blank and WAN (igc0) as v4/DHCP4: xx.xx.xx.xx (ip address from my isp)

(system setup)

optical converter ---- 5 port unmanaged switch ----  router (192.168.50.1) ------  24 port unmanaged switch ---- wired and wireless clients (various 192.168.50.xx)
                                                                          ------ opnsense box (  ) ------   no load at present

Questions:

Did I set up something wrong initially so that igc0 and 1 were changed upon reboot?
If so - - - what do I change?
Ports igc2 through 4 are available - - - I want to use say igc2 for a wireless AP when opnsense goes live - - - - is that a good idea?


TIA

Hello,

I have the same issue. I Have the latest version of OPNsense (24.7).

After tick the 'Prevent Interface removal', all NICs are recognized, but after the automatic return of the energy fault, my WANs interfaces are not  load your respective configuration.


My NICs are:

- Realtek PCie GbE Family - onboard (Re0) -> Not in use
- Realtek PCie GbE Family - single network card (Re1) -> LAN
- Intel dual Intel Pro/1000 82576 (igb0, igb1) -> WAN1 (DHCP), WAN2 (PPoe)


I appreciate anyone who can help!

5

General Discussion / Authentication LDAP

« on: January 30, 2023, 09:28:20 am »

Hello,

Due to me not being able to integrate Squid with Secure LDAP from Google Workspace,  I'm switching from pfsense to opnSense.


I have Proxy Squid and Captive Portal integrated with Google Workspace secure LDAP, via Stunne. This work's fine.

I have users in differents subdomains of my principal domain. eg: subdomain1.domain.com, subdomain2.domain.com, subdomain3.domain.com.

I put theses subdomains in Base DN of the autentication server (System: Access: Servers), but on a few cases, I'm have the same username in differents subdomains. Are distincts persons.

So, because this , i want authenticate with username@subdomain.domain.com.

It's possible?


Regards,

6

17.1 Legacy Series / Web Proxy can't authenticate with LDAP

« on: March 29, 2017, 12:57:04 am »

Hello,

I set up an LDAP authentication server (SAMBA 4). I did a test on "System: Access: Tester" and the connection works fine.

The LDAP server is used with SAMBA4 AD. In Windows 10 clients all users/groups can connect.

I configured the proxy web service to connect with LDAP authentication server, but when I open a internet browser (Chrome, Firefox) do not make the connection. The internet browser show a dialog box to authenticate with proxy server.

I put any valid user and your respective password, but don't work. See atached image.




Regards,
Marcelo Costa
Porto Alegre - Brazil

7

General Discussion / Re: Webfilter based in usergroups

« on: March 20, 2017, 04:40:21 am »

+ 1.

For me, this is a priority feature.

8

16.7 Legacy Series / Re: LDAP Issue - Could not connect to the LDAP server

« on: November 22, 2016, 04:20:02 pm »

Ok...

thanks

9

16.7 Legacy Series / Re: LDAP Issue - Could not connect to the LDAP server

« on: November 22, 2016, 02:45:19 am »

Hi Franco,

Thanks for notice.

On This moment, OpnSense is not work with samba4? There is not a workaround?

10

16.7 Legacy Series / Re: LDAP Issue - Could not connect to the LDAP server

« on: November 16, 2016, 03:46:02 am »

Hi Franco,

I want use Proxy/Squid of the OpnSense, authenticated with AD (SAMBA4).

Following read a few tutorials, they talk that the first action is create a connection with LDAP server, but when I try create the connection, I get the informative message:

"Could not connect to the LDAP server. Please check your LDAP configuration."


Thanks,
Marcelo Costa

11

Portuguese - Português / Re: Como autenticar por LDAP

« on: November 04, 2016, 02:28:03 pm »

Ninguém?

12

16.7 Legacy Series / Re: LDAP Issue - Could not connect to the LDAP server

« on: November 04, 2016, 02:06:28 pm »

noone?

13

16.7 Legacy Series / LDAP Issue - Could not connect to the LDAP server

« on: October 21, 2016, 08:55:41 am »

Hello,

I'am a new user and I am setting up OPNsense 16.7.6-amd64 (OpenSSL) hosted on Xenserver 7.

I am trying to set up an LDAP authentication server against a local Active Directory domain controller (SAMBA 4) to use proxy.

I was on "System" -> "Access" -> "Servers" and put the following configs:

Hostname or IP address: <AD_IPADDRESS>
Port: 389
Transport: TCP-Standard
Protocol version: 3
User DN: CN=Administrator, CN=Users, DC=domain, DC=local
Password: <ADMINISTRATOR_PASSWORD>
Level: One Level
Base DN:DC=domain, DC=local


When I click the Select button in the Containers section, I get the informative message:
"Could not connect to the LDAP server. Please check your LDAP configuration."

I appreciate any help.


Marcelo Costa
Porto Alegre - Brazil

14

Portuguese - Português / Re: Como autenticar por LDAP

« on: October 21, 2016, 03:16:19 am »

Olá,

Gostaria de aproveitar o tópico, pois não estou conseguindo fazer a conexão com meu AD SAMBA4 em rede local.


Fui em System -> Acess -> Servers e fiz as seguintes definições:

Hostname or IP address: <Endereço IP do AD>
Port: 389
Transport: TCP-Standard
Protocol version: 3
User DN: CN=Administrator, CN=Users, DC=dominio, DC=local
Password: <senha do usuário administrator>
Level: One Level
Base DN:DC=dominio, DC=local


Ocorre que ao clicar no botão [Select], para selecionar um container, não é possível fazer a conexão, mostrando a seguinte mensagem: "Could not connect to the LDAP server. Please check your LDAP configuration."


Não sei se o problema é nas informações de conexão ou de NAT.

Obs: Estou utilizando o OpnSense como uma máquna virtual do Xenserver e já fiz ajustes do NAT.


Agradeço quem puder ajudar.


Abraço,
Marcelo