Re: Diald problems ... continued ...
On Saturday 23 Nov 2002 1:47 pm, John Hasler wrote: Dave Selby writes: Unfortunately pppds demand dialling doesnt work very well with dynamic IP addresses alloctaion. It's working fine here. It will dial up but then says it cand find the URL, you click OK, re-request the URL while the link is up and it will work fine. This happens every time it dials up. I think this is happening because the DNS lookup is timing out before the connection comes up. It has nothing to do with dynamic IP. I think that you will have the same problem with diald. If you don't, please let me know: I have the same problem. Ive done some digging, and found out some info DIALD does indeed have the same problem as discussed, but on the diald website I found this in the FAQ section ** 6.11 I'm using dynamic addresses, and the first TCP session over a line always freezes. If your IP address is assigned dynamically when the connection comes up, then any TCP session that brings the link up will still be trying to use the IP address assigned to your machine by diald before the connection came up. The TCP protocol does not allow for active TCP sessions that move from one address to another. This really requires support for some kind of mobile TCP protocol. Both you and your provider would have to cooperate for this to work. This problem is not likely to go away in the near future. It would be much easier to get a static address. As a work around, you should avoid make TCP connections directly to a known IP address. This means your /etc/hosts file must not contain the IP addresses of any machines other than your local machine(s), and you should not be running named in such a way that it can pick up external addresses (which as near as I can tell means you must not run named). Also, making a connection by giving a numeric address, e.g. telnet 123.100.2.1 will fail. The point of this exercise is to bring the diald link up with a nameserver query rather than a TCP session start. Once the link comes up the nameserver query will be resolved, and the TCP session will be started with the correct (dynamically assigned) address. * My experience of pppd having this problem was on an old red hat system, which is why I was trying to get diald going on debian !! I will now pay my attention to pppd dial on demand for debian !!! it seems easier to configure, then follow the above ... Its one BIG LEARNING CURVE !!! dave PS if you have any sucsess with the above, please let me know, I will do likewise. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Diald problems ... continued ...
On Thursday 21 Nov 2002 11:49 pm, John Hasler wrote: Dave Selby writes: BUT I cant get diald to work ! Is there some reason why you can't use pppd's demand dialing option? You can configure it via pppconfig. Any help much appreciated You haven't given us enough information. Unfortunately pppds demand dialling doesnt work very well with dynamic IP addresses alloctaion. It will dial up but then says it cand find the URL, you click OK, re-request the URL while the link is up and it will work fine. This happens every time it dials up. More information .. yep I was a bit light on that front !!! here goes !!! Using Woody, pretty standard setup. Want to use diald to dial my isp, NTL, with dynamicle allocated IPs, when needs be, just for my computer, no network connected !! I am using a win-modem, YUK !! however I have a driver and it appears to work OK, I configured wvdial OK, internet works, using /dev/modem, actualy points to /dev/ham I have read the 'man diald-examples' and setup a /etc/diald/diald.options file containing .. mode ppp device /dev/modem connect /etc/diald/connect speed 57600 modem lock crtscts local 192.168.0.1 remote 192.168.0.2 dynamic defaultroute include /etc/diald/standard.filter I have configured /etc/diald/connect as ... ** DEBUG=-v # The initialization string for your modem MODEM_INIT=ATZ # The phone number to dial PHONE_NUMBER=126308005190100 # If the remote system calls you back, set to 1; otherwise leave to 0. CALLBACK=0 # If you authentify using PAP or CHAP (that is let pppd handle the # authentification, set this to 0. AUTHENTIFY=0 # The chat sequence to recognize that the remote system # is asking for your user name. USER_CHAT_SEQ=name:--name:--name:--name:--name:--name:--name: # The string to send in response to the request for your user name. USER_NAME=X # The chat sequence to recongnize that the remote system # is asking for your password. PASSWD_CHAT_SEQ=word: # The string to send in response to the request for your password. PASSWORD=X # The prompt the remote system will give once you are logged in # If you do not define this then the script will assume that # there is no command to be issued to start up the remote protocol. PROMPT=annex: # The command to issue to start up the remote protocol PROTOCOL_START=ppp # The string to wait for to see that the protocol on the remote : I restart diald /etc/init.d/diald restart I ask konquerer to access lycos.co.uk And the following happens The modem relay clicks once I get all sorts of informantion in /var/log/messages and /var/log/syslog, both attatched. It don't work !!! About every 30 secs it re-clicks. I tried to trace the output of the -v debug, I found it once then re-lost it!! however it said that the modem failed to initilise, part of connect script # Initialize the modem. Usually this just resets it. message Initializing Modem chat $DEBUG TIMEOUT 5 OK-AT-OK $MODEM_INIT TIMEOUT 45 OK if [ $? != 0 ]; then message Failed to initialize modem exit 1 Any help greatly appreciated Still a bit of a linux newbe !! Nov 23 06:55:41 debian pppd[593]: Modem hangup Nov 23 06:55:41 debian pppd[593]: Connection terminated. Nov 23 06:55:41 debian pppd[593]: Using interface ppp0 Nov 23 06:55:41 debian pppd[593]: Connect: ppp0 -- /dev/pts/4 Nov 23 06:55:41 debian pppd[593]: Modem hangup Nov 23 06:55:41 debian pppd[593]: Connection terminated. Nov 23 06:55:41 debian pppd[593]: Using interface ppp0 Nov 23 06:55:41 debian pppd[593]: Connect: ppp0 -- /dev/pts/4 Nov 23 06:55:41 debian pppd[593]: Modem hangup Nov 23 06:55:41 debian pppd[593]: Connection terminated. Nov 23 06:55:41 debian pppd[593]: Exit. Nov 23 06:55:41 debian diald[183]: start sl0: SIOCSIFMETRIC: Operation not supported Nov 23 06:55:41 debian diald[183]: start sl0: SIOCADDRT: File exists Nov 23 06:55:41 debian diald[183]: start sl0: SIOCDELRT: No such process Nov 23 06:55:41 debian diald[183]: start sl0: SIOCADDRT: File exists Nov 23 06:55:41 debian diald[183]: Disconnected. Call duration 0 seconds. Nov 23 06:55:41 debian diald[183]: IP transmitted 0 bytes and received 0 bytes. Nov 23 06:55:41 debian diald[183]: Closing /dev/modem Nov 23 06:55:42 debian diald[183]: Delaying 30 seconds before clear to dial. Nov 23 06:56:13 debian diald[183]: Calling site 192.168.0.2 Nov 23 06:56:14 debian diald[183]: Connected to site 192.168.0.2 Nov 23 06:56:14 debian diald[183]: Running pppd (pid = 650). Nov 23 06:56:14 debian pppd[650]: pppd 2.4.1 started by root, uid 0 Nov 23 06:56:14 debian pppd[650]: Using interface ppp0 Nov 23 06:56:14 debian pppd[650]: Connect: ppp0 -- /dev/pts/4 Nov 23 06:56:15 debian pppd[650]: Modem hangup Nov 23 06:56:15 debian pppd[650]: Connection terminated. Nov 23 06:56:15 debian pppd[650]: Using interface ppp0 Nov 23 06:56:15 debian
Re: Diald problems ... continued ...
Dave Selby writes: Unfortunately pppds demand dialling doesnt work very well with dynamic IP addresses alloctaion. It's working fine here. It will dial up but then says it cand find the URL, you click OK, re-request the URL while the link is up and it will work fine. This happens every time it dials up. I think this is happening because the DNS lookup is timing out before the connection comes up. It has nothing to do with dynamic IP. I think that you will have the same problem with diald. If you don't, please let me know: I have the same problem. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Diald problems ... continued ...
On Saturday 23 Nov 2002 1:47 pm, John Hasler wrote: Dave Selby writes: Unfortunately pppds demand dialling doesnt work very well with dynamic IP addresses alloctaion. It's working fine here. It will dial up but then says it cand find the URL, you click OK, re-request the URL while the link is up and it will work fine. This happens every time it dials up. I think this is happening because the DNS lookup is timing out before the connection comes up. It has nothing to do with dynamic IP. I think that you will have the same problem with diald. If you don't, please let me know: I have the same problem. Ive done some digging, and found out some info DIALD does indeed have the same problem as discussed, but on the diald website I found this in the FAQ section ** 6.11 I'm using dynamic addresses, and the first TCP session over a line always freezes. If your IP address is assigned dynamically when the connection comes up, then any TCP session that brings the link up will still be trying to use the IP address assigned to your machine by diald before the connection came up. The TCP protocol does not allow for active TCP sessions that move from one address to another. This really requires support for some kind of mobile TCP protocol. Both you and your provider would have to cooperate for this to work. This problem is not likely to go away in the near future. It would be much easier to get a static address. As a work around, you should avoid make TCP connections directly to a known IP address. This means your /etc/hosts file must not contain the IP addresses of any machines other than your local machine(s), and you should not be running named in such a way that it can pick up external addresses (which as near as I can tell means you must not run named). Also, making a connection by giving a numeric address, e.g. telnet 123.100.2.1 will fail. The point of this exercise is to bring the diald link up with a nameserver query rather than a TCP session start. Once the link comes up the nameserver query will be resolved, and the TCP session will be started with the correct (dynamically assigned) address. * My experience of pppd having this problem was on an old red hat system, which is why I was trying to get diald going on debian !! I will now pay my attention to pppd dial on demand for debian !!! it seems easier to configure, then follow the above ... Its one BIG LEARNING CURVE !!! dave PS if you have any sucsess with the above, please let me know, I will do likewise. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
