Thanks Terry. And thanks for sharing this, I have no doubt that it will prove useful in the future. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Terry Sweetser (SkyMesh) Sent: Tuesday, 6 September 2016 2:02 PM To: public@talk.mikrotik.com.au Subject: Re: [MT-AU Public] The NBN Questions again ... Hi Phillip, That looks like a good config -- my only difference is I use radius, and the auth is based on option 82. --- http://about.me/terry.sweetser On 06/09/16 13:59, Philip Loenneker wrote:
Hi Terry,
I think I understand now - you put the 180.181.80.1/32 IP on every AVC interface with the customer IP as the network address, and the DHCP server on each one has a pool with a single IP address but shares the Network object. Something like this:
[common to all AVCs] /ip dhcp-server network add address=180.181.80.0/20 gateway=180.181.80.1 netmask=20 ntp-server=180.181.127.1
[example AVC] /interface vlan add interface=NBN-NNI-CVC name=AVC27 vlan-id=27 arp=proxy-arp /ip address interface=AVC27 address=180.181.80.1/32 network=180.181.81.27 /ip pool add name=POOL-AVC27 ranges=180.181.81.27 /ip dhcp-server add address-pool=POOL-ACV27 disabled=no interface=AVC27 lease-time=30m name=DHCP-AVC27 add-arp=yes
Do I understand correctly?
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Terry Sweetser (SkyMesh) Sent: Tuesday, 6 September 2016 1:19 PM To: public@talk.mikrotik.com.au Subject: Re: [MT-AU Public] The NBN Questions again ...
Hi Phillip,
[terry@CCR2.NSW] /ip dhcp-server network> export # sep/06/2016 13:03:15 by RouterOS 6.36.2 # software id = CG4T-VJTQ # /ip dhcp-server network add address=180.181.80.0/20 gateway=180.181.80.1 netmask=20 ntp-server=180.181.127.1 [terry@CCR2.NSW] /ip dhcp-server network> As above, the netmask stays nice and short, 4000 ip addresses per NBN CVC.
"proxy-arp" will happily handle the issue of getting from AVC to AVC.
A '/32' on an ethernet port for the WAN ip address is very much a dead end on all CPE I have tested.
Also, of note, the ipv6 set up and M/C load from this deployment has also been far leaner. (ipv6 is trivial, add address to sub-interface with advertise=yes, add DHCPv6 with a Pool set up just for the sub-interface, voila: static ipv6 addresses and PD.)
--- http://about.me/terry.sweetser
On 06/09/16 12:33, Philip Loenneker wrote:
Hi Terry,
That's fantastic - I love seeing this kind of creative solution.
Just to clarify - are you copying the PPPoE IP addressing method by assigning a /32 to the CPE and specifying the network address as the gateway? So you would have a separate IP pool and DHCP server running on each interface.
I'd be very interested to see a more complete snip of the config if you are willing to share.
Does this seem to work on all CPEs, or do you only work with particular brands? I vaguely remember trying something like this a while back, but only Mikrotik CPEs seemed happy with it.
Regards, Philip
Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au