openl2tp.org

Perhaps I don't understand.
Your ISP can assign the same IP address for its end of the PPP connection, but should always assign your side a unique IP address. Your system should have a route set such that your traffic is routed via the IP address assigned by your ISP. If you are being assigned the same address as another subscriber, that is a problem at the ISP. Or perhaps your system has a stale route table, such that you are trying to route via the wrong IP address, which is perhaps the IP address that was used for a previous time you were online?

I assumed that the ISP gets someone IP address. And the same address has pool, which I connect. In this I am not sure exactly.

The routes are not preserved after a reboot. The table has a route to the entire net of pools, I wrote about it in the first post. This is not correct?

Not sure if this is still relevant, but we had a similar issue with a pptp client doing some wacky VPN on a university network.

The fix was to do an explicit /32 route for the VPN access concentrator. So for example let's say you connect to 1.2.3.4 then the VPN server would assign 1.2.3.4 to it's end of the ppp connection, and for example 2.3.4.5 to your end. This results in a routing table in the kernel something like:



Now when the kernel tries to send a GRE (or l2tp or pptp frame) to the VPN server it ends up in the loop as it's trying to get to the VPN server via the VPN connection. Replacing the 1.2.3.4/32 dev pppX route with:



Sorts out the problem. We used to do this from ip-pre-up or ip-up (can't recall which one).

hello!
is there any solution for this issue?
i still get hanging with "soft lock up cpu" when i try to connect to "beeline" ISP with my ubuntu 12.04

Привет
Я для подключения использовал всегда статический адрес пула, и после того, как в очередной используемый адрес умер, я стал использовать другой. На новом пуле этой проблемы нет, что еще раз доказывает, что это проблема на стороне провайдера. Сейчас я использую адрес 83.102.255.55 и никаких проблем с утечкой не испытываю. Но это для Питера, для других городов, скорее всего, он не подойдет.

а как понять годный пул или глючный? =) методом научного тыка? и как вообще получить список всех пулов билайна? я немного чайник в этом. nslookup tp.internet.beeline.ru выдаёт только один айпи, а он же точно не один.

Пулы проверять да, методом тыка. А как список получить, я не помню. Вроде винда выдает, но сча что-то из-под нее не резолвится. Можно в гугле посмотреть, как чего