Issues with PPPOE + 300mbps fiber + 192.168.144.1 hop

Issues with PPPOE + 300mbps fiber + 192.168.144.1 hop

I originally had the 100mbit fiber line. Everything appeared to work great. After upgrading to the 300mbps fiber line I am now going through a NAT box provided by Movistar. The reason I say this is because of my traceroute. 192.168.144.1 appears to be my gateway rather than me having a proper gateway that is not a NAT. I've read that this is because of me having a Dynamic IP. However, I have a static IP and always get the same IP when I reconnect my modem. Various services that I use are now broken because of this and my inability to be able to connect to anything running at home if both locations are behind a nat.

 

How do I go about having Movistar fix this? I don't speak Spanish and thus cannot communicate with Movistar. My Wife does speak spanish but she is not technical at all and I'm sure things get lost in translation. I also have a linux box acting as a router since the router provided was awful. I get a full 300mbps on the router server. My linux router is 100% not the problem here.

 

root@htpc-N56VZ:/etc# traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 192.168.144.1 (192.168.144.1) 1.107 ms 1.073 ms 1.012 ms
2 49.Red-80-58-99.staticIP.rima-tde.net (80.58.99.49) 12.003 ms 57.Red-80-58-99.staticIP.rima-tde.net (80.58.99.57) 10.235 ms 10.218 ms
3 1.Red-80-58-106.staticIP.rima-tde.net (80.58.106.1) 12.821 ms 12.801 ms 12.780 ms
4 * * *
5 google-ae2-gramadno2.net.telefonicaglobalsolutions.com (5.53.1.74) 10.537 ms 10.520 ms 10.501 ms
6 216.239.50.197 (216.239.50.197) 10.481 ms 216.239.50.199 (216.239.50.199) 10.538 ms 10.472 ms
7 209.85.248.55 (209.85.248.55) 10.297 ms 10.156 ms 209.85.246.223 (209.85.246.223) 10.873 ms
8 google-public-dns-a.google.com (8.8.8.8) 10.015 ms 10.183 ms 9.611 ms

 

root@htpc-N56VZ:/etc# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.144.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0

 

Mensaje 1 de 13
2.057 Visitas
12 RESPUESTAS 12

Helo

 

Reset the router to factory settings with the reset button on the back (press 10 seconds), check the PC data with ipconfig / all

 

Slu2.

Mensaje 2 de 13
2.043 Visitas

I have a linux server as my router. I do not use the router that Movistar provided. It shouldn't matter either though. Even when I tried with the router they supplied my traceroute was the same as it is now.

 

I set up the network we use at the office where I work. I also use a linux router, configured exactly the same as the linux router at home. I should be getting a real IP/Router at my first hop from home and not Movistar's 192168.144.1 IP address .

 

From the router at my office:

traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 40 byte packets
1 149.Red-80-58-67.staticIP.rima-tde.net (80.58.67.149) 10.827 ms 13.181 ms 9.329 ms
2 185.Red-80-58-88.staticIP.rima-tde.net (80.58.88.185) 17.964 ms 18.510 ms 19.920 ms
3 1.Red-80-58-106.staticIP.rima-tde.net (80.58.106.1) 20.535 ms 12.329 ms 11.940 ms
4 * * *
5 google-ae2-gramadno2.net.telefonicaglobalsolutions.com (5.53.1.74) 12.657 ms 14.180 ms 19.727 ms
6 216.239.50.195 (216.239.50.195) 19.349 ms
216.239.50.197 (216.239.50.197) 19.323 ms
216.239.50.199 (216.239.50.199) 11.709 ms
7 209.85.248.65 (209.85.248.65) 14.601 ms
72.14.239.103 (72.14.239.103) 12.272 ms
66.249.95.55 (66.249.95.55) 15.663 ms
8 google-public-dns-a.google.com (8.8.8.8) 15.253 ms 11.465 ms 19.495 ms

 

