All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Walton <kj6eo@kj6eo.com>
To: LINUX HAMS MAILING LIST <linux-hams@vger.kernel.org>
Subject: Is there an "IPTABLES" expert on the list?
Date: Sun, 30 Mar 2003 18:10:30 -0800	[thread overview]
Message-ID: <3E87A396.6030105@kj6eo.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]

Hello List -

Is there an "IPTABLES" expert on the list?  I telnet to my TNOS box from 
a Windoze
box on my LAN.  After I replaced my "ipchains" firewall with a new 
"iptables" firewall
I can no longer telnet to my TNOS box using my terminal program "putty". 
 What is
interesting is that if I shell out to DOS on the Windoze box I can 
"ping" the TNOS
box and "telnet" to it using the DOS "telnet 44.16.2.100" command.  I 
have attached
two files "dos.output" and "putty.output".  Both of these files capture 
what is going on
when I try to telnet to my TNOS box via "dos" or "putty".  The files 
were captured
using the "tcpdump" command ie "tcpdump -tqn -i eth1 > <output filename>.

I can also make my firewall file available to you by request 
"rc.firewall".  Any help
you could offer would be appreciated.  For whatever reason I just can't 
telnet to
the TNOS box using "putty".  Maybe I can't see the forest for the trees?

FYI, I can use "putty" telnet to connect to any other 44 IP number.  I 
can also use
"putty" ssh to connect to any of my servers on the LAN.

Any suggestions?

Regards,

Bill Walton KJ6EO (kj6eo.ampr.org)(44.16.2.100)

[-- Attachment #2: dos.output --]
[-- Type: text/plain, Size: 385 bytes --]

192.168.1.12.1055 > 44.16.2.100.telnet: tcp 0 (DF)
44.16.2.100.telnet > 192.168.1.12.1055: tcp 115
192.168.1.12.1055 > 44.16.2.100.telnet: tcp 0 (DF)
192.168.1.12.1055 > 44.16.2.100.telnet: tcp 0 (DF)
44.16.2.100.telnet > 192.168.1.12.1055: tcp 7
192.168.1.12.1055 > 44.16.2.100.telnet: tcp 0 (DF)
arp who-has 192.168.1.12 tell 192.168.1.1
arp reply 192.168.1.12 is-at 0:40:5:8f:73:aa

[-- Attachment #3: putty.output --]
[-- Type: text/plain, Size: 299 bytes --]

192.168.1.12.1057 > 44.16.2.100.telnet: tcp 0 (DF)
44.16.2.100.telnet > 192.168.1.12.1057: tcp 115
192.168.1.12.1057 > 44.16.2.100.telnet: tcp 0 (DF)
192.168.1.12.1057 > 44.16.2.100.telnet: tcp 21 (DF)
44.16.2.100.telnet > 192.168.1.12.1057: tcp 7
192.168.1.12.1057 > 44.16.2.100.telnet: tcp 0 (DF)

             reply	other threads:[~2003-03-31  2:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-31  2:10 Bill Walton [this message]
2003-03-31  5:14 ` Is there an "IPTABLES" expert on the list? Robert L Cochran
2003-03-31 14:10 ` Jose A. Amador
2003-04-01  1:22 ` M Taylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E87A396.6030105@kj6eo.com \
    --to=kj6eo@kj6eo.com \
    --cc=linux-hams@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.