OpenBSD , PopTop and NAT

From: Andrew A. Ozol (andy_at_rocc.ru)
Date: 10/28/03


Date: 28 Oct 2003 11:34:10 -0800

Regards of associate.I assembled PopTop 1.1.3 under OpenBSD 3.0 from
source with /configure - with-bsdppp - with-pppd-ip-alloc .It like as
it works, but noted one unpleasant special feature when usual users
from the different addresses they are connected up - all by beam.But
here when users are connected through NAT and have one and the same
address - is connected up only first.Rest as a rule be connected
cannot. As rule - sometimes nevertheless does succeed in .And if user
connect throw NAT with different address - it connect fine.
How resolve this situation ?
It is said subj works under FreeBSD normally in this plan/layout .

Configs
/etc/ppp/ppp.conf
loop:
     set timeout 0
     set log phase
# set log phase chat connect lcp ipcp tun command LQM
     set device localhost:pptp
     set dial
     set login
# set mppe * stateful
     # Server (local) IP address, Range for Clients, and Netmask
     # Use the same IP addresses you specified in /etc/pppd.conf :
     set ifaddr 10.0.9.2 10.0.11.10-20 255.255.255.0
     set server /tmp/loop "" 0177
loop-in:
    set timeout 0
    set log phase lcp ipcp command
    allow mode direct
pptp:
    load loop
# enable pap
# enable chap
    disable ipv6cp
    enable mschapv2
# disable deflate pred1
# accept mppe
# set mppe * *
# enable proxy
# accept dns
    # DNS Servers to assign client
    # Use your own DNS server IP address :
    # NetBIOS/WINS Servers to assign client
    # Use your own WINS server IP address :
# set nbns 10.0.0.4
    set device !/etc/ppp/secure
????????? ? ??????
pptpd[28808]: GRE: read(fd=6,buffer=6548,len=8196) from PTTY failed:
status = 0 error = No error
pptpd[28808]: CTRL: PTY read or GRE write failed (pty,gre)=(6,5)

--


Relevant Pages

  • Re: nslookup question?
    ... > If nslookup is unsuccesful, FOR EXAMPLE, showing the ... > how can I force a client to see the Primary DNS as ... > Give me constant errors that RPC server is unavailable. ... for service locations on domain controllers, not for DNS servers. ...
    (microsoft.public.windows.server.dns)
  • Request for help with proper DNS and default gateway settings in a small LAN
    ... I run a small test network behind a hardware firewall ... I recently replaced my 'server' ... WAN port is a DHCP client as required by my ISP but the TCP/IP settings ... DG 192.168.1.2 DNS same as above (ISP's DNS servers) ...
    (microsoft.public.windowsxp.network_web)
  • Re: DNS Question
    ... I could not get a timeout using ... > they point to the correct ISP DNS servers. ... > server in my client setup, which as I said in my first post solves the ...
    (microsoft.public.windows.server.sbs)
  • Re: Resolution fails, running nslookup causes it to succeed
    ... and the server has eventually received the answer and is ... Resolution still failed after clearing the client cache and hitting retry. ... Browsing to download.nai.com fails due to our internal DNS servers not ... Then if we run nslookup against our DNS ...
    (microsoft.public.win2000.dns)
  • Re: Resolution fails, running nslookup causes it to succeed
    ... and the server has eventually received the answer and is ... Resolution still failed after clearing the client cache and hitting retry. ... Then if we run nslookup against our DNS ... Likely irrelevant except that it may reflect flaky DNS servers on there ...
    (microsoft.public.win2000.dns)