i read in Mox documentation:
If MOX has just one Ethernet port it is LAN
If MOX has SFP, SFP is WAN and the rest of ports is LAN (including Ethernet port next to the power supply on MOX A)
If it has switch(es) and no SFP, then all ports in switch are LAN and the port next to the power source on MOX A is WAN
so ONLY when i exclude the SFP module, the port on Mox A is WAN, I didn’t notice that
That is why I asked about the SFP module…
OK, now we need to information from htp what parameter you should use, please exchange usernames with the string USERNAME and passords with the string PASSWORD before posting.
If e.g. htp requires a specific VLAN tag that would effortlessly explain why you do not get an IP address.
ohh yes i have forgot the access data, internet access is over PPPoE with a username and a password on a vlan and voice service over a another VLAN
That is debatable, there is evidence this second VLAN might not be necessary:
Die Information im HTP Kundencenter ist einfach falsch
Auch via TR69 wird kein 2. PVC mit VLAN10 und DHCP aufgesetzt. SIP läuft direkt über das normale WAN (in dem Fall bei HTP auf VLAN22). Also so, wie ich es eingerichtet habe.
oh that the information is false I didn’t even consider it. good to know. and that for years, really top performance
Well for that user the information was “false” and that might be the case for you as well, but that only affected the SIP telephony configuration, just keep that in mind for after we get your internet working…
@BlackMage2 so what is the status after almost a week, did you get TurrisOS up and running or did you decide to stick to another router?
yes, the turris mox works on the htp fiberbox, but i dont get the sfp modul working
What have you tried so far? And did you allow sufficient time between connection attempts, as some ISPs enforce a delay between being allowed to connect with diffrent routers/MAC addresses.
do you have to activate the serial connection on the Turris Mox separately?
i have tried a serial connection, i had followed that instructions: Serial connection - Turris Documentation . but there is always no answer with a serial connection via a USB adapter, it is correctly set to 1.8 volts
No idea, I do not have a MOX so can not offer much help. But why do you need serial access? Is that required to get the SFP to work? That would be puzzling.
no, not necessarily, but it would be very useful to always have access to the box. I don’t understand why the serial connection doesn’t work
Well, as I said, no first-hand experience with MOX (nor with serial consoles, so far never needed on under OpenWrt/TurrisOS).
So what is the status with the SFP, what does dmesg show when the SFP is plugged in and what do ifconfig and ethtool reveal about a plugged in SFP module?
then dmesg output that:
[11437.728237] sfp sfp: module removed
[11452.023347] sfp sfp: module LANCOM Systems SFP-AON-1 rev 2.0 sn LS22XXXXXXX dc 28-03-22
[11452.033194] sfp sfp: SC connector, encoding 8b10b, nominal bitrate 1.3Gbps +0% -0%
[11452.041357] sfp sfp: 1000BaseSX- 1000BaseLX- 1000BaseCX- 1000BaseT- 100BaseTLX- 1000BaseFX- BaseBX10+ BasePX-
[11452.052075] sfp sfp: 10GBaseSR- 10GBaseLR- 10GBaseLRM- 10GBaseER-
[11452.058751] sfp sfp: Wavelength 1310nm, fiber lengths:
[11452.064302] sfp sfp: 9µm SM : 20000m
[11452.068982] sfp sfp: 62.5µm MM OM1: unsupported/unspecified
[11452.075119] sfp sfp: 50µm MM OM2: unsupported/unspecified
[11452.081269] sfp sfp: 50µm MM OM3: unsupported/unspecified
[11452.087346] sfp sfp: 50µm MM OM4: unsupported/unspecified
[11452.093508] sfp sfp: Options: txdisable, txfault, los+
[11452.099114] sfp sfp: Diagnostics: ddm, intcal, rxpwravg
(lwl cable not connected)
OK, that seems to indicate that the kernel recognizes the SFP to some degree. Next question is, does the SFP show up in ifconfig and if yes with what interface/device name?
Full disclosure, I do not and did not operate an SFP module in my turris omnia (or any other device for that matter), so
hmpf what that means?
[ 15.113357] mvneta d0040000.ethernet eth1: configuring for 802.3z/1000base-x link mode
[ 15.125396] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 15.156198] IPv6: ADDRCONF(NETDEV_UP): eth1.22: link is not ready
Not sure, could you post the output of:
ifconfigethtool eth1here
root@turris:~# ifconfig
br-guest_turris Link encap:Ethernet HWaddr FF:FF:FF:52:75:D0
inet addr:10.111.222.1 Bcast:10.111.222.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
br-lan Link encap:Ethernet HWaddr FF:FF:FF:00:CF:CF
inet addr:192.168.179.23 Bcast:192.168.179.255 Mask:255.255.255.0
inet6 addr: fde7:adc1:9b87::1/60 Scope:Global
inet6 addr: fe80::da58:d7ff:fe00:cfcf/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15204 errors:0 dropped:0 overruns:0 frame:0
TX packets:1976 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4760735 (4.5 MiB) TX bytes:562219 (549.0 KiB)
eth0 Link encap:Ethernet HWaddr FF:FF:FF:00:CF:CE
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15395 errors:0 dropped:187 overruns:0 frame:0
TX packets:1976 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:532
RX bytes:5030163 (4.7 MiB) TX bytes:562219 (549.0 KiB)
Interrupt:10
eth1 Link encap:Ethernet HWaddr FF:FF:FF:00:CF:CF
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:532
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:11
eth1.22 Link encap:Ethernet HWaddr FF:FF:FF:00:CF:CF
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:21575 errors:0 dropped:0 overruns:0 frame:0
TX packets:21575 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7807994 (7.4 MiB) TX bytes:7807994 (7.4 MiB)
root@turris:~# ethtool eth1
Settings for eth1:
Supported ports: [ FIBRE ]
Supported link modes: 1000baseX/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 1000baseX/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: d
Wake-on: d
Link detected: no
OK, seems to be recognized as what it supposed to be good, but no link? Is the fiber plugged in?