Vastattu

public IP address does not work with my SIM Card

  • 9 lokakuu 2019
  • 12 kommenttia
  • 313 katselukerrat

Hello Elisa.

I just recently bought Julkinen IP service for my data only SIM card.
Changed APN to internet 4 and expected to have fixed public IP address on my Miktorik LTE router.

But after I restarted my router I received new public IPv4 address.
Same applies to IPv6.

Is this a bug or a feature?

Great thanks.
icon

Vastauksen tähän kysymykseen jakoi Sokrates 9 lokakuu 2019, 13:38

Hello Elisa.

I just recently bought Julkinen IP service for my data only SIM card.
Changed APN to internet 4 and expected to have fixed public IP address on my Miktorik LTE router.

But after I restarted my router I received new public IPv4 address.
Same applies to IPv6.

Is this a bug or a feature?

Great thanks.

It is a feature. Elisa has no public fixed IP addresses for mobile subscriptions. They are all variable. If you need fixed IP , you must use some DDNS-service.
Katso alkuperäinen viesti

12 kommenttia

Käyttäjätaso 7
Hello Elisa.

I just recently bought Julkinen IP service for my data only SIM card.
Changed APN to internet 4 and expected to have fixed public IP address on my Miktorik LTE router.

But after I restarted my router I received new public IPv4 address.
Same applies to IPv6.

Is this a bug or a feature?

Great thanks.

It is a feature. Elisa has no public fixed IP addresses for mobile subscriptions. They are all variable. If you need fixed IP , you must use some DDNS-service.
Käyttäjätaso 7
Kunniamerkki +3
Julkinen IP gives you public IP to use, but it won't be fixed IP address. Fixed IP addresses can't be obtained on consumer connections from us, Corporate Customer side has some options available for that if you need that for business 🙂
Thanks. What is then julkinen IP service? What it gives to customer?

Any why Elisa is not giving fixed IPv6 even /64? What is the reason for that? IPv6 /64 costs almost 0 EUR.
Käyttäjätaso 7
Kunniamerkki +3
Julkinen IP gives you more open NAT profile (NAT 2 instead of NAT 3) that allows you to do stuff that you normally couldn't achieve 🙂
Käyttäjätaso 7
Kunniamerkki +3
Julkinen IP service enables you to have a dynamic public ip address for your mobile data.

Mobile data subscribers without Julkinen IP service are allocated a dynamic private ip address. In other words, you are behind carrier grade network address translation, CGNAT. Many online games and surveillance cameras do not work under these conditions.

If you need fixed IP , you must use some DDNS-service.

Even using a DDNS service, like dy.fi, you will still have a dynamic ip address with Elisa's Julkinen IP service. However, in most use cases having a fixed DNS name pointing to a dynamic ip address is sufficient and there is no need to have a fixed ip address.
Käyttäjätaso 7

If you need fixed IP , you must use some DDNS-service.Even using a DDNS service, like dy.fi, you will still have a dynamic ip address with Elisa's Julkinen IP service. However, in most use cases having a fixed DNS name pointing to a dynamic ip address is sufficient and there is no need to have a fixed ip address.

That's what I meant. 😉
Julkinen IP also under CGNAT

I got 100.123.122.82/32 ip address from Elisa's router.
But I got an idea, Julkinen IP opens firewall for lower ports and thats makes life easier to access network from outside world.

I am not interested in games, I am interested to access my security camera's and other stuff from any place with internet. For that purpose Fixed IP is very beneficial compare to DDNS as there are several "servers" in my network.
Käyttäjätaso 7
Kunniamerkki +3
Getting an 100.64.0.0/10 address, i.e. from range 100.64.0.0 – 100.127.255.255 implies that either the order process for Julkinen IP service has failed or the mobile router APN reconfiguration has not taken place.

Could you check Elisa's customer portal Oma Elisa to see if Julkinen IP service order has been processed and the service is indeed active? Some services still do not show up correctly on Oma Elisa. It is a good idea to double check how does your services show up on the old Oma Saunalahti portal as well.

Have you powered down your router at least once after ordering Julkinen IP service? The service changes might not become effective until the next time you re-register to the mobile network.

Are you sure that your router configuration change has committed?

Some routers are not very straightforward when setting the APN. Sometimes you must perform a manual disconnect before editing the APN. On some other routers you cannot edit the default configuration set at all, but must create a new configuration set, set the APN to internet4 and then activate the new configuration set.

* * *

If you have a number of servers around, it might be better to set up a VPN server and have all your sites connect to your VPN server. Then you can have fixed private ip addresses for all your cameras and route them through VPN. As an additional bonus, your cameras will become available only within your own VPN, which is a great security benefit.

Outgoing VPN connections, at least when using openvpn protocol, do not require Julkinen IP service. This way you would need only one public ip address for the VPN server. All other sites can manage with private ip addresses, which are the default for Elisa mobile broadband.
Getting an 100.64.0.0/10 address, i.e. from range 100.64.0.0 – 100.127.255.255 implies that either the order process for Julkinen IP service has failed or the mobile router APN reconfiguration has not taken place.

Could you check Elisa's customer portal Oma Elisa to see if Julkinen IP service order has been processed and the service is indeed active? Some services still do not show up correctly on Oma Elisa. It is a good idea to double check how does your services show up on the old Oma Saunalahti portal as well.

Have you powered down your router at least once after ordering Julkinen IP service? The service changes might not become effective until the next time you re-register to the mobile network.

Are you sure that your router configuration change has committed?

Some routers are not very straightforward when setting the APN. Sometimes you must perform a manual disconnect before editing the APN. On some other routers you cannot edit the default configuration set at all, but must create a new configuration set, set the APN to internet4 and then activate the new configuration set.


Thanks a lot. I checked OmaElisa and OmaSaunalahti. JuliknenIP is activated there.
Yes, I changed APN to internet4 and IP address on LTE interface is taken from DHCP. I wlll check it one more time. If nothing happens, will open support case.

Few days ago I had a case with OmaElisa and my old number, I could not change settings for it. Hopefully it is not related to each other.

But anyway, thanks for clarification.
If you have a number of servers around, it might be better to set up a VPN server and have all your sites connect to your VPN server. Then you can have fixed private ip addresses for all your cameras and route them through VPN. As an additional bonus, your cameras will become available only within your own VPN, which is a great security benefit.

Outgoing VPN connections, at least when using openvpn protocol, do not require Julkinen IP service. This way you would need only one public ip address for the VPN server. All other sites can manage with private ip addresses, which are the default for Elisa mobile broadband.


Yes, this is possible workaround but still believe that public static IP for several EUR per month is easier to maintain at home environment.
I removed IP address from LTE interface and after restart again received from range 100.64.0.0 – 100.127.255.255

Investigation continues.
Getting an 100.64.0.0/10 address, i.e. from range 100.64.0.0 – 100.127.255.255 implies that either the order process for Julkinen IP service has failed or the mobile router APN reconfiguration has not taken place.



Irritus.
Great thanks. I played with LTE APN settings and finally got IP from different subnet.

PS. Mikrotik has built in DDNS client, I will use it to get static IPv6 /48 network from www.tunnelbroker.net and separately LetsEncrypt certificates. Will be the solution for me to use AAA DNS records.

Osallistu keskusteluun