From my router at mtraceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 192.168.144.1 (192.168.144.1) 1.632 ms 1.567 ms 1.597 ms
2 181.Red-81-46-130.staticIP.rima-tde.net (81.46.130.181) 10.732 ms 57.Red-80-58-99.staticIP.rima-tde.net (80.58.99.57) 12.147 ms 49.Red-80-58-99.staticIP.rima-tde.net (80.58.99.49) 12.295 ms
3 1.Red-80-58-106.staticIP.rima-tde.net (80.58.106.1) 11.553 ms 11.527 ms 11.498 ms
4 * * *
5 google-ae2-gramadno2.net.telefonicaglobalsolutions.com (5.53.1.74) 10.047 ms 10.012 ms 9.983 ms
6 216.239.50.195 (216.239.50.195) 9.954 ms 216.239.50.197 (216.239.50.197) 10.464 ms 216.239.50.199 (216.239.50.199) 14.949 ms
7 66.249.95.55 (66.249.95.55) 10.739 ms 209.85.248.75 (209.85.248.75) 10.611 ms 216.239.46.59 (216.239.46.59) 11.092 ms
8 google-public-dns-a.google.com (8.8.8.8) 10.515 ms 10.399 ms 10.846 msy home:

 

Mensaje 3 de 13
2.035 Visitas

¿He has tried to do what you said you F650?



Si necesitas soporte técnico en averías de Móvil, Fijo, Movistar+ o Internet Fijo (cobre o fibra), puedes acceder a nuestro apartado de Soporte Técnico o rellenar este formulario. También puedes contactar con nosotros llamando al 1002.

 Si necesitas contratar Fibra Ópticacomprobar tu cobertura Adsl y Fibrao ver información sobre la instalación de la fibra visita nuestra página ADSL y Fibra en movistar.es 

Solución aceptada.png
Mensaje 4 de 13
2.020 Visitas

Even with a factory resert of Both the modem (Black Comtrend unit) as well as the bridge device (where the fiber plugs into) I am still seeing 192.168.144.1.

 

Here is the latest traceroute while using the Modem:

 

Josephs-MacBook-Pro: ~ $ joe 8.8.8.8 traceroute
traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 3,854 ms 4,884 ms 132 435 ms
2 192.168.144.1 (192.168.144.1) 203,632 ms 5,278 ms 6,885 ms
3 61.red-80-58-99.staticip.rima-tde.net (80.58.99.61) 15,461 16,570 ms ms
185.red-81-46-130.staticip. rima-tde.net (81.46.130.185) 15,303 ms
4 153.red-80-58-84.staticip.rima-tde.net (80.58.84.153) 15,086 19,456 ms ms *

 

Here is the routing table form my laptop:

 

Josephs-MacBook-Pro:~ joe$ netstat -rn
Routing tables

Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.1.1 UGSc 47 0 en0
127 127.0.0.1 UCS 0 0 lo0
127.0.0.1 127.0.0.1 UH 6 357149 lo0
169.254 link#4 UCS 0 0 en0
192.168.1 link#4 UCS 4 0 en0
192.168.1.1/32 link#4 UCS 1 0 en0
192.168.1.1 f8:8e:85:40:f2:71 UHLWIir 50 106 en0 1165
192.168.1.2 link#4 UHRLWIi 6 142 en0 7
192.168.1.10 0:90:a9:d5:aa:ba UHLWIi 2 404576 en0 1199
192.168.1.33/32 link#4 UCS 1 0 en0
192.168.1.33 24:a0:74:f1:5:80 UHLWI 0 25 lo0
192.168.1.39 link#4 UHLWI 0 2 en0
192.168.1.255 ff:ff:ff:ff:ff:ff UHLWbI 0 11 en0

 

 

Here is the latest traceroute / routing table while using my linux router:

 

