> That's LANIC IP space, not RIPE. Though RIPE should have
> pointed you to LANIC, IMO, they don't.
With RIPE one is doing well to get anything at all.
> They show what you
> see for any IP space that isn't under their control. I'd
> recommend starting your searches with ARIN, as they'll
On 8/23/06, beno <[EMAIL PROTECTED]> wrote:
Since I'm here at said café, this is my
current address:
*200.88.97.128
*I went to ripe.net and searched it, but that didn't provide anything
interesting that I could see. It says "Allocated Unspecified" and "This
country is really worldwide." Any idea
Hi;
Now that my initial pf.conf file is all but completed, I still need (or,
want) to block out all the world from SSH access except myself. However,
I still need to get the IP addresses from the Internet café I
occasionally use (like right now), who gets them from Verizon here in
the Dominica
Michal Mertl wrote:
beno wrote:
Michal Mertl wrote:
Note that no quoting is necessary here and the parser doesn't care much
about whitespace. If you run pfctl with "-v" you shall see the macro
expansion which should help in understanding the parser and finding out
errors.
That
> set fingerprints /etc/pf.os
> pfctl: /etc/pf.os : No such file or directory
I wonder if the parser sees the second space and assumes that is part of
the filename. I didn't test, but try removing the extra space before the
pathname.
> /etc/pf.conf:24: syntax error
> Here's that line, which t
beno wrote:
> Michal Mertl wrote:
> > Note that no quoting is necessary here and the parser doesn't care much
> > about whitespace. If you run pfctl with "-v" you shall see the macro
> > expansion which should help in understanding the parser and finding out
> > errors.
> >
> That does help! Tha
Michal Mertl wrote:
Note that no quoting is necessary here and the parser doesn't care much
about whitespace. If you run pfctl with "-v" you shall see the macro
expansion which should help in understanding the parser and finding out
errors.
That does help! Thanks! Now, throwing that flag with
Jon Simola wrote:
> On 8/22/06, beno <[EMAIL PROTECTED]> wrote:
> > This is accepted by the pfclt compiler just fine:
> >
> > http_ports="80 8080 7080"
> > ssh_ports="22"
> > ftp_ports="21 8021 7021"
> > smtp_ports="25"
> > pop3_ports="110"
> > https_ports="443"
> > imap_ssl_ports="993 143"
> > squ
