First time Pfsense install and I'm scratching my head!
-
Hi All,
I was hoping for a smooth install and to not be posting on here quite so quickly.
Although it must be noted I'm by no means tech proficient. An Unraid server build being the highlight of my technical prowess.
I'm wondering if anyone with a similar setup can help?
After months of becoming infuriated with my BT homehub, I decided to go for a pfsense install on an old Dell vostro intel core2duo I had laying around.
I picked up a Draytek Vigor 130 modem and connected to the pfsense build after install.
The modem is now in Bridge mode, but I'm getting no wan address at all.I can login in to the draytek web gui and it shows a positive connection.
Pfsense web gui has a green up sign on the connection but no wan ip.I'm not sure of how to set the PPOE details (might be wrong here) or even if I can manually add in wan details from previous router.
Any help with this pairing would be great.
I'm using the latest pfsense build and the wan nic is Intel EXPI9301CTBLK PRO1000.
-
You may need to set a VLAN, I can't recall if the V130 does that for you or not. Certainly using an Openreach modem you do not need to.
Is BT actually your ISP? If so you probably don't need any real credentials.
Go to Interfaces > WAN and set the connection type as PPPoE and enter the login, I use bthomehub@btbroadband.com/1234Steve
-
@stephenw10 Thanks, I'll give it a try tomorrow night.
-
So I’ve tried that and the wan connection goes from up to off.
BT is my isp.Any suggestions for next troubleshooting step?
-
Hello, Rory!
I'd certainly call them (your ISP) and ask what type of connection they use.
If it's really PPPOE, ask them for the credentials. It may be the same for all clients, or may be different for each one.
Good luck with it!
~Henrique
-
I can always give BT a call tomorrow, but based on this I think the pppoe details should be fine.
https://community.bt.com/t5/BT-Fibre-broadband/Configuration-of-third-party-router/td-p/1040540
-
Hmm.. If you have tried everything from that forum post, even VLAN setup, I don't really know what else you can try.
Have you tried copying all the WAN settings from the modem as you mentioned?
Also, something unlikely but possible, is that you may be mistyping the PPPoE username, because in this case, not only the password is case-sensitive, and I noticed that somewhere on that forum, the guy typed the first character of the username as upper case.. idk, who knows the problem is something that simple. ¯_(ツ)_/¯
Good luck,
~Henrique
-
I’ve not tried Vlan setup as I’ve read it’s not required.
Would an older version suit my hardware better do you think?
-
I'm sorry, older version of what? pfSense?
About the VLAN, I think it's worth trying.
It may work without it for some people, but who knows, maybe it depends on the region.
~Henrique
-
Can we maybe see some screenshots of your settings?
The credentials should be fine on BT. They know who you are by the actual line you're connecting on.
You do need to have VLAN 101 set somewhere. That might be in the modem, it does appear to have that option:
https://www.draytek.co.uk/support/guides/kb-vigor-130-vlantagIn fact it appears to be configured like that by default if you have a UK model.
That is how the BT modems are configured.
Steve
-
Once I'm home from work tonight I'll send over screenshots.
Are there particular screenshots that would be more useful for you to help me?
I'm guessing gui pages from modem and pfsense.
Would a screenshot of pfsense connected to monitor help?
-
Yes, check the modem setup for it's VLAN tag setting, or lack of one.
Then I would want to see the Interfaces > WAN page in pfSense.
Probably also the Interfaces > Assignments page and Interfaces > PPPs > Edit pppoe0
The PPP entry pppoe0 should be automatically generated when you switch the WAN type to PPPoE and on the correct parent interface.
Steve
-
Good morning, Rory!
Would a screenshot of pfsense connected to monitor help?
Unless there are any errors on the console, not really.
-
-
-
-
-
-
-
-
-
-
-
-
Ok, so your modem is setup wrong.
It looks to be configured in router mode, it's doing the PPP dialing itself, and it doesn't have the tagging set to 101 which it will need to.
Put it in bridge mode so it passes the connection to pfSense and set the tagging to 101 (if that doesn't happen automatically).This has a few options:
https://www.draytek.com/en/faq/faq-connectivity/connectivity.wan/how-to-use-pppoe-pass-through-and-bridge-mode-on-vigor130/But I don't see the PPPoE Pass-through checkbox on your screenshots.
I would disable the DHCP server on LAN. And disable the PPPoE client on WAN in the V130.If you need to access the modem from behind pfSense you cab assign the em0 interface separately and put it in the 1921.168.1.X subnet. If you add the V130 IP as a gateway pfSense will NAT to that and the clients on the pfSense LAN will be able to reach the modem.
https://www.netgate.com/docs/pfsense/interfaces/accessing-modem-from-inside-firewall.htmlSteve
-
Steve, Thanks for all your help.
I've made the adjustments you mentioned, but still no luck!There was one part I was particularly unsure of and that was setting the tagging to 101.
there is customer and service in vdsl2. I put 101 in both.Although the screenshots took me about half an hour to upload due to my new user rating, would you mind taking another look if i post them tomorrow night?
-
Sure.
This should be pretty easy. I used to use a Draytek V120 back on ADSL and pass-through was it's default mode.
I wasn't sure what the difference between 'customer' and 'service' was either but that guide seems to indicate it should be on the customer side.Steve
-
Is your Vigor 130 the UK model?
If it is, it comes automatically configured for UK VDSL (BT Infinity), including the correct setting of VLAN 101 for VDSL and it should need no changes to this.
The latest BT VDSL modem code is 576D17 - you don't seem to be running this. You can always download the latest BT firmware (currently 3.8.3 BT) from https://www.draytek.co.uk/support/downloads/vigor-130
As explained in the accompanying notes, if you use the .RST file then the Vigor 130 will be reset to defaults and should need no other setting for BT.
If your Vigor 130 was sourced outside the UK/Ireland then this may not work, as I believe the non-UK/Ireland model is different (a full router versus an ADSL/VDSL modem).
-
Guys. I’ve got there!
Took 3 attempts this evening!Thanks for all your help!
-
Nice!
Was there a single settings that fixed it? It looks like the default settings in that new firmware would probably have done it.Always good to note what the fix was for future readers.
Steve
-
The bt firmware for DrayTek definitely helped.
Outside what you had advised Steve the only change I had to make in the modem was to change the MTU from 1520 to 1492.I knew I was close and got success when I turned ipv6 to none in wan settings in pf.
Thanks again!
-
Thanks also Bigsy for the firmware link
-
@rory4881 Glad it's working.
If you reset the modem with the default configuration file the modem is in bridge mode and you should not have to adjust the MTU on it - this is done via the PPPoE settings in pfSense.
-
Thanks Bigsy.
It reset to MTU number 1520. Plus pf only allows to 1500.1492 on both and all good
-
@rory4881 Do your ISP and pfSense hardware support an MTU of 1500 on PPPoE (RFC 4638)? Both BT Infinity and the Vigor 130 support this and it's what I use on my connection to Zen Internet.
Again, if the modem is in its default bridged state, whatever the modem config web page is displaying as MTU is irrelevant, as pfSense controls this via the WAN/PPPoE interface.
-
Mmm, there was a report that was broken in 2.4.X but I was unable to test at the time. It did seem to break IPv6 though.
Does Zen give you v6?Steve
-
@stephenw10 Yes Steve, Zen uses IPv6.
I'm running 2.4.4 here and have had no problems. The WAN ethernet is Intel i211 (igb driver).
[2.4.4-RELEASE][admin@x]/root: ping6 -D -s 1452 -c 4 pfsense.org PING6(1500=40+8+1452 bytes) 2a02:x:x:x:x:x:x:x --> 2610:160:11:11::69 1460 bytes from 2610:160:11:11::69, icmp_seq=0 hlim=250 time=123.880 ms 1460 bytes from 2610:160:11:11::69, icmp_seq=1 hlim=250 time=123.528 ms 1460 bytes from 2610:160:11:11::69, icmp_seq=2 hlim=250 time=123.517 ms 1460 bytes from 2610:160:11:11::69, icmp_seq=3 hlim=250 time=132.205 ms --- pfsense.org ping6 statistics --- 4 packets transmitted, 4 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 123.517/125.782/132.205/3.711 ms
