Re: ipmasq_3.2.5 breaks nameserver lookups

[Greg Wooledge]

Curt Daugaard ([EMAIL PROTECTED]) wrote:

 The subject says it all.  I've gone through the docs, but
 since the out-of-the-box config at least appears to have
 broken a pretty average dialup ppp setup, I'm wondering
 if others have run into the same problem and would be
 willing to tell what fixed it.

The slink ipmasq package *would not* work for me.  I uninstalled it, and
then manually added the lines I wanted to the startup scripts:

case `uname -r` in
  2.1*|2.2.*)
echo 1 /proc/sys/net/ipv4/ip_forward
ipchains -P forward ACCEPT
ipchains -A forward -j MASQ -s 192.168.2.0/24 -d 0.0.0.0/0
;;
  2.0*)
ipfwadm -F -p deny
ipfwadm -F -a m -S 192.168.2.0/24 -D 0.0.0.0/0
;;
esac

(Not perfect, since the switch to ipchains isn't cleanly 2.1.*, but
this worked for the set of kernels I was using at the time)

-- 
Greg Wooledge| Truth belongs to everybody.
[EMAIL PROTECTED] |   Red Hot Chili Peppers,
http://www.kellnet.com/wooledge/ |


pgpIjzRH1EYh9.pgp
Description: PGP signature

ipmasq_3.2.5 breaks nameserver lookups

[Curt Daugaard]

The subject says it all.  I've gone through the docs, but
since the out-of-the-box config at least appears to have
broken a pretty average dialup ppp setup, I'm wondering
if others have run into the same problem and would be
willing to tell what fixed it.

Thanks.

Curt Daugaard
[EMAIL PROTECTED]

Re: ipmasq_3.2.5 breaks nameserver lookups--workaround

[Curt Daugaard]

The Slink version was the problem.  I installed the one from
Potato and the nameserver problem is fixed.

Curt

On Tue, Nov 02, 1999 at 06:56:35PM -0600, Curt Daugaard wrote:
 The subject says it all.  I've gone through the docs, but
 since the out-of-the-box config at least appears to have
 broken a pretty average dialup ppp setup, I'm wondering
 if others have run into the same problem and would be
 willing to tell what fixed it.
 
 Thanks.
 
 Curt Daugaard
 [EMAIL PROTECTED]
 
 
 -- 
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null