pfSense cannot get WAN IP after reboot

PzrrL

@DaddyGo Great news I brought you (and to myself)! set WAN to 100baseTX full-duplex works! Thanks!!!! But what is the reason behind?

DaddyGo

What I wrote above is that the different ethernet controllers (chip) (one is the modem eth. port the other is the pfSense WAN port) can't match the link speed properly, since I have seen that when it works you are on 100base, so you should be forced the WAN port not to use the Auto-negotiation.

@PzrrL PzrrL
"And I thought people generally use DNS resolver on pfSense instead of 3rd parties"

with this I too have experimented a lot over the years and all my systems are built that way
so I can control everything and in the greatest security I think

You know (privacy is a myth):

@PzrrL
May I know where can I find this setting?

PzrrL

@DaddyGo said in pfSense cannot get WAN IP after reboot:

and this is necessary:

use the ARPWATCH package for tracking

Do you usually turn this on or off then?

PzrrL

@DaddyGo Really huge thanks to you, thank you!

DaddyGo

@PzrrL Do you usually turn this on or off then?
for a static entry always on

NinthWave

@daddygo I have the same problem but my pfSense is running in Proxmox. I have a 30 Mbs connexion and the only option I have in the interface config is 10baseT.

Any option ?

NinthWave

@ninthwave
Is there a way to use pastebin ?

https://imgur.com/i7GsbW0

Gertjan

@ninthwave said in pfSense cannot get WAN IP after reboot:

Is there a way to use pastebin ?

There is a way.

If this forum complains about the URL, do the 'smart' thing :

https: slash slash pastebin dot com/cMNrLnjC

NinthWave

@gertjan Thanks. I know how to use pastebin. My problem is I cant download the log with WinSCP.

PzrrL

@ninthwave said in pfSense cannot get WAN IP after reboot:

@gertjan Thanks. I know how to use pastebin. My problem is I cant download the log with WinSCP.

Can you guys starts another new thread? This is a year old already.