shut up, I am connected with WIFIonICE
-
shut up, I am connected with WIFIonICE
-
shut up, I am connected with WIFIonICE
@awoo captive portal moment -
@awoo captive portal moment
@0x4d6165 actually nope, i checked iceportal.de right after I went through it lol
-
shut up, I am connected with WIFIonICE
-
@awoo DNS? WIFIonICE has its own DNS that overwrites iceportal.de to 172.18.whatever (local ipv4). there’s still a record for “iceportal.de” in the public dns for showing this
@wyldtom I didn't change any of the DNS settings, and with ICEs it does work! though it seems like ICs are set up differently?
-
@wyldtom I didn't change any of the DNS settings, and with ICEs it does work! though it seems like ICs are set up differently?
-
@wyldtom
WHAT
-
@wyldtom
WHAT
-
@awoo exactly my reaction. ICE sends MTU 1440 via option 26, while on an IC2 it sends MTU 1350 (and thus breaking the default wireguard config)
@wyldtom
aaaaaaaaa-
also, another thing which I find funny is that I can't access my infra via WIFI@DB typically, but it works with WIFIonICE lol
-
@wyldtom
aaaaaaaaa-
also, another thing which I find funny is that I can't access my infra via WIFI@DB typically, but it works with WIFIonICE lol
-
@awoo huh? Now I’m curious why.
btw: DBLounge sends MTU 1500 but only supports MTU 1462 (with broken pmtud) and drops traffic to 1.1.1.1
Now I’m curious why.
I'm as clueless as you are - and the fault isn't on my end from what I can tell.