pfSense won't get IP from Frontier Fiber.
-
@stephenw10
The snippet I posted was from 13.1 man page where it's applied to all interfaces. If you look at the 12.3 man page it's only applied to vlans. It's actually called vlanpcp or something like that. -
@bogusexception I don't use their router (no modem needed with fiber) anymore. This install wasn't mine though and they don't even provide a router anymore. Actually they provide an Eero 6 Pro but it's not much of a router and I would never use it as one.
But before learning this (yesterday) I did still use their router (Arris NVGsomething) and it worked fine. Their newer, not sure when, firmware added a 'transparent bridge' mode which was more of a true bridge than the more common DHCP reservation suedo-bridge instructions you find all over the internet. If you're using one of their arris routers go to advanced/connection and you'll find the bridge mode there. My biggest thing was I didn't want another device plugged in so I changed my install to the switch in between yesterday and it's working perfectly. -
@stephenw10 I actually do have a "lab" box I have pfSense+ on. If I get time tomorrow maybe I'll give that a shot!
-
Mmm, it might 'just work'. pfSense is built on 12-stable. So whilst it still shows as 12.3 it's actually newer.
Though it looks like that code has actually been in ifconfig for some years:
https://github.com/pfsense/FreeBSD-src/commit/9de215608cfe3e871e92c6d6444063dd8be2b5c9
And it specifically mentions only tagging outbound traffic and that incoming traffic may be filtered by the driver.Steve
-
@stephenw10
Just tried with no luck.
Can't find too much info on pcp though so I may not be implementing properly.
All I did was "ifconfig em0 -pcp 0"
It did show as applied but made no difference.
Is that all that's needed? -
I would try
ifconfig em0 pcp 0which should enable tagging. However after reading I don't think it does anything for the replies which are the problem here.Steve
-
How is this going? Frontier is running fiber here soon. I would love to dump Charter (Spectrum).
-
You will still require a switch to strip the tags if they are sending vlan0 tagged traffic.
Steve
-
My concern is not getting it to work if we take the plunge and losing money. Probably can get it to work, but I cannot get any answers from Frontier about what their network does here. No surprise, these companies treat people like cattle anyway. If you read their website about the eero, they are all like you have to use it blah blah blah. The fine print says you have to sign with Amazon account too (lol, what??).
Anyway, I found so many posts out there regarding this. This one was most interesting. One person says a linux router distro works out of the box (did not say which). Another said Proxmox worked. My pfsense is on Hyper-V, so hopefully Hyper-V will handle it if it is there (back up is on the Netgate appliance though). Otherwise, I will be finagling two of my SFP+ 10 Gb ports for their own little VLAN.
What is it with these telecomm companies pushing half-brained services? Regulation is a joke lol.
-
Hmm, not sure if I've seen Hyper-V used with vlan0 tags. There's a pretty good chance that would strip the tags in the vswitch though.
-
I have a couple of Frontier installs going through a managed switch and they work fine. Yours will too.
You won't be using the sfp+ ports though, all copper since you'll have to use their ONT. -
Good to have options. These are combo SFP+ ports supporting 10 Gbe. My pfsense box uses one already using a copper module. Although I bet Hyper-V will handle it as is.
The waiting game now... Have to wait for construction in the neighborhood first.
-
Just had Frontier 1gbps service installed with the new black ONT. Engineer connected it to my pfSense 2.5.2 routers WAN port replacing my Spectrum S33 modem and it picked up a public WAN address without hiccup or any VLAN0 messing.
-
Anyone figure out how enable the PfSense box to get an IP address on the WAN port for Frontier Fiber?
I also have a White Frontier ONT and an Arris NVG468MQ router they provided. My Pfsense box has never been able to grab a WAN IP address unless the Arris router is in front of it. If I plug my Mac or other PCs directly to the ONT they can obtain a WAN IP without a problem without the Arris router.
I just recently upgraded to the 2GB service but the tech wasn't trained or didn't know that you needed new hardware so I'm still waiting for the new hardware that supports 2GB connections; however, I have a new PfSense box from Protecli that supports 2.5GB connections and a Zyxel 2.5GB unmanaged switch, so I thought I would again try to plug the ONT directly into the PfSense box but it still won't grab an IP address on the WAN port.
-
@scottv
You have a few options.
Search the forum for vlan0.There's a script you can use, you can put a switch in between the ONT and pfSense or you can put their router in bridge mode depending on which they give you.
-
@jarhead said in pfSense won't get IP from Frontier Fiber.:
There's a script you can use
Should be noted here the script is technically side-loading and if you have a TAC support subscription that can possibly result in not receiving support. Not an absolute but an advisory.
-
@rcoleman-netgate Can he have a TAC subscription with a Protectli? Thought that was just for Netgate equipment.
-
@jarhead TAC support is available on any system that runs a current version of pfSense (CE or Plus) and can be purchased at any time at https://shop.netgate.com/collections/support
-
@rcoleman-netgate Good to know. Thanks.
-
@jarhead
Thanks for the options; however, I found an easier 3rd option which is switching to OPNsense. I am up and running on my own equipment without Frontier's router in Bridge mode and only spent a couple hours work to install and configure to my needs. Now I am running at 2000Mbps and don't even need to wait for Frontier's new equipment and tech to show up. I am sure they will want to install it whenever it gets in and I will just remove it after they leave...Will re-consider pfSense once it's fixed but my needs are pretty simple and it's just as easy for me to switch to a different solution.
