Pozdrav ja koristim Linux mint 6 i imam slican problem. Ppoe se konektuje dobije adresu od provajdera ali rute su problem ubaci neku bez veze i neotvara nista.Probao sam po ovom uputstvu : #
RTNETLINK answers: File exists
#
huge transmit data counters
#
LCP EchoReq without LCP EchoRep
Symptom: connection is established but no data transfer happens, ifconfig shows large amounts of data transmitted on PPTP tunnel, tcpdump shows many transmitted packets, the connection is closed after one minute, and debug logs contain this sequence:
rcvd [LCP EchoReq id=0x1
sent [LCP EchoRep id=0x1
sent [LCP EchoReq id=0x1
rcvd [LCP EchoReq id=0x2
sent [LCP EchoRep id=0x2
sent [LCP EchoReq id=0x2
which indicates that echo requests from the server are being received by the client, which issues an echo reply, but that echo requests from the client are not generating echo replies from the server.
Diagnosis: the route to the PPTP Server has changed to include the tunnel itself, and packets are being looped. Packets sent through the VPN are being encapsulated in PPP over GRE, and then sent through the same interface again.
See our diagram that explains this further. See our Routing HOWTO for more information about routing.
Solution: examine the routing table using netstat -rn before and after the tunnel becomes active. Determine why the route to the PPTP Server is via the tunnel interface. We list some possible reasons and actions that can be taken:
Possible Reason Action
1. the defaultroute option was used, causing pppd to add a new default route that overrides the existing default route that was used to initiate the tunnel. remove defaultroute from the options given to pppd, and use other means to provide routes through the tunnel interface.
2. distribution specific or local interface-up scripts changed the route. change or remove the scripts so that they do not change the route in this manner.
3. the PPTP Server may have failed to provide an IP address, causing the new interface to have the same address as the default address on your host (compare "local IP address" in the logs, or the address shown by "ifconfig ppp0" with the address of your main network interface). add the noipdefault option.
4. the PPTP Server may have given its own IP address for the new interface (compare "remote IP address" in the debug logs with the IP address you give to pptp). try one of the following:
1. change the point-to-point IP address of the newly created ppp interface, using an ip-up or ip-pre-up script, for example;
#!/bin/sh
# $1: interface-name
# $4: local-IP-address
# delete the assigned address from the network device
ip addr del $4 dev $1
# add back the assigned address along with a replacement peer address
ip addr add $4 peer 10.0.0.1/32 dev $1
# add a default route, remove if not wanted
route add default $1
2. change the point-to-point IP address of the newly created ppp interface, using ifconfig, for example;
ifconfig ppp0 pointopoint 10.0.1.1
where 10.0.1.1 is the address to be adopted, see internal address for how to determine this.
3. add a static route to the PPTP Server via your usual default gateway, for example;
route add -host x.x.x.x/32 gw y.y.y.y dev nnn0
where x.x.x.x is the IP address of the PPTP Server, y.y.y.y is the IP address of your usual default gateway, and nnn0 is the name of the network interface through which the gateway is contacted.
4. request a more appropriate address by adding an option such as :10.0.1.1, where 10.0.1.1 is the address to be adopted, (the PPTP server may be configured to refuse the request, or may not be capable of it)
5. use the iptables and ip commands to direct the tunnel packets away from the tunnel interface, see our Routing HOWTO for more detail,
6. ask the PPTP Server administrator to change the configuration to use another remote address.
sa
http://pptpclient.sourceforge.net/howto-diagnosis.phtml#lots_of_data ali nemogu da promenim rute.
