Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Chrysalis]

On AAISP network over a cable connection.

Code: [Select]

Tracing route to bbc.co.uk [151.101.0.81]
over a maximum of 30 hops:

  1    17 ms    17 ms    19 ms  l2tp.thn.aa.net.uk [90.155.53.19]
  2    17 ms    19 ms    19 ms  k-aimless.thn.aa.net.uk [90.155.53.101]
  3    17 ms    18 ms    18 ms  195.66.225.91
  4    19 ms    18 ms    18 ms  151.101.0.81

Trace complete.
Using windows L2TP client at the moment as pfsense is freaking out, I activate the tunnel and VM goes down alongside AAISP not coming up, but on windows it worked as expected.

[Alex Atkin UK]

That's odd, works fine here.  The only problem I've had is if it goes down (as I'm using it over 5G) it sometimes fails to come back up.

[Chrysalis]

Well this is what I did please let me know if this is wrong.

https://support.aa.net.uk/L2TP_Client:_pfSense

Followed the above guide, so new PPP, L2TP type, selected igb3 which for me is my VM interface, entered my auth details, and the aaisp L2TP IP.

I then went in the interface after to configure IPv6 as SLAAC as the above guide says and enabled it.

VM then went to 100% packet loss, errors to VM gateway, AAISP L2TP gateway stayed on pending, logs showed no responses to L2TP packets.  Could only get back online by disabling the L2TP service, and cycling the VM DHCP.

However on windows it just came up as expected, its capped to 100mbit, so I am guessing the L2TP on broadband accounts doesnt have the new 200mbit cap.

My theory is that I am linking it to a physical interface, and maybe when it works its on a virtual PPPoE interface, but I am using IPoE.

[Alex Atkin UK]

Okay, here is what I have.

Worth noting, I had to set System, Routing, AAISP_SLAAC (the IPv6 one) to Disable Gateway Monitoring as the AAISP gateway did not respond to pings and while the documentation says "it should work anyway" I found it did not.  This does not however impact IPv4.

[Chrysalis]

Looks almost the same, you ticked the ipv4 parent box as the only difference, after I ordered my food shopping I will give it another go.

[Chrysalis]

Its a no go, I tested it over EE (ue0) and it works fine like it does on your mobile network, but as soon as I try the VM interface it kills VM.

The error that appears for the VM connectivity is "arpresolve: can't allocate llinfo" and igb3 flips between active and no carrier state until I intervene by killing the L2TP.

[Chrysalis]

Is working now Alex, seems spoofing mac on the host interface breaks l2tp on pfsense.

Also IPv6 works however the monitoring if you dont specify a monitor ip reports 100% loss (aaisp gateway doesnt respond to pings) and if selecting a manual ip to ping although it pings manually the SLAAC gateway gets stuck in a pending state which I am guessing is a pfsense bug, so I force it to the online state so it gets used and then everything works.

[Alex Atkin UK]

Is working now Alex, seems spoofing mac on the host interface breaks l2tp on pfsense.

Also IPv6 works however the monitoring if you dont specify a monitor ip reports 100% loss (aaisp gateway doesnt respond to pings) and if selecting a manual ip to ping although it pings manually the SLAAC gateway gets stuck in a pending state which I am guessing is a pfsense bug, so I force it to the online state so it gets used and then everything works.

The gateway monitoring issue isn't limited to AAISP, it happens on Zen too for me, stuck in pending right now even though I have confirmed manually the IP I have in monitoring is responding fine.

This is one of the reasons I just don't care about IPv6, its just not as reliable as IPv4, at least on pfSense using L2TP/PPP as the carrier layer.  When I had the HE.NET GRE tunnel configured, that always seemed to work.

More interestingly I seem to have lost IPv6 routing over AAISP completely at the moment.  If I try to force AAISP as the src IP, it just goes over Zen anyway. 

[bogof]

Out of interest, what are the use cases whereby you find it useful to have something like this L2TP service setup?

[Chrysalis]

The gateway monitoring issue isn't limited to AAISP, it happens on Zen too for me, stuck in pending right now even though I have confirmed manually the IP I have in monitoring is responding fine.

This is one of the reasons I just don't care about IPv6, its just not as reliable as IPv4, at least on pfSense using L2TP/PPP as the carrier layer.  When I had the HE.NET GRE tunnel configured, that always seemed to work.

More interestingly I seem to have lost IPv6 routing over AAISP completely at the moment.  If I try to force AAISP as the src IP, it just goes over Zen anyway. 

Yep its a pfsense bug.

Go to system menu -> routing, select the gateway, click edit, and tick the option "disable gateway monitoring (assume its online)".

It will go to online state and work normally.

[Chrysalis]

Out of interest, what are the use cases whereby you find it useful to have something like this L2TP service setup?

For me I have certain uses, and also use cases where I need static IP addressing, and also have use cases for IPv6 as well which VM has no IPv6 support at all.

[bogof]

For me I have certain uses, and also use cases where I need static IP addressing, and also have use cases for IPv6 as well which VM has no IPv6 support at all.

Interesting.  I am intrigued by it.  Especially as I see that for £10/per month domestic it comes with 2TB traffic.  I have 10TB at the moment on FTTP don't fully need, but 1TB isn't enough, so I pay the extra £10.  If the 2TB /month that comes with the L2TP service goes into the pot, I could have 3TB / month Inc the L2TP service, which would be more than enough data and offer the  extra functionality. 

Edit: actually I don't think broadband and L2TP can share quotas.  Oh well.

[Chrysalis]

Its built in if you have a broadband account and I assume shares the quota.  Thats how I am using it now.  But of course can buy it as standalone also.

https://support.aa.net.uk/Category:Incoming_L2TP

[bogof]

Its built in if you have a broadband account and I assume shares the quota.  Thats how I am using it now.  But of course can buy it as standalone also.

https://support.aa.net.uk/Category:Incoming_L2TP

Ah, gotcha!   So is there a good configuration of a particular router that will only bring up the L2TP over eg: cellular if the main connection goes down?

[Weaver]

Firebrick can do just that. Using ‘profiles’.