Not Getting Wan Address
-
I wasn't trying to do everything at once..... I just install pf and set the lan side to a static ip, and turned off its DHCP server so it wouldn't fight with the old router. Was going to turn on the DHCP server, try to transfer everything over once I confirmed that pf was seeing an outside connection.
So I'll try getting a wan ip from the old router real quick then.
And again thanks for the help so far.edit: Well that doesn't seem to be working, the wan interface is still show n/a on the main page.
-
Did you change the LAN IP so it doesn't conflict with the WAN when it pulls a lease from the old router?
It will normally still pull a lease in that scanario but it will break routing so you loose access to the webgui.
-
I might just be stupid, but all I saw pf doing was being assisted a dhcp ip (192.168.0.106) while connected to the old router. Feel free to tell me how much of an idiot I am, the more I mess around with this stuff the more I realize I really have no idea what I'm doing.....
-
If the pfSense WAN interface is being handed that as a lease by the old router that's probably working correctly. Assuming that's the correct subnet etc.
But if the pfSense LAN is also configured to use 192.168.0.X/24 that puts the same subnet on two interfaces which is invalid. And it's likely you did configure it like that if pfSense is intended to replace the old router. Whilst testing the WAN like that you would need to temporarily set the LAN to some other subnet like 192.168.100.X/24.
-
OH! Okay, that makes more sense to me. Unfortunately it will be a bit before I can try that now. I restarted the server while trying some things with a Home Assistant vm I have on there, and the whole thing became unreachable. So I'm just doing a total reinstall at this point.
-
After several hour and dinner, I figured out that I lost access to the server because the old router decided it was a great idea to give that ip to another device. Fun........ The new ip is now reserved to prevent that from happening again.
I did as you suggested and have pf on its own subnet now (192.168.100.X/24), and tried connecting to the old router again. It was again assigned an dhcp ip instead of getting the public ip from the modem. Connected it back to said modem again and it went back to getting nothing. -
Hmm, but 192.168.0.106 is actually a lease from the old router?
Did you reboot the modem between connecting the pfSense WAN to it? It may be locked to the MAC address of the old router.
-
Have you tried changing the MAC on the pfsense WAN interface so that it's the same as the ISP router you have which is getting a WAN IP (MAC cloning). Then try again with modem in bridge mode and see if that helps.
-
Holy shit........ My dyslexic brain...... I somehow managed to mix up the words router, with modem.....
So I just spoofed the old routers mac address, and it works now. Old router is removed and I"m watching a stream as I type this.
Sorry it took me so long to understand what you was saying. Am a dumb dumb. Thanks for all the help. I'll have a better idea one how to fix problems like this in the future now. -
@Malvazar Well, who cares, the important thing is that it works now!
