From: "Tyler Littlefield" <compgeek13@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: iptables questions
Date: Wed, 12 Jul 2006 16:12:52 -0600 [thread overview]
Message-ID: <002e01c6a600$5334ae10$6501a8c0@gramdmasfury> (raw)
In-Reply-To: <20060712205622.GA9603@localhost.localdomain>
OK.
With a router set to static, and the IP as 10. That tells me its the isp
doing it. especially when the gateway is also a 10 address.
~~TheCreator~~
website:
http://tysplace.shaned.net
msn:
compgeek134@hotmail.com
aim:
st8amnd2005
skype:
st8amnd127
moo coder/wizard and administrator
----- Original Message -----
From: "Gregory Nowak" <greg@romuald.net.eu.org>
To: <jheim@math.wisc.edu>; "Speakup is a screen review system for Linux."
<speakup@braille.uwo.ca>
Sent: Wednesday, July 12, 2006 2:56 PM
Subject: Re: iptables questions
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Wed, Jul 12, 2006 at 07:46:34PM -0500, John Heim wrote:
> > Lots of
> > ISPs block some ports so you can't set up your own smtp server, for
> > example. Maybe Tyler's ISP blocks all incoming connections by default
> > and allows only outgoing and existing connections.
> >
>
> I know, my former ISP blocked outgoing smtp, and what's even worse is
> that when they out-sourced their tech support, those people insisted
> that they didn't block any ports. I also have a friend who has some
> incoming ports blocked as well, so I'm familiar with the port blocking
> problem, though I've never heard those situations described as
> public or private ip addressing.
>
> > I can't believe an ISP would hand out 10.0.0/24 addresses. Hand out
> > private IP addresses and do NAT for every customer? Impossible (I
> > think). It may even be illegal.
> >
>
> I agree totally. However, Tyler insisted on several occasions in private
> messages that his ISP handed out 10.0.0/24 addresses to him, and I
> repeatedly kept telling him that it was either his modem or router
> that was doing that. As you said, for an ISP to be doing NAT for all
> its customers would be more costly then having a pool of dynamic
> public IPS to hand out.
>
> Greg
>
>
> - --
> web site: http://www.romuald.net.eu.org
> gpg public key: http://www.romuald.net.eu.org/pubkey.asc
> skype: gregn1
> (authorization required, add me to your contacts list first)
>
> - --
> Free domains: http://www.eu.org/ or mail dns-manager@EU.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
>
> iD8DBQFEtWH27s9z/XlyUyARAuQ9AJ0bd/+uhKph27XpWxKiOEX/dQUGOgCgkVLm
> 1DAtvLZe8hNyd6EX4QzAmq4=
> =E+fP
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
Tyler Littlefield
` Gregory Nowak
` Tyler Littlefield
` Alex Snow
` Gregory Nowak
` Tyler Littlefield
` Gregory Nowak
` Tyler Littlefield
` John Heim
` Tyler Littlefield
` Gregory Nowak
` Tyler Littlefield [this message]
` Willem van der Walt
-- strict thread matches above, loose matches on Subject: below --
IPTABLES QUESTIONS Doug Lawlor
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='002e01c6a600$5334ae10$6501a8c0@gramdmasfury' \
--to=compgeek13@gmail.com \
--cc=speakup@braille.uwo.ca \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).