Many thanks to the kind folk that replied to my routing problem (see below
for original).  The simplest solution was that I had put 0.0.0.0 as both
local and remote host with dynamic assignment so I replaced these with
192.168.0.1 and 192.168.0.2, which are not used in my hausnet.  This cured
the problem - I remember seeing somewhere (as you do!) that 0.0.0.0 wasn't
a good idea but it worked under normal ppp.  So many thanks to Michael
Doerner and Dmitry Pogosyan for the simplest solution.

The add route suggestion from Ben Johnson was my next port of call and no
doubt enables finer control.

Clearly it is not a good idea to have stuff in the diald.conf file that is
in the ppp options file but in practice I am not diald-ing until I have
all the filtering and stuff set up to avoid excessing connecting (don't
forget we pay by the second for connection time).  Since it doesn't do any
harm, I'll leave it.  Thanks to Wookey for the thought anyway.

Now I will get down to understanding IP masquerading and firewalling so
that by next millenium I will have either a brain the size of a planet or
have gone even more ga-ga than I am already.  Oh - we are nearly at the
next millenium - I hadn't noticed.  I had better get a move on!

Thanks also to anyone I have not mentioned or whose message hadn't reached
me yet!

John

On Mon, 8 Nov 1999, John Logsdon wrote:

> Hi
> 
> Having just finished a major non-computing problem, I am turning my mind
> to trying to get demand dialing and network access from the hausnet before
> my family kill me.
> 
> Setup: RH5.2 2.0.36 kernel, ppp 2.3.5-1, diald 0.16.5a-1
> 
> >From some previous postings and advice received, I have decided not to use
> pppd demand dial because I do want to have a bit more policing of when my
> offspring are netting and, more importantly I gather there are problems
> with the version of ppp I have.  I did copy down 2.3.10-1 but that came
> with a patch file that didn't seem to work and anyway I can get the demand
> dialing bit done by diald.  The palaver of compiling ppp, rebuilding the
> kernel and then hoping everything would work in the end was too much.
> 
> Here is my very brief ppp options file:
> 
> defaultroute
> noipdefault
> modem
> /dev/modem
> 115200
> crtscts
> debug
> passive
> asyncmap 0
> name "j.logsdon"
> 
> and here is the diald.conf file (it helped enormously when I realised it
> was the /etc/diald.conf that needed to be modified, not the
> /etc/diald/diald.conf.  
> 
> accept any 420 any
> device /dev/modem
> speed 115200
> mode ppp
> dynamic
> local 0.0.0.0
> remote 0.0.0.0
> up-delay 5
> defaultroute
> modem
> crtscts
> connect "/usr/sbin/chat -f /etc/ppp/pppscript"
> redial-timeout 10
> fifo /etc/diald/diald.ctl
> 
> The present problem I have is that once I execute diald and ping something
> to force a connection, my network hangs.  So it is a routing problem.  
> Here is the route table before diald:
> 
> Kernel IP routing table
> Destination   Gateway Genmask         Flags Metric Ref   Use   Iface
> 192.168.1.0   *       255.255.255.0   U     0      0    5502   eth0
> 127.0.0.0     *           255.0.0.0   U     0      0    2512   lo
> 
> The after diald is executed but before a ping the network is still OK
> with the routing table:
> 
> Kernel IP routing table
> Destination   Gateway Genmask         Flags Metric Ref    Use   Iface
> default       *       255.255.255.255 UH    1      0        0   sl0
> 192.168.1.0   *       255.255.255.0   U     0      0     5502   eth0
> 127.0.0.0     *       255.0.0.0       U     0      0     2512   lo
> default       *       0.0.0.0         U     1      0        0   sl0
> 
> 
> And now when I have done a ping to force ppp up, the network hangs
> (specifically the xterms off the server on another machine freeze
> completely) with routing table:
> 
> Kernel IP routing table
> Destination   Gateway Genmask         Flags Metric Ref    Use  Iface
> default       *       255.255.255.255 UH    1      0        0  sl0
> locke.zen.co.uk *     255.255.255.255 UH    0      0        0  ppp0
> 192.168.1.0   *       255.255.255.0   U     0      0     5504  eth0
> 127.0.0.0     *       255.0.0.0       U     0      0     2514  lo
> default       *       0.0.0.0         U     0      0        2  ppp0
> default       *       0.0.0.0         U     1      0        2  sl0
> 
> Any ideas what is up and what additional commands I should be adding to
> diald?
> 
> TIA 
> 
> John
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-diald" in
> the body of a message to [EMAIL PROTECTED]
> 


-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]

Reply via email to