On Sat, 1 Mar 2014 18:23:08 -0800 "Paul B. Henson" <hen...@acm.org> wrote: > On Sat, Mar 01, 2014 at 01:48:06PM +0900, YASUOKA Masahiko wrote: >> > on the other side? Right now it looks like the client is setting a >> > route to 10.0.0.0/8 across the tunnel, that should actually be >> > 10.128.0.0/16, would setting the netmask in npppd-users fix that remote >> > route? Can I set the netmask but still let the client get a dynamic IP? >> >> My answer was wrong. Assigning statically or netmask to the client is >> not related the ospf problem, I'm sorry. > > No worries, I appreciate the help :). I tried setting the netmask in > npppd-users, that didn't change the /8 route the iPhone client set. From > a little investigation, it doesn't look like there's any way to set the > client netmask for the l2tp vpn route? The client just does whatever it > wants it seems, whether to just assume a class based route (/8 in the > case of my 10.128 address) or some seem to just assume a /24 8-/. You'd > think defining the client netmask would be part of the protocol, but > unless I'm missing something, I guess it's not.
"framed-ip-netmask" in npppd-user to set the netmask of the route to the PPP link. But it is not to set the client netmask (on iPhone). AFAIK to set the client netmask, DHCP inform can be used. Also I found some bugs around "framed-ip-netmask". I will fix them soon. --yasuoka
