Topics

1

22.1 Legacy Series / [SOLVED] Since upgrade to 22.1.8 PPPoe not working anymore

« on: May 28, 2022, 05:44:01 pm »

Hi,

i use this dsl line only as backup and noticed, that it was down. The mpd shows only tries, but not response. So i thought, its the fault of the isp.  But no infos on this. The sync is there, all seems right. I configured my vigor 130 to use its own pppoe client and this worked immedially. 
Searched the logs and its really since the update to 22.1.8 , bevor the pppoe session worked.

The night bevor the update (around 2am) all worked:

Code: [Select]

<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="141"] [wan] IFACE: Up event
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="142"] [wan] IFACE: Rename interface ng0 to pppoe0
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="143"] [wan] IPCP: rec'd Configure Nak #2 (Ack-Sent)
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="144"] [wan]   IPADDR xx.xx.xx.xxx
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="145"] [wan]     xx.xx.xx.xx is OK
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="146"] [wan]   PRIDNS xx.xx.xx.xx
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="147"] [wan]   SECDNS xx.xx.xx.xx
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="148"] [wan] IPCP: SendConfigReq #3
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="149"] [wan]   IPADDR xx.xx.xx.xx
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="150"] [wan]   PRIDNS xx.xx.xx.xx
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="151"] [wan]   SECDNS xx.xx.xx.xx
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="152"] [wan] IPCP: rec'd Configure Ack #3 (Ack-Sent)
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="153"] [wan]   IPADDR xx.xx.xx.xx
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="154"] [wan]   PRIDNS xx.xx.xx.xx
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="155"] [wan]   SECDNS xx.xx.xx.xx
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="156"] [wan] IPCP: state change Ack-Sent --> Opened
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="157"] [wan] IPCP: LayerUp
<30>1 2022-05-25T02:20:08+02:00 OPNsense.local ppp 57539 - [meta sequenceId="158"] [wan]   xx.xx.xx.xx -> xx.xx.xx.xx
<30>1 2022-05-25T22:26:18+02:00 OPNsense.local ppp 57539 - [meta sequenceId="1"] [wan] error writing len 12 frame to b0: Network is down

The last line is caused from the update (i think), i did it right at that time.
And now, nothing works. From this point, it goes right that.

Code: [Select]

<30>1 2022-05-25T22:27:10+02:00 OPNsense.local ppp 57539 - [meta sequenceId="30"] [wan_link0] LCP: SendTerminateReq #4
<30>1 2022-05-25T22:27:10+02:00 OPNsense.local ppp 57539 - [meta sequenceId="31"] [wan_link0] LCP: LayerDown
<30>1 2022-05-25T22:27:14+02:00 OPNsense.local ppp 57539 - [meta sequenceId="32"] [wan_link0] LCP: SendTerminateReq #5
<30>1 2022-05-25T22:27:16+02:00 OPNsense.local ppp 57539 - [meta sequenceId="33"] [wan_link0] LCP: state change Stopping --> Stopped
<30>1 2022-05-25T22:27:16+02:00 OPNsense.local ppp 57539 - [meta sequenceId="34"] [wan_link0] LCP: LayerFinish
<30>1 2022-05-25T22:27:16+02:00 OPNsense.local ppp 57539 - [meta sequenceId="35"] [wan_link0] PPPoE: connection closed
<30>1 2022-05-25T22:27:16+02:00 OPNsense.local ppp 57539 - [meta sequenceId="36"] [wan_link0] Link: DOWN event
<30>1 2022-05-25T22:27:16+02:00 OPNsense.local ppp 57539 - [meta sequenceId="37"] [wan_link0] LCP: Down event
<30>1 2022-05-25T22:27:16+02:00 OPNsense.local ppp 57539 - [meta sequenceId="38"] [wan_link0] LCP: state change Stopped --> Starting
<30>1 2022-05-25T22:27:16+02:00 OPNsense.local ppp 57539 - [meta sequenceId="39"] [wan_link0] LCP: LayerStart
<30>1 2022-05-25T22:27:16+02:00 OPNsense.local ppp 57539 - [meta sequenceId="40"] [wan_link0] Link: reconnection attempt 1 in 2 seconds
<30>1 2022-05-25T22:27:18+02:00 OPNsense.local ppp 57539 - [meta sequenceId="41"] [wan_link0] Link: reconnection attempt 1
<30>1 2022-05-25T22:27:18+02:00 OPNsense.local ppp 57539 - [meta sequenceId="42"] [wan_link0] PPPoE: Connecting to ''
<30>1 2022-05-25T22:27:27+02:00 OPNsense.local ppp 57539 - [meta sequenceId="43"] [wan_link0] PPPoE connection timeout after 9 seconds
<30>1 2022-05-25T22:27:27+02:00 OPNsense.local ppp 57539 - [meta sequenceId="44"] [wan_link0] Link: DOWN event
<30>1 2022-05-25T22:27:27+02:00 OPNsense.local ppp 57539 - [meta sequenceId="45"] [wan_link0] LCP: Down event
<30>1 2022-05-25T22:27:27+02:00 OPNsense.local ppp 57539 - [meta sequenceId="46"] [wan_link0] Link: reconnection attempt 2 in 1 seconds
<30>1 2022-05-25T22:27:28+02:00 OPNsense.local ppp 57539 - [meta sequenceId="47"] [wan_link0] Link: reconnection attempt 2

