in 2116/2216 you will no have another option than running v7do you think it makes a difference whether I'm running V6 or V7 on the devices?
That is not true.in 2116/2216 you will no have another option than running v7do you think it makes a difference whether I'm running V6 or V7 on the devices?
if you are asking about performance improvements, you will not have any performance improvement moving your 1072/1036 to v7
to date the only relevant motivation to move a production router from v6 to v7 is the need to take advantage of some new feature only available on v7
I would dump PPPoE, but my radius/billing software is limited on other ways to AAA dhe dhcp clients.Or move to DHCP and dump PPPoE. PPPoE has MTU and CPU overhead due to encapsulation, DHCP does not have any such issues.
if your access network is open (ethernet switches ) you will need to stick with PPPoE for authCan you suggest what king of authentication would be used along with DHCP?
DHCP options of your choice based on your needs, DHCP client ID, DHCP+RADIUSCan you suggest what king of authentication would be used along with DHCP?
Why? Perform MAC binding and use various DHCP options that you need or want and client ID.if your access network is open (ethernet switches ) you will need to stick with PPPoE for auth
Sure. You're arguing against DHCP. But since we agree both PPPoE/DHCP can't be stopped with the right skillset, why use PPPoE and lose MTU overhead/CPU overhead?then PPPoE does not solve the situation neither because with the right skillset. That doesn't stop anything.
Hi i know its an old thread.. but called my attention on your post.. could you elaborate a litle bit more on that?Or move to DHCP and dump PPPoE. PPPoE has MTU and CPU overhead due to encapsulation, DHCP does not have any such issues.
Same problem here..stuck on radius because of that.I would dump PPPoE, but my radius/billing software is limited on other ways to AAA dhe dhcp clients.Or move to DHCP and dump PPPoE. PPPoE has MTU and CPU overhead due to encapsulation, DHCP does not have any such issues.
Same problem here..stuck on radius because of that.
I would dump PPPoE, but my radius/billing software is limited on other ways to AAA dhe dhcp clients.
@PortalNET
PPPoE is an encapsulation protocol, it made sense in the era of hubs and massive L2 domains back in 1998 with DSL era.
Now we are living in PON world with QinQ/VLAN support. There's no reason to use PPPoE except to stick to an outdated protocol just as many do with IPv4 instead of IPv6.
Anyone defending PPPoE is plain stupid or too old and should retire while they can.
You can migrate to DHCP and talk with your AAA vendor, example:
https://docs.splynx.com/networking/auth ... hcp_radius
DHCPv4 + DHCPv6 can work together by enabling dual stack queues option and use radius option.
There seems to be an obsession with PPPoE in some countries, even in multiple gigabits FTTH days.Anyone defending PPPoE is plain stupid or too old and should retire while they can.