Josephs-MacBook-Pro:~ joe$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
1 192.168.1.2 (192.168.1.2) 13.835 ms 5.809 ms 4.081 ms
2 192.168.144.1 (192.168.144.1) 14.967 ms 13.948 ms 10.588 ms
3 49.red-80-58-99.staticip.rima-tde.net (80.58.99.49) 19.119 ms
57.red-80-58-99.staticip.rima-tde.net (80.58.99.57) 15.499 ms
181.red-81-46-130.staticip.rima-tde.net (81.46.130.181) 20.052 ms
4 1.red-80-58-106.staticip.rima-tde.net (80.58.106.1) 21.316 ms 20.136 ms 20.555 ms

 

Josephs-MacBook-Pro:~ joe$ netstat -rn
Routing tables

Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.1.2 UGSc 63 0 en0
127 127.0.0.1 UCS 0 0 lo0
127.0.0.1 127.0.0.1 UH 6 357884 lo0
169.254 link#4 UCS 0 0 en0
192.168.1 link#4 UCS 3 0 en0
192.168.1.2/32 link#4 UCS 2 0 en0
192.168.1.2 30:85:a9:5:f1:14 UHLWIir 61 104 en0 1164
192.168.1.10 0:90:a9:d5:aa:ba UHLWIi 2 193704 en0 1194
192.168.1.39 link#4 UHRLWI 0 12 en0
192.168.1.40/32 link#4 UCS 1 0 en0
192.168.1.40 24:a0:74:f1:5:80 UHLWI 0 25 lo0
192.168.1.255 ff:ff:ff:ff:ff:ff UHLWbI 0 1 en0

 

It is most definitely within the Telefonica network that is keeping me behind the Telefonica NATD device located on 192.168.144.1

 

Thanks in advance!

Mensaje 5 de 13
2.009 Visitas

I originally had the 100mbit fiber line. Everything appeared to work great. After upgrading to the 300mbps fiber line I am now going through a NAT box provided by Movistar. The reason I say this is because of my traceroute. 192.168.144.1 appears to be my gateway rather than me having a proper gateway that is not a NAT. I've read that this happens because of me having a Dynamic IP. However, I have a static IP and always get the same IP when I reconnect with my router . Various services that I use are now broken because of this and my inability to be able to connect to anything running at home if both locations are behind a nat.

 

How do I go about having Movistar fix this? I don't speak Spanish and thus cannot communicate with Movistar. My Wife does speak spanish but she is not technical at all and I'm sure things get lost in translation. I also have a linux box acting as a router since the router provided was awful. I get a full 300mbps on the router server. My linux router is 100% not the problem here.

 

 

root@htpc-N56VZ:/etc# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.144.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0

 

Even with a factory resert of Both the modem (Black Comtrend unit) as well as the bridge device (where the fiber plugs into) I am still seeing 192.168.144.1.

 

Here is the latest traceroute while using the Modem:

 

Josephs-MacBook-Pro: ~ $ joe 8.8.8.8 traceroute
traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 3,854 ms 4,884 ms 132 435 ms
2 192.168.144.1 (192.168.144.1) 203,632 ms 5,278 ms 6,885 ms
3 61.red-80-58-99.staticip.rima-tde.net (80.58.99.61) 15,461 16,570 ms ms
185.red-81-46-130.staticip. rima-tde.net (81.46.130.185) 15,303 ms
4 153.red-80-58-84.staticip.rima-tde.net (80.58.84.153) 15,086 19,456 ms ms *

 

Here is the routing table form my laptop:

 

Josephs-MacBook-Pro:~ joe$ netstat -rn
Routing tables

Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.1.1 UGSc 47 0 en0
127 127.0.0.1 UCS 0 0 lo0
127.0.0.1 127.0.0.1 UH 6 357149 lo0
169.254 link#4 UCS 0 0 en0
192.168.1 link#4 UCS 4 0 en0
192.168.1.1/32 link#4 UCS 1 0 en0
192.168.1.1 f8:8e:85:40:f2:71 UHLWIir 50 106 en0 1165
192.168.1.2 link#4 UHRLWIi 6 142 en0 7
192.168.1.10 0:90:a9:d5:aa:ba UHLWIi 2 404576 en0 1199
192.168.1.33/32 link#4 UCS 1 0 en0
192.168.1.33 24:a0:74:f1:5:80 UHLWI 0 25 lo0
192.168.1.39 link#4 UHLWI 0 2 en0
192.168.1.255 ff:ff:ff:ff:ff:ff UHLWbI 0 11 en0

 

 

