RE: Two questions

From: Schneider, Tim <SCHNEIDER_at_no.spam.please>
Date: Wed Jun 16 1999 - 11:37:08 CST

I had nothing but trouble telneting into a linux box from win95 once I had
setup firewalling (this was with a Slakware 2.0.30 kernel) then I got
QVT/Term from and it works great. That
was when I stopped troubleshooting telnet.

one thing you could try is telneting into both ip addresses for the
firewall. You may be able to telnet into the 192.168.x.x address but not
the "real world" IP address.

> ----------
> From: Les Klassen Hamm
> Sent: Monday, June 14, 1999 9:42 PM
> To: SLG
> Subject: Two questions
> Greetings all,
> I have two questions - I don't know if they are related or not.
> Background:
> I have two computers, networked together, and I can ping, ftp, telnet,
> http and all works well. One is a linux box (pingu) and the other dual
> boots linux/win98 (chimay).
> Question 1:
> As soon as I set up IP-masquerading on pingu (2.2.x kernel, using
> IPChains),
> the IP masq'ing works well (ie the win98 box can use it and browse the
> net), but then a telnet or ftp from chimay pauses for what I guess is a
> timeout before giving me a prompt (at least a minute). This is true even
> when both boxes are running linux. My /etc/hosts on both boxes list
> themselves and the other box (this is a frequent answer to this very FAQ
> on
> the net), so that is not the problem. (Yes, /etc/host.conf has order
> hosts,
> bind.) If it were the problem, the delay should exist before IPmasq'ing,
> no? Why does the ipchaining create the need for DNS lookups, if indeed
> that is what is happening. My IPchain set is minimal and simple - for
> testing now it is only:
> /sbin/modprobe ip_masq_ftp
> echo "1" > /proc/sys/net/ipv4/ip_dynaddr
> /sbin/ipchains -M -S 7200 10 60
> /sbin/ipchains -P forward DENY
> /sbin/ipchains -A forward -s -j MASQ
> Any ideas?
> PS This constant lookup means that diald is trying to dial out even for
> local telnets and ftp's between machines in my basement!!
> Question 2:
> DIALD! Has anyone got diald running happily with a 2.2.x kernel? It wants
> ethertap devices - I MAY have that part figured out. But dial-outs keep
> dying saying that:
> Jun 14 21:19:03 pingu pppd[779]: Device ttyS1 is locked by pid 742
> pid 742 is the diald process
> I read the man page - it says to insure that "lock" is removed from
> /etc/ppp/options, because diald will take care of all of that. So who's
> lock is bugging who here? I take it pppd is complaining because diald
> already locked the port, but I haven't told pppd to try locking it. Is
> there a command elsewhere that is telling pppd to lock the port. I just
> used /sbin/ifup ppp0 to initiate the connection (this works from the
> command line if diald isn't running).
> Ideas?
> Thanks much for any help!!
> Les...
> -
> Saskatoon Linux Group Mailing List.
> -
> To unsubscribe, send mail to
> '' with
> 'unsubscribe' in the body.

Saskatoon Linux Group Mailing List.
To unsubscribe, send mail to
'' with
'unsubscribe' in the body.

Received on Wed Jun 16 11:37:08 1999

This archive was generated by hypermail 2.1.8 : Sun Jan 09 2005 - 13:53:59 CST