KN-1910 doesn't work with Alcatel IK41VE1

[strange_v]

Hi.

I've bought an Alcatel IK41VE1 4G modem (as it's present in the list of supported devices), but unfortunately, it doesn't work.

After connecting to the router, the led starts blinking red, then blue, then constant blue (connected to 4G), and then after 10-30 sec, the cycle starts from the beginning.

When "Check the availability of the Internet" is disabled - the led on the modem always shows blue, but it doesn't provide internet.

As you can see on the screen, IP is not set. But it'll be here for some time after the modem reboot. The web interface is accessible on 192.168.1.1, it shows that the connection resets every 10 sec. KeeneticOS version is 3.8.5.4.

When connected to the laptop, there are no issues with the modem at all (tested for 20 - 30 min).

Any suggestion on what might be wrong? Thank you.

UPD: Added logs related to CdcEthernet0

CdcEthernet0.txt

Edited November 21, 2022 by strange_v
Added logs

[strange_v]

vst, you was right, thanks.

By modifying the JS code used to display the user interface, I managed to unlock hidden settings, select IPv4, and save a new profile. Now everything works.

In case someone will deal with the same issue - search for profileItemIptype.isActive in the modem's JS code.

Edited November 22, 2022 by strange_v
wording

[vst]

Now IPv6 it partially works: address is obtained, but prefix doesn't. LAN will not work with this configuration.

The only way to make it work is to somehow enable IPv4 on the modem.

[vst]

It seems that your modem is connected to IPv6 network. But the modem is connected to the router via IPv4. Could you enable IPv4 or IPv4/IPv6 in modem settings?

[strange_v]

18 minutes ago, vst said:

It seems that your modem is connected to IPv6 network. But the modem is connected to the router via IPv4. Could you enable IPv4 or IPv4/IPv6 in modem settings?

Good catch. I haven't noticed this (as I mentioned previously, I see the IPv4 address right after the modem restart, but it seems then it switches to IPv6).

Unfortunately, the modem settings are extremely limited, and there is nothing about IPv4/IPv6.

[vst]

Please try to enable IPv6 transport between modem and router by setting the following:

interface CdcEthernet0 ipv6 address auto
interface CdcEthernet0 ipv6 prefix auto

 

[strange_v]

1. IPv6 component was not installed, so I added it.

2. After execution of the suggested commands I see this on UI:

But the overall behavior is the same as before.

CdcEthernet0 - 02.txt

[vst]

It is also possible to follow a direct link and modify your profile settings(IP type):
http://192.168.1.1/default.html#settings/profileManagement.html

 

[strange_v]

Unfortunately, not in my case. For some reason, they decided to hide IP type option.

[vst]

By the way, I tried to use 464xlat on the router side to workaround the IPv6 only issue , but it doesn't work.

Quote

(config)> show interface CdcEthernet0/Clat0

               id: CdcEthernet0/Clat0
            index: 0
   interface-name: CdcEthernet0/Clat0
             type: Clat
      description:

           traits: Ip
           traits: Ip46
           traits: Clat

             link: up
        connected: yes
            state: up
              mtu: 1400
          address: 192.168.0.1
             mask: 255.255.255.255
           uptime: 380
           global: yes
        defaultgw: yes
         priority: 400
   security-level: public

             clat:
           ipv6-address: 2b00:1fa0:5d5:ae90:636c:6174:0:19
     ipv6-remote-prefix: 64:ff9b::/96

ping 8.8.4.4

Quote

tcpdump -i cdc_br0 -v -n ip6
14:28:41.136374 IP6 (hlim 63, next-header ICMPv6 (58) payload length: 64) 2b00:1fa0:5d5:ae90:636c:6174:0:19 > 64:ff9b::808:404: ICMP6, echo request, length 64, seq 256

 

[vst]

On 11/23/2022 at 1:42 PM, strange_v said:

Unfortunately, not in my case. For some reason, they decided to hide IP type option.

Right, it is not possible to modify standard profile. But you can create your own and set it as default.

[strange_v]

As I already said, IP type combobox isn't there, even on a new profile.

[drugold]

Try selecting a different value for the Protocol field.

[strange_v]

drugold, thank you for trying to help, but the problem is already solved for me.