Mpd-4.2 released.

[Nikolay Pavlov]

On Tuesday, 26 June 2007 at 18:31:30 -0700, Julian Elischer wrote:
> Nikolay Pavlov wrote:
> >On Wednesday, 27 June 2007 at  2:25:22 +0300, Alexander Motin wrote:
> >>Nikolay Pavlov wrote:
> >>>This is probably a new feature request, but is this possible to create
> >>>some kind of VirtualTemplate interface like it is in Cisco access
> >>>routers. Currently i have to configure bunch of different ng interfaces
> >>>for every kind user. However on my Cisco 7206VXR i can bundle physical
> >>>link together with VirtaulTemplate interface in one vpdn-group config
> >>>like this:
> >>>And all the ppp interfaces for all users will use this configuration
> >>>as a template.
> >>Yes, I am thinking about that. That is not trivial change. It will require changing all internal model from static to the dynamic one. But that change also should give many 
> >>other bonuses so I would like to try.
> >>
> >>One of problems is more or less new config file syntax required. I have very limited cisco experience, so it is difficult for me to adopt their model to mpd, but I would not 
> >>like to reinvent a wheel. I will be grateful for any ideas/examples of how do you see that.
> >>
> >>
> 
> I am not sure that people know how to use the 'include' syntax in mpd.
> 
> i have not used it for a long time but I do remember that my setups were very simple,
> because I used a kind of template entry to hold all teh common stuff.
> 
> ah here it is.. in this example I use 'load' to save lots of typing..
> 
> 
> 
> tun_standard:
>        set link yes acfcomp protocomp
>        set link no pap
>        set link no chap
>        set link keep-alive 2 15
>        set link mru 900
>        set link mtu 900
> #       set link bandwidth 1440000
> ############### per-link settings #################
> vpn-site1:
>        new -i ng0 vpn-site1 site1-ISP1 site1-ISP2
>        set iface addrs 10.12.1.24 10.12.1.10
>        set iface route 192.168.10.0/24
>        set ipcp ranges 10.12.1.24/32 10.12.1.10/32
>        load vpn_standard
>        link site1-ISP1        load tun_standard
>        link site1-ISP2
>        load tun_standard
>        open
> vpn-site2:
>        new -i ng1 vpn-site2 site2-ISP1 site2-ISP2
>        set iface addrs 10.12.1.24 10.12.1.20
>        set iface route 192.168.20.0/24
>        set ipcp ranges 10.12.1.24/32 10.12.1.20/32
>        load vpn_standard
>        link site2-ISP1        load tun_standard
>        link site2-ISP2
>        load tun_standard
>        open

But what if you want to support one thousand of concurrent connections?


-- 
======================================================================  
- Best regards, Nikolay Pavlov. <<<-----------------------------------    
======================================================================