I did downgrade the kernel to 22.1 and opnsense to 22.1.7, but it does not helped, this persists as it is.
I also tried to configure the old way with VLAN7 and on this the pppoe session (and disabled the vlan tag 7 addition in the vigor130), does not help, sadly.

Any hints on this ?

Thanks,
Ronny

Setup is:  APU2 with Vigor130 on the igb1 port, vlan 7 tag insserts the vigor130. The cable is directly from vigor130 to the apu2 on this port. I have an alias on this interface for the management address, that works flawlesse since ages. What is suspicious,  is that the counters only show out but NO in pakets since then:

Code: [Select]

Interfaces Overview for this:
Status up
PPPoE
up 
Uptime 00:00:0
MAC address 00:00:00:00:00:00 - XEROX CORPORATION
MTU 1492
IPv4 address pppoe/
IPv6 link-local fe80::20d:b9ff:fe4c:464/64
IPv6 address
In/out packets 0 / 36 (0 bytes / 3 KB)
In/out packets (pass) 0 / 36 (0 bytes / 3 KB)
In/out packets (block) 0 / 0 (0 bytes / 0 bytes)
In/out errors 0 / 0
Collisions 0

2

20.7 Legacy Series / [solved] 20.7.2 - FreeRadius and "users" File (not 20.7.2 related)

« on: September 04, 2020, 08:51:15 pm »

Hi,

since the 20.7.2 update my users (the link to the authorize file for radius" gets not updated anymore. I have had 2 users (mac pairs for mac based auth) which were not in the file but in the users list, apply or restart did not help.

The log sas "configd freedrius config generated" so all seems fine.

Any hint on how i can debug, whats going on ?

Thanks,
Ronny

3

20.1 Legacy Series / Freeradius - Remote Syslog not possible since 20.1 ?

« on: February 17, 2020, 03:35:17 pm »

Hi,

update from 19.7 to 20.1 worked great, as every time Good Job !

No critical issue, but it seems ,that i can not get the freeradius logs to my syslog server on the network. I included all targets (except configd and filter) to my syslog remote target. Radius Logs (Login OK, Rejected etc) are local vissible in the backend log but not get not send to the remote target.

Did I miss a configuration here, to make it possible, or is this simply missing atm ?

Thanks,
Ronny

4

German - Deutsch / eMail wenn PPPoe Fehler / Down / SSL-Zertifikat per Script hochladen

« on: December 21, 2018, 09:12:40 am »

Moin,

ich habe eine OPNSense (aktuelle Version) auf ner APU2C4 laufen, derzeit eher im Testbetrieb mit einer VDSL50 Leitung und Vigor 130 Modem und paar "unwichtigen" Clients.
Das rennt gut, irgendwann will ich auch den 2 Inet Zugang über Kabel auf das System legen, damit ich den aktuellen Router auch mal neu starten kann ohne Ausfall bei Updates.

2 Dinge sind jedoch noch offen, wo ich nicht weiterkomme und ein paar Infos benötigen würde:

1. Wenn die PPPoE Session down ist oder einen Fehler hat, kommt keine Info, ich finde auch nichts, wo ich sagen könnte: Schick ne Mail o.ä.  Wie macht Ihr das ?
Ich könnte auch per API von extern den Status bestimmt abfragen und dann agieren, wenn jemand hier einen Einsprungspunkt für mich hat, wie ich an die Infos komme.

2. Ich habe auf einem Zentralen Server die LetsEncrypt Zertifikate, da ich über die DNS Server das so deutlich einfacher erneuern kann und per Ansible verteilen. Bei pfSense hatte ich eine Script, welches die Zertifikate importieren konnte (aus dem pfSense /tmp verzeichnis unter angabe des namens (pem nutzte ich da), bei OPNSense hab ich hier bisher noch nichts gefunden, denke aber, das es da auch API Calls gibt, die man nutzen kann für die Prüfung und das eigentliche Importieren.
Hat da jemand schon was getan und kann mich dabei Untersützen ?

Danke Ronny