<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<title type="html"><![CDATA[Linux Forum &mdash; Домашний роутер через городскую сетку и VPN в интернет]]></title>
	<link rel="self" href="https://linuxforum.ru/extern.php?action=feed&amp;tid=22591&amp;type=atom" />
	<updated>2012-06-28T08:15:16Z</updated>
	<generator>PunBB</generator>
	<id>https://linuxforum.ru/viewtopic.php?id=22591</id>
		<entry>
			<title type="html"><![CDATA[Re: Домашний роутер через городскую сетку и VPN в интернет]]></title>
			<link rel="alternate" href="https://linuxforum.ru/viewtopic.php?pid=284653#p284653" />
			<content type="html"><![CDATA[<div class="quotebox"><cite>Ovoshlook пишет:</cite><blockquote><p>Если еще актуально то вот:<br /><a href="http://wiki.debian.org/ru/pptp-linux">http://wiki.debian.org/ru/pptp-linux</a><br />Тут все очень хорошо описано.</p></blockquote></div><p>Спасибо... был я там. <img src="https://linuxforum.ru/img/smilies/bx.gif" alt="bx" /><br />С подключением через VPN я уже разобрался.<br />Были и мои ошибки в конфигах, но и провайдер был не точен.<br />Я пытался аутенфицироваться по самому &quot;крутому&quot; протоколу, MS-CHAP-v2. Оный был объявлен в описалове настроек провайдера, но реально не работал. Не из под Линукса, не из под винды (специально проверял). Как только разрешил простой CHAP, соединение получилось.</p>]]></content>
			<author>
				<name><![CDATA[User150]]></name>
				<uri>https://linuxforum.ru/profile.php?id=24053</uri>
			</author>
			<updated>2012-06-28T08:15:16Z</updated>
			<id>https://linuxforum.ru/viewtopic.php?pid=284653#p284653</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Домашний роутер через городскую сетку и VPN в интернет]]></title>
			<link rel="alternate" href="https://linuxforum.ru/viewtopic.php?pid=284647#p284647" />
			<content type="html"><![CDATA[<p>Если еще актуально то вот:<br /><a href="http://wiki.debian.org/ru/pptp-linux">http://wiki.debian.org/ru/pptp-linux</a><br />Тут все очень хорошо описано.</p><p>Выложи сюда маршрутизацию (route -n)</p><p>В ней у тебя скорее всего будет следующее:<br />3 Маршрута:<br />1. Маршрут в локальную сеть 192.168.0.0 через 192.168.0.2<br />2. Маршрут в подсеть 10.а.b.<strong>y</strong> через 0.0.0.0<br />3. Маршрут в&nbsp; подсеть 0.0.0.0 через 10.а.b.<strong>z</strong></p><p>При создании vpn соединения, он будет посылать запрос на авторизацию в соответсвии с таблицей маршрутизации, то по маршруту 0.0.0.0 через 10.а.b.<strong>z</strong>. Соответственно интерфейс для vpn выбирается не вписыванием его куда либо а через таблицу маршрутизации.</p><p>А по второму вопросу читай по ссылке, которую я дал. Там есть ответ.</p>]]></content>
			<author>
				<name><![CDATA[Ovoshlook]]></name>
				<uri>https://linuxforum.ru/profile.php?id=15792</uri>
			</author>
			<updated>2012-06-28T08:04:40Z</updated>
			<id>https://linuxforum.ru/viewtopic.php?pid=284647#p284647</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Домашний роутер через городскую сетку и VPN в интернет]]></title>
			<link rel="alternate" href="https://linuxforum.ru/viewtopic.php?pid=282653#p282653" />
			<content type="html"><![CDATA[<p>Лог ошибок <em>/var/log/ppp-connect-errors</em> содержит единственную фразу <em>sh: PPTP: not found</em><br />Есть еще вопросы:<br /> - Как задать конкретный интерфейс для VPN канала? У меня их два: eth0 и eth1.<br /> - Как задать задержки запуска VPN подключения? В моём случае винда сначала получает IP по DHCP, затем через полученный IP запускает процедуру VPN подключения. Эта процедура визуально занимает от 3-5 секунд до минуты порой. Кроме того, похоже, провайдер &quot;повесил&quot; минутный интервал для повторного подключения в случае разрыва соединения VPN.</p>]]></content>
			<author>
				<name><![CDATA[User150]]></name>
				<uri>https://linuxforum.ru/profile.php?id=24053</uri>
			</author>
			<updated>2012-06-18T02:49:01Z</updated>
			<id>https://linuxforum.ru/viewtopic.php?pid=282653#p282653</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Домашний роутер через городскую сетку и VPN в интернет]]></title>
			<link rel="alternate" href="https://linuxforum.ru/viewtopic.php?pid=280612#p280612" />
			<content type="html"><![CDATA[<p>Так и не заработал. <br /></p><ul><li><p>Снес поставил Debian CD1 (т.е. только Х и системные утилиты)</p></li><li><p>Инсталировал pptp-linux</p></li><li><p>поправил 4 конфига (включая interfaces)</p></li><li><p>не работает <img src="https://linuxforum.ru/img/smilies/ac.gif" alt="ac" /></p></li></ul><p>Есть где логи посмотреть, что происходит после <em>pon PPTP</em> ?<br />И что после <em>/etc/ppp/ip-up ppp0</em> ?</p>]]></content>
			<author>
				<name><![CDATA[User150]]></name>
				<uri>https://linuxforum.ru/profile.php?id=24053</uri>
			</author>
			<updated>2012-06-07T18:56:35Z</updated>
			<id>https://linuxforum.ru/viewtopic.php?pid=280612#p280612</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Домашний роутер через городскую сетку и VPN в интернет]]></title>
			<link rel="alternate" href="https://linuxforum.ru/viewtopic.php?pid=280479#p280479" />
			<content type="html"><![CDATA[<div class="quotebox"><cite>Kettler пишет:</cite><blockquote><div class="quotebox"><cite>User150 пишет:</cite><blockquote><p>require-mppe-128<br />require-mschap-v2</p></blockquote></div><p>точно необходимо у прова шифрование?</p></blockquote></div><p>В инструкции провайдера для виндового ВПН стоят такие чек-боксы.<br />Вчера переставил Дибиан, сейчас начну проверять.</p>]]></content>
			<author>
				<name><![CDATA[User150]]></name>
				<uri>https://linuxforum.ru/profile.php?id=24053</uri>
			</author>
			<updated>2012-06-07T15:51:27Z</updated>
			<id>https://linuxforum.ru/viewtopic.php?pid=280479#p280479</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Домашний роутер через городскую сетку и VPN в интернет]]></title>
			<link rel="alternate" href="https://linuxforum.ru/viewtopic.php?pid=280131#p280131" />
			<content type="html"><![CDATA[<div class="quotebox"><cite>User150 пишет:</cite><blockquote><p>require-mppe-128<br />require-mschap-v2</p></blockquote></div><p>точно необходимо у прова шифрование?<br /></p><div class="quotebox"><cite>User150 пишет:</cite><blockquote><p>options</p></blockquote></div><p>вообще не трогай.<br /></p><div class="quotebox"><cite>User150 пишет:</cite><blockquote><p>#noauth</p></blockquote></div><p>раскоментируй.</p>]]></content>
			<author>
				<name><![CDATA[Kettler]]></name>
				<uri>https://linuxforum.ru/profile.php?id=11719</uri>
			</author>
			<updated>2012-06-06T18:10:51Z</updated>
			<id>https://linuxforum.ru/viewtopic.php?pid=280131#p280131</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Домашний роутер через городскую сетку и VPN в интернет]]></title>
			<link rel="alternate" href="https://linuxforum.ru/viewtopic.php?pid=279860#p279860" />
			<content type="html"><![CDATA[<div class="quotebox"><cite>Kettler пишет:</cite><blockquote><p>покаж все конфиги.</p></blockquote></div><p>pptpd-options<br /></p><div class="fancy_spoiler_switcher"><div class="fancy_spoiler_switcher_header" data-lang-open="открыть спойлер" data-lang-close="скрыть спойлер"><strong>+</strong>&nbsp;открыть спойлер</div><div class="fancy_spoiler"><p>###############################################################################<br /># $Id: pptpd-options 4643 2006-11-06 18:42:43Z rene $<br />#<br /># Sample Poptop PPP options file /etc/ppp/pptpd-options<br /># Options used by PPP when a connection arrives from a client.<br /># This file is pointed to by /etc/pptpd.conf option keyword.<br /># Changes are effective on the next connection.&nbsp; See &quot;man pppd&quot;.<br />#<br /># You are expected to change this file to suit your system.&nbsp; As<br /># packaged, it requires PPP 2.4.2 and the kernel MPPE module.<br />###############################################################################</p><br /><p># Authentication</p><p># Name of the local system for authentication purposes <br /># (must match the second field in /etc/ppp/chap-secrets entries)<br />name pptpd</p><p># Optional: domain name to use for authentication<br /># domain mydomain.net</p><p># Strip the domain prefix from the username before authentication.<br /># (applies if you use pppd with chapms-strip-domain patch)<br />#chapms-strip-domain</p><br /><p># Encryption<br /># Debian: on systems with a kernel built with the package<br /># kernel-patch-mppe &gt;= 2.4.2 and using ppp &gt;= 2.4.2, ...<br /># {{{<br />refuse-pap<br />refuse-chap<br />refuse-mschap<br /># Require the peer to authenticate itself using MS-CHAPv2 [Microsoft<br /># Challenge Handshake Authentication Protocol, Version 2] authentication.<br />require-mschap-v2<br /># Require MPPE 128-bit encryption<br /># (note that MPPE requires the use of MSCHAP-V2 during authentication)<br />require-mppe-128<br /># }}}</p><br /><br /><br /><p># Network and Routing</p><p># If pppd is acting as a server for Microsoft Windows clients, this<br /># option allows pppd to supply one or two DNS (Domain Name Server)<br /># addresses to the clients.&nbsp; The first instance of this option<br /># specifies the primary DNS address; the second instance (if given)<br /># specifies the secondary DNS address.<br /># Attention! This information may not be taken into account by a Windows<br /># client. See KB311218 in Microsoft&#039;s knowledge base for more information.<br />#ms-dns 10.0.0.1<br />#ms-dns 10.0.0.2</p><p># If pppd is acting as a server for Microsoft Windows or &quot;Samba&quot;<br /># clients, this option allows pppd to supply one or two WINS (Windows<br /># Internet Name Services) server addresses to the clients.&nbsp; The first<br /># instance of this option specifies the primary WINS address; the<br /># second instance (if given) specifies the secondary WINS address.<br />#ms-wins 10.0.0.3<br />#ms-wins 10.0.0.4</p><p># Add an entry to this system&#039;s ARP [Address Resolution Protocol]<br /># table with the IP address of the peer and the Ethernet address of this<br /># system.&nbsp; This will have the effect of making the peer appear to other<br /># systems to be on the local ethernet.<br /># (you do not need this if your PPTP server is responsible for routing<br /># packets to the clients -- James Cameron)<br />proxyarp</p><p># Debian: do not replace the default route<br />nodefaultroute</p><br /><p># Logging</p><p># Enable connection debugging facilities.<br /># (see your syslog configuration for where pppd sends to)<br />#debug</p><p># Print out all the option values which have been set.<br /># (often requested by mailing list to verify options)<br />#dump</p><br /><p># Miscellaneous</p><p># Create a UUCP-style lock file for the pseudo-tty to ensure exclusive<br /># access.<br />lock</p><p># Disable BSD-Compress compression<br />nobsdcomp</p></div></div><p>0000usepeerdns из ip-up.d<br /></p><div class="fancy_spoiler_switcher"><div class="fancy_spoiler_switcher_header" data-lang-open="открыть спойлер" data-lang-close="скрыть спойлер"><strong>+</strong>&nbsp;открыть спойлер</div><div class="fancy_spoiler"><p>#!/bin/sh -e</p><p># this variable is only set if the usepeerdns pppd option is being used<br />[ &quot;$USEPEERDNS&quot; ] || exit 0</p><p># exit if the resolvconf package is installed<br />[ -x /sbin/resolvconf ] &amp;&amp; exit 0</p><p># create the file if it does not exist<br />if [ ! -e /etc/resolv.conf ]; then<br />&nbsp; : &gt; /etc/resolv.conf<br />fi</p><p># follow any symlink to find the real file<br />REALRESOLVCONF=$(readlink --canonicalize /etc/resolv.conf)</p><p># merge the new nameservers with the other options from the old configuration<br />{<br />&nbsp; cat /etc/ppp/resolv.conf<br />&nbsp; grep --invert-match &#039;^nameserver[[:space:]]&#039; &quot;$REALRESOLVCONF&quot; || true<br />} &gt; &quot;$REALRESOLVCONF.tmp&quot;</p><p># backup the old configuration and install the new one<br />cp -a &quot;$REALRESOLVCONF&quot; &quot;$REALRESOLVCONF.pppd-backup.$PPP_IFACE&quot;<br />mv -f &quot;$REALRESOLVCONF.tmp&quot; &quot;$REALRESOLVCONF&quot;</p><p># restart nscd because resolv.conf has changed<br />if [ -e /var/run/nscd.pid ]; then<br />&nbsp; /etc/init.d/nscd restart || true<br />fi</p><p>exit 0</p></div></div><p>chap-secrets<br /></p><div class="fancy_spoiler_switcher"><div class="fancy_spoiler_switcher_header" data-lang-open="открыть спойлер" data-lang-close="скрыть спойлер"><strong>+</strong>&nbsp;открыть спойлер</div><div class="fancy_spoiler"><p># Secrets for authentication using CHAP<br /># client&nbsp; &nbsp; server&nbsp; &nbsp; secret&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; IP addresses<br />&lt;My_login&gt;&nbsp; &nbsp; PPTP &lt;My_password&gt;&nbsp; &nbsp; *</p></div></div><br /><p>exim4 из ip-up.d<br /></p><div class="fancy_spoiler_switcher"><div class="fancy_spoiler_switcher_header" data-lang-open="открыть спойлер" data-lang-close="скрыть спойлер"><strong>+</strong>&nbsp;открыть спойлер</div><div class="fancy_spoiler"><p>#!/bin/sh</p><p>if [ -n &quot;$EX4DEBUG&quot; ]; then<br />&nbsp; echo &quot;now debugging $0 $@&quot;<br />&nbsp; set -x<br />fi</p><p>[ -x /usr/lib/exim4/exim4 ] || exit 0</p><p>[ -f /etc/default/exim4 ] &amp;&amp; . /etc/default/exim4</p><p>if [ &quot;${QUEUERUNNER}&quot; != &quot;no&quot; ] ; then<br /># Flush exim queue<br />&nbsp; &nbsp; /usr/sbin/exim4 -qqf ${QUEUERUNNEROPTIONS} ${COMMONOPTIONS}<br />fi</p></div></div><br /><p>/etc/hostname<br /></p><div class="fancy_spoiler_switcher"><div class="fancy_spoiler_switcher_header" data-lang-open="открыть спойлер" data-lang-close="скрыть спойлер"><strong>+</strong>&nbsp;открыть спойлер</div><div class="fancy_spoiler"><p>&lt;host_name&gt;</p></div></div><p>ifconfig -a<br /></p><div class="fancy_spoiler_switcher"><div class="fancy_spoiler_switcher_header" data-lang-open="открыть спойлер" data-lang-close="скрыть спойлер"><strong>+</strong>&nbsp;открыть спойлер</div><div class="fancy_spoiler"><p>ifconfig -a тут в запарке не поднял <em>pon ppp0</em>, но здесь он обычно ppp0 без Айпишника<br />eth0&nbsp; &nbsp; &nbsp; Link encap:Ethernet&nbsp; HWaddr f4:6d:04:73:bd:e9&nbsp; <br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; inet addr:192.168.0.2&nbsp; Bcast:192.168.0.255&nbsp; Mask:255.255.255.0<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; UP BROADCAST MULTICAST&nbsp; MTU:1500&nbsp; Metric:1<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; RX packets:0 errors:0 dropped:0 overruns:0 frame:0<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; TX packets:0 errors:0 dropped:0 overruns:0 carrier:0<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; collisions:0 txqueuelen:1000 <br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; RX bytes:0 (0.0 B)&nbsp; TX bytes:0 (0.0 B)<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Interrupt:27 Base address:0x4000 </p><p>eth1&nbsp; &nbsp; &nbsp; Link encap:Ethernet&nbsp; HWaddr 00:1b:21:bf:66:33&nbsp; <br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; inet addr:10.XXX.YYY.ZZZ&nbsp; Bcast:10.55.15.255&nbsp; Mask:255.255.254.0<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; inet6 addr: fe80::21b:21ff:febf:6633/64 Scope:Link<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; UP BROADCAST RUNNING MULTICAST&nbsp; MTU:1500&nbsp; Metric:1<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; RX packets:1498 errors:0 dropped:0 overruns:0 frame:0<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; TX packets:109 errors:0 dropped:0 overruns:0 carrier:0<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; collisions:0 txqueuelen:1000 <br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; RX bytes:111503 (108.8 KiB)&nbsp; TX bytes:12823 (12.5 KiB)<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Interrupt:16 Memory:feac0000-feae0000 </p><p>lo&nbsp; &nbsp; &nbsp; &nbsp; Link encap:Local Loopback&nbsp; <br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; inet addr:127.0.0.1&nbsp; Mask:255.0.0.0<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; inet6 addr: ::1/128 Scope:Host<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; UP LOOPBACK RUNNING&nbsp; MTU:16436&nbsp; Metric:1<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; RX packets:104 errors:0 dropped:0 overruns:0 frame:0<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; TX packets:104 errors:0 dropped:0 overruns:0 carrier:0<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; collisions:0 txqueuelen:0 <br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; RX bytes:8604 (8.4 KiB)&nbsp; TX bytes:8604 (8.4 KiB)</p><p>pan0&nbsp; &nbsp; &nbsp; Link encap:Ethernet&nbsp; HWaddr 12:9d:b8:65:d6:1f&nbsp; <br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; BROADCAST MULTICAST&nbsp; MTU:1500&nbsp; Metric:1<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; RX packets:0 errors:0 dropped:0 overruns:0 frame:0<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; TX packets:0 errors:0 dropped:0 overruns:0 carrier:0<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; collisions:0 txqueuelen:0 <br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; RX bytes:0 (0.0 B)&nbsp; TX bytes:0 (0.0 B)</p></div></div><p>interfaces<br /></p><div class="fancy_spoiler_switcher"><div class="fancy_spoiler_switcher_header" data-lang-open="открыть спойлер" data-lang-close="скрыть спойлер"><strong>+</strong>&nbsp;открыть спойлер</div><div class="fancy_spoiler"><p># This file describes the network interfaces available on your system<br /># and how to activate them. For more information, see interfaces(5).</p><p># The loopback network interface<br />auto lo<br />iface lo inet loopback</p><p>auto eth1 <br />iface eth1 inet dhcp</p><p>auto eth0<br />iface eth0 inet static<br />&nbsp; &nbsp; address&nbsp; &nbsp; &nbsp; &nbsp; 192.168.0.2<br />&nbsp; &nbsp; netmask &nbsp; &nbsp; 255.255.255.0<br />&nbsp; &nbsp; broadcast&nbsp; &nbsp; 192.168.0.255<br />&nbsp; &nbsp; gateway&nbsp; &nbsp; &nbsp; &nbsp; 192.168.0.1</p></div></div><p>options<br /></p><div class="fancy_spoiler_switcher"><div class="fancy_spoiler_switcher_header" data-lang-open="открыть спойлер" data-lang-close="скрыть спойлер"><strong>+</strong>&nbsp;открыть спойлер</div><div class="fancy_spoiler"><p># /etc/ppp/options<br /># <br /># Originally created by Jim Knoble &lt;jmknoble@mercury.interpath.net&gt;<br /># Modified for Debian by alvar Bray &lt;alvar@meiko.co.uk&gt;<br /># Modified for PPP Server setup by Christoph Lameter &lt;clameter@debian.org&gt;<br />#<br /># To quickly see what options are active in this file, use this command:<br />#&nbsp; &nbsp;egrep -v &#039;#|^ *$&#039; /etc/ppp/options</p><p># Specify which DNS Servers the incoming Win95 or WinNT Connection should use<br /># Two Servers can be remotely configured<br /># ms-dns 192.168.1.1<br /># ms-dns 192.168.1.2</p><p># Specify which WINS Servers the incoming connection Win95 or WinNT should use<br /># ms-wins 192.168.1.50<br /># ms-wins 192.168.1.51</p><p># Run the executable or shell command specified after pppd has<br /># terminated the link.&nbsp; This script could, for example, issue commands<br /># to the modem to cause it to hang up if hardware modem control signals<br /># were not available.<br />#disconnect &quot;chat -- \d+++\d\c OK ath0 OK&quot;</p><p># async character map -- 32-bit hex; each bit is a character<br /># that needs to be escaped for pppd to receive it.&nbsp; 0x00000001<br /># represents &#039;\x01&#039;, and 0x80000000 represents &#039;\x1f&#039;.<br />asyncmap 0</p><p># Require the peer to authenticate itself before allowing network<br /># packets to be sent or received.<br /># Please do not disable this setting. It is expected to be standard in<br /># future releases of pppd. Use the call option (see manpage) to disable<br /># authentication for specific peers.<br />auth</p><p># Use hardware flow control (i.e. RTS/CTS) to control the flow of data<br /># on the serial port.<br />crtscts</p><p># Use software flow control (i.e. XON/XOFF) to control the flow of data<br /># on the serial port.<br />#xonxoff</p><p># Specifies that certain characters should be escaped on transmission<br /># (regardless of whether the peer requests them to be escaped with its<br /># async control character map).&nbsp; The characters to be escaped are<br /># specified as a list of hex numbers separated by commas.&nbsp; Note that<br /># almost any character can be specified for the escape option, unlike<br /># the asyncmap option which only allows control characters to be<br /># specified.&nbsp; The characters which may not be escaped are those with hex<br /># values 0x20 - 0x3f or 0x5e.<br />#escape 11,13,ff</p><p># Don&#039;t use the modem control lines.<br />#local</p><p># Specifies that pppd should use a UUCP-style lock on the serial device<br /># to ensure exclusive access to the device.<br />lock</p><p># Don&#039;t show the passwords when logging the contents of PAP packets.<br /># This is the default.<br />hide-password</p><p># When logging the contents of PAP packets, this option causes pppd to<br /># show the password string in the log message.<br />#show-password</p><p># Use the modem control lines.&nbsp; On Ultrix, this option implies hardware<br /># flow control, as for the crtscts option.&nbsp; (This option is not fully<br /># implemented.)<br />modem</p><p># Set the MRU [Maximum Receive Unit] value to &lt;n&gt; for negotiation.&nbsp; pppd<br /># will ask the peer to send packets of no more than &lt;n&gt; bytes. The<br /># minimum MRU value is 128.&nbsp; The default MRU value is 1500.&nbsp; A value of<br /># 296 is recommended for slow links (40 bytes for TCP/IP header + 256<br /># bytes of data).<br />#mru 542</p><p># Set the interface netmask to &lt;n&gt;, a 32 bit netmask in &quot;decimal dot&quot;<br /># notation (e.g. 255.255.255.0).<br />#netmask 255.255.255.0</p><p># Disables the default behaviour when no local IP address is specified,<br /># which is to determine (if possible) the local IP address from the<br /># hostname. With this option, the peer will have to supply the local IP<br /># address during IPCP negotiation (unless it specified explicitly on the<br /># command line or in an options file).<br />#noipdefault</p><p># Enables the &quot;passive&quot; option in the LCP.&nbsp; With this option, pppd will<br /># attempt to initiate a connection; if no reply is received from the<br /># peer, pppd will then just wait passively for a valid LCP packet from<br /># the peer (instead of exiting, as it does without this option).<br />#passive</p><p># With this option, pppd will not transmit LCP packets to initiate a<br /># connection until a valid LCP packet is received from the peer (as for<br /># the &quot;passive&quot; option with old versions of pppd).<br />#silent</p><p># Don&#039;t request or allow negotiation of any options for LCP and IPCP<br /># (use default values).<br />#-all</p><p># Disable Address/Control compression negotiation (use default, i.e.<br /># address/control field disabled).<br />#-ac</p><p># Disable asyncmap negotiation (use the default asyncmap, i.e. escape<br /># all control characters).<br />#-am</p><p># Don&#039;t fork to become a background process (otherwise pppd will do so<br /># if a serial device is specified).<br />#-detach</p><p># Disable IP address negotiation (with this option, the remote IP<br /># address must be specified with an option on the command line or in<br /># an options file).<br />#-ip</p><p># Disable IPCP negotiation and IP communication. This option should<br /># only be required if the peer is buggy and gets confused by requests<br /># from pppd for IPCP negotiation.<br />#noip</p><p># Disable magic number negotiation.&nbsp; With this option, pppd cannot<br /># detect a looped-back line.<br />#-mn</p><p># Disable MRU [Maximum Receive Unit] negotiation (use default, i.e.<br /># 1500).<br />#-mru</p><p># Disable protocol field compression negotiation (use default, i.e.<br /># protocol field compression disabled).<br />#-pc</p><p># Require the peer to authenticate itself using PAP.<br />#+pap</p><p># Don&#039;t agree to authenticate using PAP.<br />#-pap</p><p># Require the peer to authenticate itself using CHAP [Cryptographic<br /># Handshake Authentication Protocol] authentication.<br />#+chap</p><p># Don&#039;t agree to authenticate using CHAP.<br />#-chap</p><p># Disable negotiation of Van Jacobson style IP header compression (use<br /># default, i.e. no compression).<br />#-vj</p><p># Increase debugging level (same as -d).&nbsp; If this option is given, pppd<br /># will log the contents of all control packets sent or received in a<br /># readable form.&nbsp; The packets are logged through syslog with facility<br /># daemon and level debug. This information can be directed to a file by<br /># setting up /etc/syslog.conf appropriately (see syslog.conf(5)).&nbsp; (If<br /># pppd is compiled with extra debugging enabled, it will log messages<br /># using facility local2 instead of daemon).<br />#debug</p><p># Append the domain name &lt;d&gt; to the local host name for authentication<br /># purposes.&nbsp; For example, if gethostname() returns the name porsche,<br /># but the fully qualified domain name is porsche.Quotron.COM, you would<br /># use the domain option to set the domain name to Quotron.COM.<br />#domain &lt;d&gt;</p><p># Enable debugging code in the kernel-level PPP driver.&nbsp; The argument n<br /># is a number which is the sum of the following values: 1 to enable<br /># general debug messages, 2 to request that the contents of received<br /># packets be printed, and 4 to request that the contents of transmitted<br /># packets be printed.<br />#kdebug n</p><p># Set the MTU [Maximum Transmit Unit] value to &lt;n&gt;. Unless the peer<br /># requests a smaller value via MRU negotiation, pppd will request that<br /># the kernel networking code send data packets of no more than n bytes<br /># through the PPP network interface.<br />#mtu &lt;n&gt;</p><p># Set the name of the local system for authentication purposes to &lt;n&gt;.<br /># This is a privileged option. With this option, pppd will use lines in the<br /># secrets files which have &lt;n&gt; as the second field when looking for a<br /># secret to use in authenticating the peer. In addition, unless overridden<br /># with the user option, &lt;n&gt; will be used as the name to send to the peer<br /># when authenticating the local system to the peer. (Note that pppd does<br /># not append the domain name to &lt;n&gt;.)<br />#name &lt;n&gt;</p><p># Enforce the use of the hostname as the name of the local system for<br /># authentication purposes (overrides the name option).<br />#usehostname</p><p># Set the assumed name of the remote system for authentication purposes<br /># to &lt;n&gt;.<br />#remotename &lt;n&gt;</p><p># Add an entry to this system&#039;s ARP [Address Resolution Protocol]<br /># table with the IP address of the peer and the Ethernet address of this<br /># system.<br />#proxyarp</p><p># Use the system password database for authenticating the peer using<br /># PAP. Note: mgetty already provides this option. If this is specified<br /># then dialin from users using a script under Linux to fire up ppp wont work.<br /># login</p><p># If this option is given, pppd will send an LCP echo-request frame to the<br /># peer every n seconds. Normally the peer should respond to the echo-request<br /># by sending an echo-reply. This option can be used with the<br /># lcp-echo-failure option to detect that the peer is no longer connected.<br />lcp-echo-interval 30</p><p># If this option is given, pppd will presume the peer to be dead if n<br /># LCP echo-requests are sent without receiving a valid LCP echo-reply.<br /># If this happens, pppd will terminate the connection.&nbsp; Use of this<br /># option requires a non-zero value for the lcp-echo-interval parameter.<br /># This option can be used to enable pppd to terminate after the physical<br /># connection has been broken (e.g., the modem has hung up) in<br /># situations where no hardware modem control lines are available.<br />lcp-echo-failure 4</p><p># Set the LCP restart interval (retransmission timeout) to &lt;n&gt; seconds<br /># (default 3).<br />#lcp-restart &lt;n&gt;</p><p># Set the maximum number of LCP terminate-request transmissions to &lt;n&gt;<br /># (default 3).<br />#lcp-max-terminate &lt;n&gt;</p><p># Set the maximum number of LCP configure-request transmissions to &lt;n&gt;<br /># (default 10).<br />#lcp-max-configure &lt;n&gt;</p><p># Set the maximum number of LCP configure-NAKs returned before starting<br /># to send configure-Rejects instead to &lt;n&gt; (default 10).<br />#lcp-max-failure &lt;n&gt;</p><p># Set the IPCP restart interval (retransmission timeout) to &lt;n&gt;<br /># seconds (default 3).<br />#ipcp-restart &lt;n&gt;</p><p># Set the maximum number of IPCP terminate-request transmissions to &lt;n&gt;<br /># (default 3).<br />#ipcp-max-terminate &lt;n&gt;</p><p># Set the maximum number of IPCP configure-request transmissions to &lt;n&gt;<br /># (default 10).<br />#ipcp-max-configure &lt;n&gt;</p><p># Set the maximum number of IPCP configure-NAKs returned before starting<br /># to send configure-Rejects instead to &lt;n&gt; (default 10).<br />#ipcp-max-failure &lt;n&gt;</p><p># Set the PAP restart interval (retransmission timeout) to &lt;n&gt; seconds<br /># (default 3).<br />#pap-restart &lt;n&gt;</p><p># Set the maximum number of PAP authenticate-request transmissions to<br /># &lt;n&gt; (default 10).<br />#pap-max-authreq &lt;n&gt;</p><p># Set the maximum time that pppd will wait for the peer to authenticate<br /># itself with PAP to &lt;n&gt; seconds (0 means no limit).<br />#pap-timeout &lt;n&gt;</p><p># Set the CHAP restart interval (retransmission timeout for<br /># challenges) to &lt;n&gt; seconds (default 3).<br />#chap-restart &lt;n&gt;</p><p># Set the maximum number of CHAP challenge transmissions to &lt;n&gt;<br /># (default 10).<br />#chap-max-challenge</p><p># If this option is given, pppd will rechallenge the peer every &lt;n&gt;<br /># seconds.<br />#chap-interval &lt;n&gt;</p><p># With this option, pppd will accept the peer&#039;s idea of our local IP<br /># address, even if the local IP address was specified in an option.<br />#ipcp-accept-local</p><p># With this option, pppd will accept the peer&#039;s idea of its (remote) IP<br /># address, even if the remote IP address was specified in an option.<br />#ipcp-accept-remote</p><p># Disable the IPXCP and IPX protocols.<br /># To let pppd pass IPX packets comment this out --- you&#039;ll probably also<br /># want to install ipxripd, and have the Internal IPX Network option enabled<br /># in your kernel.&nbsp; /usr/doc/HOWTO/IPX-HOWTO.gz contains more info.<br />noipx</p><p># Exit once a connection has been made and terminated. This is the default,<br /># unless the `persist&#039; or `demand&#039; option has been specified.<br />#nopersist</p><p># Do not exit after a connection is terminated; instead try to reopen<br /># the connection.<br />#persist</p><p># Terminate after n consecutive failed connection attempts.<br /># A value of 0 means no limit. The default value is 10.<br />#maxfail &lt;n&gt;</p><p># Initiate the link only on demand, i.e. when data traffic is present. <br /># With this option, the remote IP address must be specified by the user on<br /># the command line or in an options file.&nbsp; Pppd will initially configure<br /># the interface and enable it for IP traffic without connecting to the peer. <br /># When traffic is available, pppd will connect to the peer and perform<br /># negotiation, authentication, etc.&nbsp; When this is completed, pppd will<br /># commence passing data packets (i.e., IP packets) across the link.<br />#demand</p><p># Specifies that pppd should disconnect if the link is idle for &lt;n&gt; seconds.<br /># The link is idle when no data packets (i.e. IP packets) are being sent or<br /># received.&nbsp; Note: it is not advisable to use this option with the persist<br /># option without the demand option.&nbsp; If the active-filter option is given,<br /># data packets which are rejected by the specified activity filter also<br /># count as the link being idle.<br />#idle &lt;n&gt;</p><p># Specifies how many seconds to wait before re-initiating the link after<br /># it terminates.&nbsp; This option only has any effect if the persist or demand<br /># option is used.&nbsp; The holdoff period is not applied if the link was<br /># terminated because it was idle.<br />#holdoff &lt;n&gt;</p><p># Wait for up n milliseconds after the connect script finishes for a valid<br /># PPP packet from the peer.&nbsp; At the end of this time, or when a valid PPP<br /># packet is received from the peer, pppd will commence negotiation by<br /># sending its first LCP packet.&nbsp; The default value is 1000 (1 second).<br /># This wait period only applies if the connect or pty option is used.<br />#connect-delay &lt;n&gt;</p><p># Packet filtering: for more information, see pppd(8)<br /># Any packets matching the filter expression will be interpreted as link<br /># activity, and will cause a &quot;demand&quot; connection to be activated, and reset<br /># the idle connection timer. (idle option)<br /># The filter expression is akin to that of tcpdump(1)<br />#active-filter &lt;filter-expression&gt;</p><p># ---&lt;End of File&gt;---</p></div></div><br /><p>options.pptp<br /></p><div class="fancy_spoiler_switcher"><div class="fancy_spoiler_switcher_header" data-lang-open="открыть спойлер" data-lang-close="скрыть спойлер"><strong>+</strong>&nbsp;открыть спойлер</div><div class="fancy_spoiler"><p>###############################################################################<br /># $Id: options.pptp,v 1.3 2006/03/26 23:11:05 quozl Exp $<br />#<br /># Sample PPTP PPP options file /etc/ppp/options.pptp<br /># Options used by PPP when a connection is made by a PPTP client.<br /># This file can be referred to by an /etc/ppp/peers file for the tunnel.<br /># Changes are effective on the next connection.&nbsp; See &quot;man pppd&quot;.<br />#<br /># You are expected to change this file to suit your system.&nbsp; As<br /># packaged, it requires PPP 2.4.2 or later from <a href="http://ppp.samba.org/">http://ppp.samba.org/</a><br /># and the kernel MPPE module available from the CVS repository also on<br /># <a href="http://ppp.samba.org/,">http://ppp.samba.org/,</a> which is packaged for DKMS as kernel_ppp_mppe.<br />###############################################################################</p><p># Lock the port<br />lock</p><p># Authentication<br /># We don&#039;t need the tunnel server to authenticate itself<br />noauth</p><p># We won&#039;t do PAP, EAP, CHAP, or MSCHAP, but we will accept MSCHAP-V2<br /># (you may need to remove these refusals if the server is not using MPPE)<br />refuse-pap<br />refuse-eap<br />refuse-chap<br />refuse-mschap</p><p># Compression<br /># Turn off compression protocols we know won&#039;t be used<br />nobsdcomp<br />nodeflate</p><p># Encryption<br /># (There have been multiple versions of PPP with encryption support,<br /># choose with of the following sections you will use.&nbsp; Note that MPPE<br /># requires the use of MSCHAP-V2 during authentication)</p><p># <a href="http://ppp.samba.org/">http://ppp.samba.org/</a> the PPP project version of PPP by Paul Mackarras<br /># ppp-2.4.2 or later with MPPE only, kernel module ppp_mppe.o<br /># {{{<br /># Require MPPE 128-bit encryption<br />#require-mppe-128<br /># }}}</p><p># <a href="http://polbox.com/h/hs001/">http://polbox.com/h/hs001/</a> fork from PPP project by Jan Dubiec<br /># ppp-2.4.2 or later with MPPE and MPPC, kernel module ppp_mppe_mppc.o<br /># {{{<br /># Require MPPE 128-bit encryption<br />#mppe required,stateless<br /># }}}</p></div></div><p>pptpd-options<br /></p><div class="fancy_spoiler_switcher"><div class="fancy_spoiler_switcher_header" data-lang-open="открыть спойлер" data-lang-close="скрыть спойлер"><strong>+</strong>&nbsp;открыть спойлер</div><div class="fancy_spoiler"><p>###############################################################################<br /># $Id: pptpd-options 4643 2006-11-06 18:42:43Z rene $<br />#<br /># Sample Poptop PPP options file /etc/ppp/pptpd-options<br /># Options used by PPP when a connection arrives from a client.<br /># This file is pointed to by /etc/pptpd.conf option keyword.<br /># Changes are effective on the next connection.&nbsp; See &quot;man pppd&quot;.<br />#<br /># You are expected to change this file to suit your system.&nbsp; As<br /># packaged, it requires PPP 2.4.2 and the kernel MPPE module.<br />###############################################################################</p><br /><p># Authentication</p><p># Name of the local system for authentication purposes <br /># (must match the second field in /etc/ppp/chap-secrets entries)<br />name pptpd</p><p># Optional: domain name to use for authentication<br /># domain mydomain.net</p><p># Strip the domain prefix from the username before authentication.<br /># (applies if you use pppd with chapms-strip-domain patch)<br />#chapms-strip-domain</p><br /><p># Encryption<br /># Debian: on systems with a kernel built with the package<br /># kernel-patch-mppe &gt;= 2.4.2 and using ppp &gt;= 2.4.2, ...<br /># {{{<br />refuse-pap<br />refuse-chap<br />refuse-mschap<br /># Require the peer to authenticate itself using MS-CHAPv2 [Microsoft<br /># Challenge Handshake Authentication Protocol, Version 2] authentication.<br />require-mschap-v2<br /># Require MPPE 128-bit encryption<br /># (note that MPPE requires the use of MSCHAP-V2 during authentication)<br />require-mppe-128<br /># }}}</p><br /><br /><br /><p># Network and Routing</p><p># If pppd is acting as a server for Microsoft Windows clients, this<br /># option allows pppd to supply one or two DNS (Domain Name Server)<br /># addresses to the clients.&nbsp; The first instance of this option<br /># specifies the primary DNS address; the second instance (if given)<br /># specifies the secondary DNS address.<br /># Attention! This information may not be taken into account by a Windows<br /># client. See KB311218 in Microsoft&#039;s knowledge base for more information.<br />#ms-dns 10.0.0.1<br />#ms-dns 10.0.0.2</p><p># If pppd is acting as a server for Microsoft Windows or &quot;Samba&quot;<br /># clients, this option allows pppd to supply one or two WINS (Windows<br /># Internet Name Services) server addresses to the clients.&nbsp; The first<br /># instance of this option specifies the primary WINS address; the<br /># second instance (if given) specifies the secondary WINS address.<br />#ms-wins 10.0.0.3<br />#ms-wins 10.0.0.4</p><p># Add an entry to this system&#039;s ARP [Address Resolution Protocol]<br /># table with the IP address of the peer and the Ethernet address of this<br /># system.&nbsp; This will have the effect of making the peer appear to other<br /># systems to be on the local ethernet.<br /># (you do not need this if your PPTP server is responsible for routing<br /># packets to the clients -- James Cameron)<br />proxyarp</p><p># Debian: do not replace the default route<br />nodefaultroute</p><br /><p># Logging</p><p># Enable connection debugging facilities.<br /># (see your syslog configuration for where pppd sends to)<br />#debug</p><p># Print out all the option values which have been set.<br /># (often requested by mailing list to verify options)<br />#dump</p><br /><p># Miscellaneous</p><p># Create a UUCP-style lock file for the pseudo-tty to ensure exclusive<br /># access.<br />lock</p><p># Disable BSD-Compress compression<br />nobsdcomp</p></div></div><p>resolv.conf<br /></p><div class="fancy_spoiler_switcher"><div class="fancy_spoiler_switcher_header" data-lang-open="открыть спойлер" data-lang-close="скрыть спойлер"><strong>+</strong>&nbsp;открыть спойлер</div><div class="fancy_spoiler"><p>domain &lt;domain_name&gt;<br />search &lt;domain_name&gt;<br />nameserver &lt;DNS_IP_1&gt;<br />nameserver &lt;DNS_IP_2&gt;</p></div></div><br /><p>/etc/ppp/peers/PPTP<br /></p><div class="fancy_spoiler_switcher"><div class="fancy_spoiler_switcher_header" data-lang-open="открыть спойлер" data-lang-close="скрыть спойлер"><strong>+</strong>&nbsp;открыть спойлер</div><div class="fancy_spoiler"><p># example configuration for a dialup connection authenticated with PAP or CHAP<br />#<br /># This is the default configuration used by pon(1) and poff(1).<br /># See the manual page pppd(8) for information on all the options.</p><p># MUST CHANGE: replace myusername@realm with the PPP login name given to<br /># your by your provider.<br /># There should be a matching entry with the password in /etc/ppp/pap-secrets<br /># and/or /etc/ppp/chap-secrets.<br />#user admin77</p><p># MUST CHANGE: replace ******** with the phone number of your provider.<br /># The /etc/chatscripts/pap chat script may be modified to change the<br /># modem initialization string.<br />#connect &quot;/usr/sbin/chat -v -f /etc/chatscripts/pap -T ********&quot;</p><p># Serial device to which the modem is connected.<br /># /dev/modem</p><p># Speed of the serial line.<br /># 115200</p><p># Assumes that your IP address is allocated dynamically by the ISP.<br />#noipdefault<br /># Try to get the name server addresses from the ISP.<br />#usepeerdns<br /># Use this connection as the default route.<br />#defaultroute</p><p># Makes pppd &quot;dial again&quot; when the connection is lost.<br />persist</p><p># Do not ask the remote to authenticate.<br />#noauth</p><p>maxfail 0<br />lcp-echo-interval 60<br />lcp-echo-failure 4<br />defaultroute<br />pty &quot;pptp --loglevel 1 &lt;VPN_Server_URL&gt; --nolaunchpppd --nobuffer&quot;<br />name &lt;MY_Login&gt;<br />remotename PPTP<br />file /etc/ppp/options.pptp<br />ipparam PPTP</p></div></div><br /><p>/etc/ppp/peers/provider<br /></p><div class="fancy_spoiler_switcher"><div class="fancy_spoiler_switcher_header" data-lang-open="открыть спойлер" data-lang-close="скрыть спойлер"><strong>+</strong>&nbsp;открыть спойлер</div><div class="fancy_spoiler"><p># example configuration for a dialup connection authenticated with PAP or CHAP<br />#<br /># This is the default configuration used by pon(1) and poff(1).<br /># See the manual page pppd(8) for information on all the options.</p><p># MUST CHANGE: replace myusername@realm with the PPP login name given to<br /># your by your provider.<br /># There should be a matching entry with the password in /etc/ppp/pap-secrets<br /># and/or /etc/ppp/chap-secrets.<br />user &quot;myusername@realm&quot;</p><p># MUST CHANGE: replace ******** with the phone number of your provider.<br /># The /etc/chatscripts/pap chat script may be modified to change the<br /># modem initialization string.<br />connect &quot;/usr/sbin/chat -v -f /etc/chatscripts/pap -T ********&quot;</p><p># Serial device to which the modem is connected.<br />/dev/modem</p><p># Speed of the serial line.<br />115200</p><p># Assumes that your IP address is allocated dynamically by the ISP.<br />noipdefault<br /># Try to get the name server addresses from the ISP.<br />usepeerdns<br /># Use this connection as the default route.<br />defaultroute</p><p># Makes pppd &quot;dial again&quot; when the connection is lost.<br />persist</p><p># Do not ask the remote to authenticate.<br />noauth</p></div></div><p>У-ф-ф-ф <img src="https://linuxforum.ru/img/smilies/ab.gif" alt="ab" /></p>]]></content>
			<author>
				<name><![CDATA[User150]]></name>
				<uri>https://linuxforum.ru/profile.php?id=24053</uri>
			</author>
			<updated>2012-06-05T16:56:56Z</updated>
			<id>https://linuxforum.ru/viewtopic.php?pid=279860#p279860</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Домашний роутер через городскую сетку и VPN в интернет]]></title>
			<link rel="alternate" href="https://linuxforum.ru/viewtopic.php?pid=279754#p279754" />
			<content type="html"><![CDATA[<p>покаж все конфиги.</p>]]></content>
			<author>
				<name><![CDATA[Kettler]]></name>
				<uri>https://linuxforum.ru/profile.php?id=11719</uri>
			</author>
			<updated>2012-06-05T10:57:20Z</updated>
			<id>https://linuxforum.ru/viewtopic.php?pid=279754#p279754</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Домашний роутер через городскую сетку и VPN в интернет]]></title>
			<link rel="alternate" href="https://linuxforum.ru/viewtopic.php?pid=279651#p279651" />
			<content type="html"><![CDATA[<div class="quotebox"><cite>XliN пишет:</cite><blockquote><p>Общий шлюз будет всегда, а вот как раз что бы ходить по локалке прова и добавляются таблицы маршрутизации. <br />Хочется посмотреть что в /etc/resolv.conf</p></blockquote></div><p>В etc/resolv.conf я в своё время записал два айпишника ДНС серверов провайдера.<br />Исследование показало, что команда<br /><em>route add default dev ppp0</em> сообщает что сеть &quot;из даун&quot; что-то вроде этого.<br />Команда <em>/etc/ppp/ip-up ppp0</em> ни к чему не приводит.<br />Ранее я ошибочно писал, что в таблицах маршрутизации указан Айпишник данный мне от VPN. Это не так:( , на самом деле я запутался, сейчас распутался <img src="https://linuxforum.ru/img/smilies/ab.gif" alt="ab" /> это был Айпишник данный мне через DHCP для eth1. <br />Команда <em>pon $Tunnel</em> приводит к увеличению интерфейсов ppp0-pppX видимых в <em>ifconfig -a</em> но все они &quot;лежачие&quot;</p>]]></content>
			<author>
				<name><![CDATA[User150]]></name>
				<uri>https://linuxforum.ru/profile.php?id=24053</uri>
			</author>
			<updated>2012-06-04T20:33:19Z</updated>
			<id>https://linuxforum.ru/viewtopic.php?pid=279651#p279651</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Домашний роутер через городскую сетку и VPN в интернет]]></title>
			<link rel="alternate" href="https://linuxforum.ru/viewtopic.php?pid=279648#p279648" />
			<content type="html"><![CDATA[<p>Общий шлюз будет всегда, а вот как раз что бы ходить по локалке прова и добавляются таблицы маршрутизации. <br />Хочется посмотреть что в /etc/resolv.conf</p>]]></content>
			<author>
				<name><![CDATA[XliN]]></name>
				<uri>https://linuxforum.ru/profile.php?id=6412</uri>
			</author>
			<updated>2012-06-04T20:23:24Z</updated>
			<id>https://linuxforum.ru/viewtopic.php?pid=279648#p279648</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Домашний роутер через городскую сетку и VPN в интернет]]></title>
			<link rel="alternate" href="https://linuxforum.ru/viewtopic.php?pid=279645#p279645" />
			<content type="html"><![CDATA[<div class="quotebox"><cite>XliN пишет:</cite><blockquote><p>Если появился ррр0, то коннект есть. Покпжи<br />route -n или ip r l<br />тем самым узнаем твой шлюз по умолчанию. Так же покажи настройки dns + конфиг ррр.</p></blockquote></div><p>Я быстро показать не могу компа два, а монитор один. Надо отключаться переконтачивать всё на свете <img src="https://linuxforum.ru/img/smilies/ac.gif" alt="ac" />, но насколько я помню, route -n во всех маршрутах к городским подсетях показывал шлюзом айпишник данный мне через VPN.<br />Провайдер (насколько я помню) указал, что общий шлюз по умолчанию не нужен, т.к. в городские сетки следует ходить через таблицы маршрутизации, а в инет через VPN.</p>]]></content>
			<author>
				<name><![CDATA[User150]]></name>
				<uri>https://linuxforum.ru/profile.php?id=24053</uri>
			</author>
			<updated>2012-06-04T20:14:10Z</updated>
			<id>https://linuxforum.ru/viewtopic.php?pid=279645#p279645</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Домашний роутер через городскую сетку и VPN в интернет]]></title>
			<link rel="alternate" href="https://linuxforum.ru/viewtopic.php?pid=279643#p279643" />
			<content type="html"><![CDATA[<p>Если появился ррр0, то коннект есть. Покпжи<br />route -n или ip r l<br />тем самым узнаем твой шлюз по умолчанию. Так же покажи настройки dns + конфиг ррр.</p>]]></content>
			<author>
				<name><![CDATA[XliN]]></name>
				<uri>https://linuxforum.ru/profile.php?id=6412</uri>
			</author>
			<updated>2012-06-04T20:03:39Z</updated>
			<id>https://linuxforum.ru/viewtopic.php?pid=279643#p279643</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Домашний роутер через городскую сетку и VPN в интернет]]></title>
			<link rel="alternate" href="https://linuxforum.ru/viewtopic.php?pid=279640#p279640" />
			<content type="html"><![CDATA[<div class="quotebox"><cite>Kettler пишет:</cite><blockquote><p>...cделай так /etc/ppp/peers/PPTP</p></blockquote></div><p>Спасибо <img src="https://linuxforum.ru/img/smilies/ab.gif" alt="ab" /> Сделал. Кое что заработало.<br />Теперь вижу ppp0 в ifconfig, правда никакой активности не наблюдается.<br />В маршрутах указан айпишник присвоенный моему VPN соединению. <br />Но... Инета нет.<br />Все делал из под терминала. Где искать логи пока не знаю.<br />Возможно стоит приступить к файрволу? С чего начать? <br />Есть где доступное Хау-Ту ?</p><p>В ifconfig обнаружил интерфейс pan0. Вроде блютусов на мамке нет. Откуда он взялся?</p><p>Я тут начитавшись, включил рута в графическом режиме.&nbsp; Легче не стало. (потом поставлю минимальный образ с СиДи оболочку отключу)</p><p>Там в графической настройке сети есть закладка с VPN, но кнопка добавить серая. Видимо надо еще какой нибудь пакет происталить. <img src="https://linuxforum.ru/img/smilies/ac.gif" alt="ac" /></p><p>2 олл, я пытаюсь настроить доступ от домашнего компьютера к Инету через VPN сервер провайдера, т.е. настраиваю свой VPN клиент.&nbsp; Раньше я не знал, что это две разные штуки. Казалось туннель он и есть туннель с двух сторон одинаковый. Ан нет</p>]]></content>
			<author>
				<name><![CDATA[User150]]></name>
				<uri>https://linuxforum.ru/profile.php?id=24053</uri>
			</author>
			<updated>2012-06-04T19:49:52Z</updated>
			<id>https://linuxforum.ru/viewtopic.php?pid=279640#p279640</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Домашний роутер через городскую сетку и VPN в интернет]]></title>
			<link rel="alternate" href="https://linuxforum.ru/viewtopic.php?pid=279492#p279492" />
			<content type="html"><![CDATA[<div class="quotebox"><cite>ASDev пишет:</cite><blockquote><p>Единственное что не пойму - провайдер даёт доступ в инет через ВПН или ВЫ хотите давать доступ внутренней подсети к инету через ВПН?</p></blockquote></div><p>Вот и я не понял.</p>]]></content>
			<author>
				<name><![CDATA[zenon]]></name>
				<uri>https://linuxforum.ru/profile.php?id=6867</uri>
			</author>
			<updated>2012-06-04T08:56:47Z</updated>
			<id>https://linuxforum.ru/viewtopic.php?pid=279492#p279492</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Домашний роутер через городскую сетку и VPN в интернет]]></title>
			<link rel="alternate" href="https://linuxforum.ru/viewtopic.php?pid=279472#p279472" />
			<content type="html"><![CDATA[<p>Меня сейчас наверное запинают, но для начинающего рекомендую поставить WebMin, многие вопросы отпадут <img src="https://linuxforum.ru/img/smilies/ab.gif" alt="ab" /> Будете сетку и ВПН конфигурить из веб-морды. Единственное что не пойму - провайдер даёт доступ в инет через ВПН или ВЫ хотите давать доступ внутренней подсети к инету через ВПН?</p>]]></content>
			<author>
				<name><![CDATA[ASDev]]></name>
				<uri>https://linuxforum.ru/profile.php?id=24062</uri>
			</author>
			<updated>2012-06-04T08:11:57Z</updated>
			<id>https://linuxforum.ru/viewtopic.php?pid=279472#p279472</id>
		</entry>
</feed>
