Not Getting Wan Address
-
I couldn't use some guidance here. I have pf installed as a vm on proxmox, with an intell 2.5g nic passed through. Install went fine, nic was detected and configured, and it booted up fine. For what ever reason however I'm not getting a wan ip from my xfinity modem (which is set to bridge mode). I've tried rebooting both pf and the modem with no luck, and tried just setting the information manually but didn't gain internet access. I'm still fairly new to this level of routing/networking stuff, mainly just used an off the shelf wifi router till now. So please if you need some kinda info to help just tell me and I'll do my best to get it.
Also sorry about posting about this issue. I know there are other post about this, but none of them were really helping me. -
S stephenw10 moved this topic from Problems Installing or Upgrading pfSense Software on
-
It looks like you're trying to do a number of things at the same time.
I would first try either pulling a lease from the modem directly using a laptop. Or try pulling a dhcp lease from something else on the pfSense WAN like an existing router.
You might also try using a WAN side Linux bridge in Porxmox instead of passing through the NIC if it can't pull a lease at all.
Steve
-
Thanks for responding, I actually did try setting the wan ip to static and set the ip the I pulled from the modem, but as far as I could tell there still wasn't a connection made. Pf wasn't able to check of updated at least, so I figured that meant it didn't work.
Also I do currently still have my old tplink router connected, and using it to keep the houses devices up (other wise my house mates would eat me alive without internet x.x). So I at least know its not the modem being a problem (as far as i can tell).
Random thought. Would connecting the wan of pf to the old router instead of the modem help at all. I'm assuming it wouldn't, but I'm up for trying anything at this point. -
Ok so you have proven the modem is working as expected in bridge mode if the old router can pull a lease from it correctly?
@Malvazar said in Not Getting Wan Address:
Would connecting the wan of pf to the old router instead of the modem help at all.
Yes, that was one of my suggestions. If the pfSense is set to DHCP it should be able to pull a lease from the old router if the NIC passthrough is configured correctly.
However be aware that if you have configured pfSense to replace the old router it will likely have the same subnet on it's WAN and LAN and that will break routing.Basically it looks like you've tried to do everything at once so now when it doesn't work as expected it's hard to say what failed. You need to do things one step at a time, verifying as you go.
Steve
-
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!
