ppp/peers/* files

[Jim Stapleton]

What man/handbook pages/sections should I look at to get a clue. I'm
so far from having one, I don't even know the direction...

Thanks,
-Jim Stapleton

On 6/26/07, Artyom Viklenko <artem at aws-net.org.ua> wrote:
> Jim Stapleton wrote:
> > That partially worked. I could only ping 192.168.1.1 on my local setup
> > (router).
> >
> > I used
> > $ mpd pptp0
> >
> > However, I couldn't access the work DNS either. The latter output of
> > MPD looked like:
> > ==========
> > pptp0] IPCP: rec'd Configure Ack #4 link 0 (Ack-Sent)
> > IPADDR <IP-ADDR-A>
> > [pptp0] IPCP: state change Ack-Sent --> Opened
> > [pptp0] IPCP: LayerUp
> >  <IP-ADDR-A> -> <IP-ADDR-B>
> > [pptp0] IFACE: Up event
> > [pptp0] setting interface ng0 MTU to 1396 bytes
> > [pptp0] exec: /sbin/ifconfig ng0 <IP-ADDR-A> <IP-ADDR-B> netmask
> > 0xffffffff -link0
> > [pptp0] exec: /sbin/route add <IP-ADDR-A> -iface lo0
> > [pptp0] exec: /sbin/route add 0.0.0.0 <IP-ADDR-B>
> > [pptp0] exec: command returned 256
> > ==========
> >
> >
> > I could ping <IP-ADDR-A> and <IP-ADDR-B> after running mpd, but I
> > could not ping them before running it, or after shutting it down. Both
> > are valid IP addresses on my works internal network.
> >
> > Aside from my nve0 and l0 devices, which look normal, ifconfig
> > displays the following:
> >
> > ==========
> > ng0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> mtu 1396
> >        inet <IP-ADDR-A> --> <IP-ADDR-B> netmask 0xffffffff
> > ==========
> >
> > I could not ping the DNS servers.
> >
> > Any suggestions?
>
> I think you need static route to your VPN server.
> After setting up tullel your default route changes.
> This can lead to incorrect routing.
>
>
> --
>              Sincerely yours,
>                               Artyom Viklenko.
> -------------------------------------------------------
> artem at aws-net.org.ua | http://www.aws-net.org.ua/~artem
> FreeBSD: The Power to Serve   -  http://www.freebsd.org
>