Date: Fri, 31 Mar 2000 00:05:20 +0200 From: "D. Rock" <rock@dead-end.net> To: Andreas Klemm <andreas@klemm.gtn.com> Cc: isdn@freebsd.org Subject: Re: problems with right sppp settings in rc.conf ??? Message-ID: <38E3CFA0.1909F37C@dead-end.net> References: <20000326234139.A31884@titan.klemm.gtn.com> <38DFB772.E98D7544@dead-end.net> <20000329081744.A23298@titan.klemm.gtn.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Andreas Klemm wrote: > > On Mon, Mar 27, 2000 at 09:33:06PM +0200, D. Rock wrote: > > I'm curious why user level ppp isn't propagated more in this mailing list. > > > > Ok, it's only available since 3.3 (?) but after I switched over to it from > > sppp setup I don't want to miss it again. > > > > Here are excerpts from my configuration: > > Thanks for the good examplem but I didn't get ti to work. > isdnd didn't dial. My filter rules loaded in my example are very aggressive. ping doesn't build up a connection. DNS traffic won't either. This were my preferences based on unwanted connections (a complete long weekend, Thursday - Sunday, nonstop online. You know what this means here in Germany). You therefor won't be able to build up a connection with a "telnet somehost" or http://somewhere.com/, because it first would require a DNS lookup. So you can build up some connection by IP-Address. I usually build up a connection, if the destination host is already cached in my name server. But mostly I just first fetch new mail, which uses an IP-Address, no DNS name. Then I usually can surf the web. You can also remove in my filter rules the two lines marked with # Kein DNS or you can disable filtering altogether by commenting out load filters all in /etc/ppp/ppp.conf You may be able to safely remove the DNS filters (see above), if you know what is running on your machine and doesn't generate DNS lookups (by having a good layout in /etc/hosts and using this file before DNS [/etc/host.conf] or [as in my case] running your own name server with your own private DNS domain). My problem mentioned above (a whole weekend online) was caused after installing the squid proxy server which seems to check its own name cache periodically. Maybe I forgot to mention some configuration details, but I cannot find any. All /etc/rc* files are uncustomized, the only modifications were made in /etc/rc.conf /etc/ppp/ppp.conf /etc/isdn/isdnd.rc Just for completeness. You can check if your configuration seems similar: # ifconfig -a fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 172.23.7.126 netmask 0xffffff00 broadcast 172.23.7.255 ether 00:a0:c9:ef:69:8d media: autoselect (100baseTX) status: active supported media: autoselect 100baseTX <full-duplex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 inet 127.0.0.1 netmask 0xff000000 isp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500 tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500 inet 62.156.55.138 --> 212.185.253.237 netmask 0xffffffff Opened by PID 249 # netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 212.185.253.237 UGSc 2 36257 tun0 127.0.0.1 127.0.0.1 UH 1 4679 lo0 172.23.7/24 link#1 UC 0 0 fxp0 => 172.23.7.1 0:a0:c9:ef:99:4e UHLW 11 526139 fxp0 1022 172.23.7.255 ff:ff:ff:ff:ff:ff UHLWb 0 354 fxp0 212.185.253.237 62.156.55.138 UH 2 0 tun0 224/4 link#1 UCS 0 0 fxp0 => [212.185.253.237 was the last remote address assigned by PPP] And, after a tip from another used, I added another file which solved my problem with persistent old IP information in the tunnel interface: /etc/ppp/ppp.linkdown t-online: iface clear -- Daniel 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?38E3CFA0.1909F37C>