Date: Mon, 15 Oct 2001 09:08:21 +0100 From: "Steve Coles" <scoles@tripos.com> To: <freebsd-isdn@freebsd.org> Cc: "H. Eckert" <ripley@nostromo.in-berlin.de> Subject: Re: Configuring isdnd, isppp/isp0 and "surftime" Message-ID: <179801c15550$8ffa3a50$9e9814ac@tripos.com> References: <159e01c152fc$2cadabe0$9e9814ac@tripos.com> <20011013124507.A80441@server.nostromo.in-berlin.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for the script, I shall use this if you don't mind. FWIW I have had a successful weekend configuring and using i4b; other than warnings to Will Robinson ? My early concerns about isdnd strangely not liking isp being down were ~misguided~ and caused by this: I had external nameservers in resolve.conf I had hosts then bind in hosts.conf I allowed remote monitoring of isdnd from 192.168.254.0 isp0 was down I ran netstat -rn and all was OK a) I typed netstat -r and the command blocked looking up the name for the localnet 192.168.254.0 b) I typed isdnd -f -l0xFFF and it blocked too... I guessed from isdnd.log that the blocking netstat lookup for 192.168.254.0 and similar lookup in isdnd.rc for isdnmonitor were related. I added 192.168.254.0 to "networks" and both netstat -rn and isdnd stopped blocking when isp0 was down. (Incidentally, I had to add "192.168.254.0", not "192.168.254" to networks ?) Thanks for your help, Steve ----- Original Message ----- From: "H. Eckert" <ripley@nostromo.in-berlin.de> To: <freebsd-isdn@freebsd.org> Cc: "Steve Coles" <scoles> Sent: 13 October 2001 11:45 Subject: Re: Configuring isdnd, isppp/isp0 and "surftime" > Quoting Steve Coles (scoles@tripos.com): > > Q. Do I just need to schedule an "ifconfig isp0 down" and "ifconfig > > isp0 up" ? > > That's what I do to allow my server to have a 2 hour window for > automatic dialin to fetch mail and news. > I have to admit though, that I'm still running 3.5.x an therefore not > the most current i4b. > > For ease of use I wrote some simple scripts to invoke that even take > care to use the connection I want to open by checking the default route. > So I could have cron entries that reset the default route and don't have > to care about that when I run "isdn+" manually to enable the connection. > > =3D=3D=3D=3D8<=3D=3D=3D=3D isdn+ > #!/bin/sh > PATH=3D/usr/bin:/bin > interface=3D`netstat -rn | grep default| awk '{print $NF;}'` > /usr/local/bin/sudo /sbin/ifconfig $interface up > =3D=3D=3D=3D8<=3D=3D=3D=3D > > > Q. Does isdnd like the isp0 going up and down when it is running ? > > I have no problem at all with that. > > > Greetings, > Ripley > -- > H. Eckert, 12051 Berlin > ISO 8859-1: =C4=3DAe, =D6=3DOe, =DC=3DUe, =E4=3Dae, =F6=3Doe, =FC=3Due,= =DF=3Dsz. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?179801c15550$8ffa3a50$9e9814ac>