mpson
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> Ray Olszewski
> Sent: Wednesday, March 13, 2002 3:49 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [Leaf-user] DCD Port forwarding not working
>
>
> At 05:14 PM 3/13/02
At 05:14 PM 3/13/02 -0600, guitarlynn wrote:
>On Wednesday 13 March 2002 12:45, Doug Sampson wrote:
>
>> I still can't access the web server via
>> http://www.cybersampson.com!!! #$%#!&
>
>It works now from my house!
And from mine as well. But it didn't before when I tried, so you did fix
someth
On Wednesday 13 March 2002 12:45, Doug Sampson wrote:
> I still can't access the web server via
> http://www.cybersampson.com!!! #$%#!&
It works now from my house!
--
~Lynn Avants
aka Guitarlynn
guitarlynn at users.sourceforge.net
http://leaf.sourceforge.net
If linux isn't the answer, you've
Doug Sampson wrote:
[snip]
> I still can't access the web server via http://www.cybersampson.com!!!
> #$%#!&
>
> I'm beginning to think it's the web server that is denying access. I'm
That web address is having problems. Apparently www2.cybersampson.com
does not work at this time.
Regards,
At 10:45 AM 3/13/02 -0800, Doug Sampson wrote:
[...]
>I still can't access the web server via http://www.cybersampson.com!!!
>#$%#!&
>
>I'm beginning to think it's the web server that is denying access. I'm
>thinking that the web server does accept requests from the private network
>but is *someh
> If I understand the setup right, you are referring here to
> hosts.allow and
> hosts.deny on the LEAF router. But the actual Web server runs
> on a different
> host, on its port 80, and gets (or is supposed to get, once everything
> works) traffic forwarded from port 8080 on the LEAF router's
At 09:29 PM 3/12/02 -0800, Doug Sampson wrote:
>I just thought of something else. If there wasn't any entry in the
>/etc/hosts.allow file for web access (i.e., in.www:ALL; in:8080:ALL), would
>this stop any incoming traffic from coming in? I am using the default
>/etc/hosts.deny file (ALL:PARANO
I just thought of something else. If there wasn't any entry in the
/etc/hosts.allow file for web access (i.e., in.www:ALL; in:8080:ALL), would
this stop any incoming traffic from coming in? I am using the default
/etc/hosts.deny file (ALL:PARANOID; ALL:ALL in that order).
Does this shed any lig
On Tuesday 12 March 2002 10:18, Doug Sampson wrote:
> > I don't know exactly how eth0 is supposed to come up and be
> > configured when running PPPoE, which is what I am assuming
> > you using with this config. If your not running PPPoE, you need
> > to fix the general config before it will work.
> I don't know exactly how eth0 is supposed to come up and be
> configured when running PPPoE, which is what I am assuming
> you using with this config. If your not running PPPoE, you need
> to fix the general config before it will work.
>
Am running dhclient on eth0 that is connected 7/24 to c
On Monday 11 March 2002 22:53, Doug Sampson wrote:
> Yes, that would be a big help! I'm extremely frustrated by the fact
> there doesn't seem to be a hole opened at port 8080... Or is it
> there and I didn't see it?
It's there, but I think you've got the port forwarding somewhat
confused. Detai
cbq bandwidth $BNDWIDTH rate $IARATE maxburst $IABURST \
allot $PXMTU avpkt 1000 bounded isolated weight 1 \
prio 2 split $HNDL:0 defmap 80
tc qdisc add dev $1 parent $HNDL:2 sfq perturb 15
# Priority class
tc class add dev $1 parent
> > I would be happier knowing what it says rather than what it
> > "essentially"
> > says. Also what "it" is (what browser is reporting the
> > error). From here,
> > Netscape (on Win95) gets the right translated address from
> > DynDNS, but times
> > out with its standard "The server is not resp
> I would be happier knowing what it says rather than what it
> "essentially"
> says. Also what "it" is (what browser is reporting the
> error). From here,
> Netscape (on Win95) gets the right translated address from
> DynDNS, but times
> out with its standard "The server is not responding ..." me
At 02:44 PM 3/9/02 -0800, Doug Sampson wrote:
>Hi all,
>
>I'm still having a problem with port forwarding packets to the internal web
>server... I am on a Cox network that supposedly blocks packets coming inward
>via port 80. I've set up an account with DynDNS that forwards packets
>directed at
15 matches
Mail list logo
