<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-1x.git/interface-definitions/include/accel-ppp/client-ip-pool-subnet.xml.i, branch 1.4.0-rc2</title>
<subtitle>VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-1x.git/atom?h=1.4.0-rc2</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-1x.git/atom?h=1.4.0-rc2'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/'/>
<updated>2023-12-28T15:28:02+00:00</updated>
<entry>
<title>accel-ppp: T5688: Standardized pool configuration in accel-ppp</title>
<updated>2023-12-28T15:28:02+00:00</updated>
<author>
<name>aapostoliuk</name>
<email>a.apostoliuk@vyos.io</email>
</author>
<published>2023-11-13T09:17:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=d5062cb045fae8b0b5d68b3b1198c3b86de4d558'/>
<id>urn:sha1:d5062cb045fae8b0b5d68b3b1198c3b86de4d558</id>
<content type='text'>
Standardized pool configuration for all accel-ppp services.
1. Only named pools are used now.
2. Allows all services to use range in x.x.x.x/mask
   and x.x.x.x-x.x.x.y format
3. next-pool can be used in all services
2. Allows to use in ipoe gw-ip-address without pool configuration
   which allows to use Fraimed-IP-Address attribute by radius.
3. Default pool name should be explicidly configured
   with default-pool.
4. In ipoe netmask and range subnet can be different.

(cherry picked from commit 422eb463d413da812eabc28706e507a9910d7b53)
</content>
</entry>
<entry>
<title>xml: accel-ppp: move building blocks to subfolder</title>
<updated>2021-03-14T15:56:11+00:00</updated>
<author>
<name>Christian Poessinger</name>
<email>christian@poessinger.com</email>
</author>
<published>2021-03-14T15:44:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=e7edd9229dd6b870f892e419ffc671d4873a5540'/>
<id>urn:sha1:e7edd9229dd6b870f892e419ffc671d4873a5540</id>
<content type='text'>
As the amount of include files now has reached a certain amount, it is getting
more and more crowsded, thuse introducing "per topic" subdirectories on the
filesystem to keep a clean structure makes sense.
</content>
</entry>
</feed>
