First time Pfsense install and I'm scratching my head!
-
-
-
-
-
-
-
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
