Project

General

Profile

Actions

Regression #12183

open

Changing MAC address for PPP parent interface stopped working

Added by adeel altaf over 1 year ago. Updated 10 months ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Interfaces
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.5.2
Affected Architecture:

Description

mac address tab not showing in pppoe client interface i want to spoof my mac please tell me solution already showing in 2.5.1 but not showing in 2.5.2 screenshot attached please resolve thanks


Files

mac tab not showing.png (114 KB) mac tab not showing.png adeel altaf, 07/30/2021 07:37 PM
Actions #1

Updated by Jim Pingle over 1 year ago

  • Tracker changed from Bug to Regression
  • Subject changed from Mac spoofing problem to Changing MAC address for PPP parent interface stopped working
  • Priority changed from High to Low
  • Affected Architecture deleted (amd64)

That was changed in #11387 to prevent the field from being set on interfaces which don't have MAC addresses.

In your case, it probably was applying it to the parent, but that isn't always desirable as it could be ambiguous if there are multiple virtual types on the same parent with conflicting settings.

Might be better to assign the parent and enable it without adding any IP addresses, and change the MAC there. In the meantime we can reconsider hiding the field in cases like this were it does work, but it may need some more thought about preventing conflicts.

Changing the type to regression since this was working before but now stopped. And updating the subject and other fields.

Actions #2

Updated by Viktor Gurov about 1 year ago

Jim Pingle wrote in #note-1:

That was changed in #11387 to prevent the field from being set on interfaces which don't have MAC addresses.

In your case, it probably was applying it to the parent, but that isn't always desirable as it could be ambiguous if there are multiple virtual types on the same parent with conflicting settings.

Might be better to assign the parent and enable it without adding any IP addresses, and change the MAC there. In the meantime we can reconsider hiding the field in cases like this were it does work, but it may need some more thought about preventing conflicts.

Changing the type to regression since this was working before but now stopped. And updating the subject and other fields.

https://docs.netgate.com/pfsense/en/latest/interfaces/ppp.html#pppoe-point-to-point-protocol-over-ethernet should be updated to clarify this.

Actions #3

Updated by Jim Pingle about 1 year ago

That page doesn't mention spoofing the MAC now, and needing to spoof it with PPPoE is so rare I don't think that it's worth mentioning as it may lead more people to doing it unnecessarily.

Actions #4

Updated by Fernando Santos 10 months ago

Jim Pingle wrote in #note-3:

That page doesn't mention spoofing the MAC now, and needing to spoof it with PPPoE is so rare I don't think that it's worth mentioning as it may lead more people to doing it unnecessarily.

Jim, I understand that many interfaces don't need to change, but it's a very useful field because internet providers lock pppoe authentication with mac and are very resistant to changing the mac in the isp configuration and ends up making it too difficult, many still only allow it using the isp's own router, and this feature made these cases much easier and as well as having to replace the equipment or network card, ending up with no connection because of this lock on the mac address made by the internet providers.
It often happens on weekends, and sometimes it would be very helpful if this field were made available again in the case of pppoe connections.

Actions #5

Updated by Jim Pingle 10 months ago

Fernando Santos wrote in #note-4:

Jim Pingle wrote in #note-3:

That page doesn't mention spoofing the MAC now, and needing to spoof it with PPPoE is so rare I don't think that it's worth mentioning as it may lead more people to doing it unnecessarily.

Jim, I understand that many interfaces don't need to change, but it's a very useful field because internet providers lock pppoe authentication with mac and are very resistant to changing the mac in the isp configuration and ends up making it too difficult, many still only allow it using the isp's own router, and this feature made these cases much easier and as well as having to replace the equipment or network card, ending up with no connection because of this lock on the mac address made by the internet providers.
It often happens on weekends, and sometimes it would be very helpful if this field were made available again in the case of pppoe connections.

You can still do it, assign the parent and spoof it there. No need for anything special here or in the docs for that, it's already covered, just not this specific combination but it's really no different than other uses.

Actions #6

Updated by Fernando Santos 10 months ago

Jim Pingle wrote in #note-5:

Fernando Santos wrote in #note-4:

Jim Pingle wrote in #note-3:

That page doesn't mention spoofing the MAC now, and needing to spoof it with PPPoE is so rare I don't think that it's worth mentioning as it may lead more people to doing it unnecessarily.

Jim, I understand that many interfaces don't need to change, but it's a very useful field because internet providers lock pppoe authentication with mac and are very resistant to changing the mac in the isp configuration and ends up making it too difficult, many still only allow it using the isp's own router, and this feature made these cases much easier and as well as having to replace the equipment or network card, ending up with no connection because of this lock on the mac address made by the internet providers.
It often happens on weekends, and sometimes it would be very helpful if this field were made available again in the case of pppoe connections.

You can still do it, assign the parent and spoof it there. No need for anything special here or in the docs for that, it's already covered, just not this specific combination but it's really no different than other uses.

I tried to do this with the interface without the IP or as DHCP, but when it changes to pppoe it tries to authenticate with the original mac and not with the changed one.

Actions

Also available in: Atom PDF