Navigation is blocked

[johnpoz]

Then call you ISP… you getting a 192.168.100.2 is not going to work on a cable modem.. You should have a public IP from your ISP..

[abrougui]

i have another connection from a rooter. the public private adress is 192.168.1.1.
now i have changed my WAN to be conected with my rooter with the public adress 192.168.1.196 and my lan with 192.168.183.1. but i have the same problem. i can ping but i cant navigate

[johnpoz]

Are you saying that devices connect to this router 192.168.1.1 work?

When you say you can ping… Are you pinging by name and resolving this to an IP?

ping www.google.com

Pinging www.google.com [[b]172.217.4.228] with 32 bytes of data:
Reply from 172.217.4.228: bytes=32 time=11ms TTL=51
Reply from 172.217.4.228: bytes=32 time=14ms TTL=51

What are the rules you have on your lan of pfsense?  Its still the default any any rule?  You have nothing in floating?  Your outbound nat is automatic.  Your not running proxy??  Your browser is not trying to use a proxy you can not get to?

Do a simple traceroute..

From windows machine it would be

tracert -d www.google.com

Tracing route to www.google.com [172.217.4.228]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms  192.168.9.253
  2    9 ms    9 ms    8 ms  50.4.132.1
  3    11 ms    11 ms    8 ms  76.73.171.73
  4    10 ms    9 ms    10 ms  76.73.164.121

leave out the -d if you want name resolution.. Can slow it up..

[kejianshi]

I'm waiting for him to plug a computer or laptop directly into that modem before I worry this any longer.

Need to confirm the modem is even working before messing around with pfsense anymore.

[johnpoz]

^ agreed… 192.168.100 does not scream Im on the internet.

Putting another router in front of it so pfsense now gets that natted IP on its wan doesn't help anything.. Especially when not stating that something else directly connected to this router works..

[kejianshi]

Yeah - The more I look at what johnpoz said earlier the more I'm think we are beating on pfsense and the modem isn't even passing an IP like it should.

Easy to check by plugging directly into the modem.  (Might have to deal with the ISP about the MAC changes though).

[abrougui]

yes i can ping to google.com

C:\Users\resa>ping www.google.com

Envoi d’une requête 'ping' sur www.google.com [216.58.205.164] avec 32 octets de données :
Réponse de 216.58.205.164 : octets=32 temps=49 ms TTL=53
Réponse de 216.58.205.164 : octets=32 temps=48 ms TTL=53
Réponse de 216.58.205.164 : octets=32 temps=49 ms TTL=53
Réponse de 216.58.205.164 : octets=32 temps=48 ms TTL=53

Statistiques Ping pour 216.58.205.164:
    Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%),

C:\Users\resa>tracert -d www.google.com

Détermination de l’itinéraire vers www.google.com [216.58.205.164]
avec un maximum de 30 sauts :

1    2 ms    1 ms    1 ms  192.168.183.1
  2    2 ms    2 ms    2 ms  192.168.1.1
  3    4 ms    4 ms    4 ms  10.223.255.249
  4    6 ms    3 ms    3 ms  10.201.32.102
  5    *        *        *    Délai d’attente de la demande dépassé.
  6    *        *        *    Délai d’attente de la demande dépassé.
  7    50 ms    50 ms    50 ms  192.168.165.74
  8    49 ms    49 ms    49 ms  37.49.236.2
  9    55 ms    49 ms    51 ms  108.170.244.240
10    49 ms    49 ms    50 ms  72.14.238.63
11    49 ms    49 ms    49 ms  216.239.35.208
12    49 ms    49 ms    49 ms  216.239.47.112
13    *        *        *    Délai d’attente de la demande dépassé.
14    52 ms    49 ms    50 ms  216.239.42.23
15    48 ms    49 ms    49 ms  216.58.205.164

Itinéraire déterminé.

[abrougui]

i think that do some rules in the NAT?

[abrougui]

so any solution?

[johnpoz]

how is it your 8 hops into your trace before you hit public IP space?  And not seeing that 192.168.100 anywhere in that unless its hop 5 or 6?

Are you clients pointing to a proxy, what are your firewall rules?  Are you trying point traffic down a vpn?

Do tcptraceroute - how far does http/https traffic get with say destination of google?

traceroute to www.google.com (172.217.0.4), 30 hops max, 60 byte packets
1  192.168.9.253  0.388 ms  0.443 ms  0.560 ms
2  50.4.132.1  11.206 ms  11.211 ms  18.032 ms
3  76.73.171.73  22.360 ms  22.487 ms  23.364 ms
4  76.73.164.121  18.929 ms  19.992 ms  19.996 ms
5  76.73.164.109  19.782 ms  19.916 ms  19.757 ms
6  76.73.164.105  19.855 ms  20.525 ms  19.436 ms
7  76.73.164.65  20.069 ms  13.502 ms  14.110 ms
8  76.73.191.224  14.320 ms  19.632 ms  18.099 ms
9  76.73.191.226  16.836 ms 75.76.35.8  18.047 ms  18.075 ms
10  72.14.211.145  16.717 ms  18.107 ms  18.099 ms
11  108.170.243.193  17.205 ms *  15.873 ms
12  216.239.42.35  16.081 ms  14.040 ms 216.239.42.33  13.946 ms
13  172.217.0.4 <syn,ack>  17.232 ms  15.859 ms  21.930 ms</syn,ack>