Here is the latest traceroute / routing table while using my linux router:

 

Josephs-MacBook-Pro:~ joe$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
1 192.168.1.2 (192.168.1.2) 13.835 ms 5.809 ms 4.081 ms
2 192.168.144.1 (192.168.144.1) 14.967 ms 13.948 ms 10.588 ms
3 49.red-80-58-99.staticip.rima-tde.net (80.58.99.49) 19.119 ms
57.red-80-58-99.staticip.rima-tde.net (80.58.99.57) 15.499 ms
181.red-81-46-130.staticip.rima-tde.net (81.46.130.181) 20.052 ms
4 1.red-80-58-106.staticip.rima-tde.net (80.58.106.1) 21.316 ms 20.136 ms 20.555 ms

 

Josephs-MacBook-Pro:~ joe$ netstat -rn
Routing tables

Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.1.2 UGSc 63 0 en0
127 127.0.0.1 UCS 0 0 lo0
127.0.0.1 127.0.0.1 UH 6 357884 lo0
169.254 link#4 UCS 0 0 en0
192.168.1 link#4 UCS 3 0 en0
192.168.1.2/32 link#4 UCS 2 0 en0
192.168.1.2 30:85:a9:5:f1:14 UHLWIir 61 104 en0 1164
192.168.1.10 0:90:a9:d5:aa:ba UHLWIi 2 193704 en0 1194
192.168.1.39 link#4 UHRLWI 0 12 en0
192.168.1.40/32 link#4 UCS 1 0 en0
192.168.1.40 24:a0:74:f1:5:80 UHLWI 0 25 lo0
192.168.1.255 ff:ff:ff:ff:ff:ff UHLWbI 0 1 en0

 

It is most definitely within the Telefonica network that is keeping me behind the Telefonica NATD device located on 192.168.144.1

 

Thanks in advance!

Mensaje 6 de 13
2.041 Visitas

@Manuev-Movistar @F650

 

Any help you can provide would be super

Mensaje 7 de 13
1.990 Visitas

@JoeOliveiro

 

Hi, Joe.

 

First I have to say you explain the problem very well. Second you can use the web https://translate.google.com and write it in English and translate it to Spanish, although you don't have to be worried about this: I suppose the engineers can translate it.

 

It's evident we have a real problem here with our conections. As you saw in my last posts 192.168.144.1 it happens to me too. 

 

You can see the title of this post is "We don't get our speed in contract", and your problem it's not this. 

 

I will try to translate the problem you have into Spanish:el usuario dice que la dirección 192.168.144.1 le aparece por tener IP fija en lugar de la IP dinámica y necesita que cada vez que reconecte el móvil le cambie dicha IP, porque le sitúa detrás de una NAT  alojada en esa IP.

 

Thank you for your post, but it doesn't seem to be the same problem we are dealing here.

Mensaje 8 de 13
2.009 Visitas

@ccartola Gracias for the help amigo! 

Mensaje 9 de 13
1.970 Visitas

@JoeOliveiro

 

You're welcome!

Mensaje 10 de 13
1.961 Visitas

I am still having this issue. Movistar has not fixed it after many months 😞

Mensaje 11 de 13
1.603 Visitas

I am still having this issue of Movistar putting me behind another NAT box that is not transparent. I cannot connect to any of my services behind my router.

 

@Manuev-Movistar Are you still with Movistar? We spoke many many months ago and you told me that they are would look in to it but I never heard anything back. Also, all my speed tests only show me as receiving 100mbit down and not 300.

Mensaje 12 de 13
1.572 Visitas

No new updates?

Etiquetas (1)
Mensaje 13 de 13
1.559 Visitas