Topics

1

German - Deutsch / IPv6 HE.Net Tunnel nicht erreichbar bis Interface update

« on: August 28, 2017, 03:15:37 pm »

Ich habe einen HE.Net tunnel, der nach der Einrichtung super funktiert hat.
Nun habe ich das Problem, dass nach einem Neustart der Tunnel nicht funktioniert(Gateway down laut WebIf)

Wenn ich jetzt unter Interfaces=>"Tunnelbroker_V6" auf speichern und anschließend auf übernehmen drücke,
funktioniert es sofort ohne probleme.

Das Tunnelbroker_V6 ist dem GIF tunnel zugewiesen.
Dieser hat als Parent das WAN-Interface welches einem PPPoE Interface zugewiesen ist.

Ich tippe hier mal auf ein Timing-Problem nach dem Hochfahren... bin aber etwas ratlos, da ich keine möglichkeit finde, die Reihenfolge festzulegen in der die Interfaces initialisiert werden.

LG,
jwe

2

17.7 Legacy Series / [SOLVED][Fix included in 17.7.1] PPPOE Crash

« on: August 10, 2017, 02:13:23 am »

UPDATE 28.08.2017:
The Problem has been solved and the fix is implemented in 17.7.1.
Cause was Multiple AC's on the PPPoE Line which where not correctly handled when a session
was already opened.
Thanks you for fixing this issue



UPDATE NOT-SOLVED:
After letting it run after the BIOS Setting it ran good until i tried to rename the WAN<->PPPoE Interface,
which lead to the same crashing as before.

UPDATE/RESOLVED/WTF:
I could fix the problem by disabling "Deep S5 State" in BIOS
Going to run the System from live-usb now until i am 100% sure that this is all... grrr..WTF...



=====ORIGINAL POST FROM HERE====


I now had a few crashes using 17.7 and pppoe connection.

Realtek Network Cards,
tried disable and enable hardware vlan tagging.

PPPoE via VLAN => Instantly crashing
PPPoE without VLAN(set vlan via switch) => possibly crashing after some time or when i rename the interface from opt1 to anything...

Crash means, system is showing a few 1000 lines on screen scrolling for about a minute, possibly creating a crashlog and rebooting. again and again until i remove the network cable from the pppoe port.

I already sent in some crash reports via the reporter in the webconfigurator.

If i can help with anything more, please let me know.

~jwe

3

16.7 Legacy Series / DNS Resolver host and domain override not working

« on: December 10, 2016, 05:55:22 pm »

Hi, i upgraded to 16.7.10.
I am using unbound/dns resolver with some domain and host overrides.

Since the update these are ignored, seems similar to https://forum.opnsense.org/index.php?topic=4041.0 but i am using the resolver, not the forwarder.

for example i set internalnet.local to forward to dns server at 10.4.4.1.
if i do nslookup for host.internalnet.local via opnsense i get a server error("Server failed") while google.com for example work as it should

if i do nslookup via ssh from opnsense host to server 10.4.4.1 for host.internalnet.local it works. Seems like just the forwarding is broken.

Same seems to be broken for host overrides.

Any ideas?