Omnia cannot connect to FTTH of Deutsche Telekom

I have the same problem here, set eth2.7 in /etc/config/network, tried the username with and without the # marks, but the interface is still flipping between up and down. Disabling autonegotiation with ethtool didn’t help either.

@mskr have you ever found a solution to this?

No sorry. Didn’t have time but plan to look at this again soon.

OK. I’m making some progress - I disabled the “Easy Login” on telekom.de, and set the username so that there’s just one # before the 0001, and no @t-online.de at the end. i.e. something like

option username ‘002222222222555555555555#0001’

now the interface doesn’t swithc between up and down anymore, and a new interface pppoe-wan is created:

pppoe-wan Link encap:Point-to-Point Protocol
inet addr:X.X.X.X P-t-P:62.155.247.164 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:60 errors:0 dropped:0 overruns:0 frame:0
TX packets:74 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:2619 (2.5 KiB) TX bytes:4088 (3.9 KiB)

but that’s all - I still can’t get to the internet, even the ping to 62.155.247.164 (which I suppose should be the gateway) fails.

OK. So 62.155.247.164 is probably not the gateway, but “remote IP address”. (Whatever that is - I have zero knowledge of how PPPoE works.) anyway I tried to get the debug log from ppp, and got this:

    Sep 10 18:21:04 turris pppd[21174]: Plugin rp-pppoe.so loaded.
    Sep 10 18:21:04 turris pppd[21174]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
    Sep 10 18:21:04 turris pppd[21174]: pppd 2.4.7 started by root, uid 0
    Sep 10 18:21:04 turris pppd[21174]: Send PPPOE Discovery V1T1 PADI session 0x0 length 12
    Sep 10 18:21:04 turris pppd[21174]:  dst ff:ff:ff:ff:ff:ff  src d8:58:d7:01:12:95
    Sep 10 18:21:04 turris pppd[21174]:  [service-name] [host-uniq  b6 52 00 00]
    Sep 10 18:21:04 turris pppd[21174]: Recv PPPOE Discovery V1T1 PADO session 0x0 length 42
    Sep 10 18:21:04 turris pppd[21174]:  dst d8:58:d7:01:12:95  src 28:8a:1c:ef:ec:ad
    Sep 10 18:21:04 turris pppd[21174]:  [AC-name GORJ00] [host-uniq  b6 52 00 00] [service-name] [AC-cookie  85 9c cb 29 91 8b fd 30 9b 94 88 00 74 a3 21 2a]
    Sep 10 18:21:04 turris pppd[21174]: Send PPPOE Discovery V1T1 PADR session 0x0 length 32
    Sep 10 18:21:04 turris pppd[21174]:  dst 28:8a:1c:ef:ec:ad  src d8:58:d7:01:12:95
    Sep 10 18:21:04 turris pppd[21174]:  [service-name] [host-uniq  b6 52 00 00] [AC-cookie  85 9c cb 29 91 8b fd 30 9b 94 88 00 74 a3 21 2a]
    Sep 10 18:21:04 turris pppd[21174]: Recv PPPOE Discovery V1T1 PADS session 0x3cc9 length 42
    Sep 10 18:21:04 turris pppd[21174]:  dst d8:58:d7:01:12:95  src 28:8a:1c:ef:ec:ad
    Sep 10 18:21:04 turris pppd[21174]:  [service-name] [host-uniq  b6 52 00 00] [AC-name GORJ00] [AC-cookie  85 9c cb 29 91 8b fd 30 9b 94 88 00 74 a3 21 2a]
    Sep 10 18:21:04 turris pppd[21174]: PADS: Service-Name: ''
    Sep 10 18:21:04 turris pppd[21174]: PPP session is 15561
    Sep 10 18:21:04 turris pppd[21174]: Connected to 28:8a:1c:ef:ec:ad via interface eth2.7
    Sep 10 18:21:04 turris pppd[21174]: using channel 3
    Sep 10 18:21:04 turris kernel: [ 6931.073881] pppoe-wan: renamed from ppp0
    Sep 10 18:21:04 turris pppd[21174]: Renamed interface ppp0 to pppoe-wan
    Sep 10 18:21:04 turris pppd[21174]: Using interface pppoe-wan
    Sep 10 18:21:04 turris pppd[21174]: Connect: pppoe-wan <--> eth2.7
    Sep 10 18:21:04 turris pppd[21174]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x5fe3add9>]
    Sep 10 18:21:04 turris pppd[21174]: rcvd [LCP ConfReq id=0x92 <mru 1492> <auth pap> <magic 0x63ce33e5>]
    Sep 10 18:21:04 turris pppd[21174]: sent [LCP ConfAck id=0x92 <mru 1492> <auth pap> <magic 0x63ce33e5>]
    Sep 10 18:21:04 turris pppd[21174]: rcvd [LCP ConfAck id=0x1 <mru 1492> <magic 0x5fe3add9>]
    Sep 10 18:21:04 turris pppd[21174]: sent [LCP EchoReq id=0x0 magic=0x5fe3add9]
    Sep 10 18:21:04 turris pppd[21174]: sent [PAP AuthReq id=0x1 user="002494196152551136296656#0001" password=<hidden>]
    Sep 10 18:21:04 turris pppd[21174]: rcvd [LCP EchoRep id=0x0 magic=0x63ce33e5]
    Sep 10 18:21:04 turris pppd[21174]: rcvd [PAP AuthAck id=0x1 ""]
    Sep 10 18:21:04 turris pppd[21174]: PAP authentication succeeded
    Sep 10 18:21:04 turris pppd[21174]: peer from calling number 28:8A:1C:EF:EC:AD authorized
    Sep 10 18:21:04 turris pppd[21174]: sent [IPCP ConfReq id=0x1 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
    Sep 10 18:21:04 turris pppd[21174]: rcvd [IPCP ConfReq id=0xb1 <addr 62.155.247.164>]
    Sep 10 18:21:04 turris pppd[21174]: sent [IPCP ConfAck id=0xb1 <addr 62.155.247.164>]
    Sep 10 18:21:04 turris pppd[21174]: rcvd [IPCP ConfNak id=0x1 <addr 87.183.126.42> <ms-dns1 217.6.165.41> <ms-dns2 62.157.140.155>]
    Sep 10 18:21:04 turris pppd[21174]: sent [IPCP ConfReq id=0x2 <addr 87.183.126.42> <ms-dns1 217.6.165.41> <ms-dns2 62.157.140.155>]
    Sep 10 18:21:04 turris pppd[21174]: rcvd [IPCP ConfAck id=0x2 <addr 87.183.126.42> <ms-dns1 217.6.165.41> <ms-dns2 62.157.140.155>]
    Sep 10 18:21:04 turris pppd[21174]: local  IP address 87.183.126.42
    Sep 10 18:21:04 turris pppd[21174]: remote IP address 62.155.247.164
    Sep 10 18:21:04 turris pppd[21174]: primary   DNS address 217.6.165.41
    Sep 10 18:21:04 turris pppd[21174]: secondary DNS address 62.157.140.155
    Sep 10 18:21:04 turris pppd[21174]: Script /lib/netifd/ppp-up started (pid 21373)
    Sep 10 18:21:04 turris netifd: Network device 'pppoe-wan' link is up
    Sep 10 18:21:04 turris netifd: Interface 'wan6' is enabled
    Sep 10 18:21:04 turris netifd: Network alias 'pppoe-wan' link is up
    Sep 10 18:21:04 turris netifd: Interface 'wan6' has link connectivity 
    Sep 10 18:21:04 turris netifd: Interface 'wan6' is setting up now
    Sep 10 18:21:04 turris netifd: Interface 'wan6' is now up
    Sep 10 18:21:04 turris netifd: Interface 'wan' is now up
    Sep 10 18:21:04 turris pppd[21174]: Script /lib/netifd/ppp-up finished (pid 21373), status = 0x1
    Sep 10 18:21:05 turris firewall: Reloading firewall due to ifup of wan (pppoe-wan)
    Sep 10 18:21:05 turris kresd[21549]: [system] warning: hard limit for number of file-descriptors is only 4096 but recommended value is 524288
    Sep 10 18:21:05 turris kresd[21549]: [priming] cannot resolve '.' NS, next priming query in 10 seconds
    Sep 10 18:21:07 turris firewall: Reloading firewall due to ifup of wan6 (pppoe-wan)
    Sep 10 18:21:15 turris kresd[21549]: [priming] cannot resolve '.' NS, next priming query in 10 seconds
    Sep 10 18:21:25 turris kresd[21549]: [priming] cannot resolve '.' NS, next priming query in 10 seconds
    Sep 10 18:21:35 turris kresd[21549]: [priming] cannot resolve '.' NS, next priming query in 10 seconds

There’s two DNS servers listed, and I can ping both of them, but I cannot get anywhere else - e.g. ping to 8.8.8.8 fails.

Hey anything new here? I am now trying again to make it work…

Does not work for me. WAN interface still flipping between up and down. You can also see it at the LED blinking.

Foris still says: WAN port has no link or it hasn’t been configured yet. Your internet connection probably won’t work.

I don’t understand what it even means for WAN to have link. Isn’t that like pulling and plugging the cable all the time? Is my cable defect? I don’t think so since I tried multiple.

I even turned on force link as described in the other thread.

Still everything the same.

Looking closely at the logread, I spotted

turris kresd[4101]: [priming] cannot resolve '.' NS, next priming query in 10 seconds

every time before the WAN interface goes down.

Could it be a DNS problem?

In the end I gave up and put Telekom’s Speedport modem between the Fiber modem and the Omnia. I’ll try again at some point, but right now I don’t have time to fiddle with the network settings at the German location.

does the speedport not have inklud fiber thingy? i am just worried, since i am using atm cuda (copper) via tae and the speedport as a dsl modem and the omia is routing and connecting my network to the telekom isp network.
last week i had the oportunity to switch to fiber. i like to have ftth and therefor i am looking to remove the speedport.

No the router by Deutsche Telekom (Speedport) and the modem are different devices.

Citing moeller0 about the modem:

No, the device offering the ethernet port is called ONT and acts as copper ethernet to GPON over optical fiber converter. You could get an ONT-SFP, and Deutsche Telekom (unlike most other german FTTH-ISPs) will provision customer owned ONTs assuming they follow the required specifications (you need to contact Telekom in that case), but for starters you are better off with the Telekom ONT.

The modem/ONT might be in your basement.

Btw. I am not a Deutsche Telekom customer currently because I moved and I only use the Omnia as LAN device. Still let us know if you are successful with your plan to remove the speedport :slight_smile:

1 Like

Maybe to be clear, in German router include dsl modems like a FRITZ!Box p. So the ones provided by German isps do so.