On Tue, Feb 15, 2011 at 11:48:53AM +0200, Andrei Popescu wrote:
> On Lu, 14 feb 11, 18:34:01, Mike McClain wrote:
> > >From this I take it you think ecn should be set to 1?
>
> http://www.frozentux.net/ipsysctl-tutorial/chunkyhtml/tcpvariables.html
Thanks Andrei, I'll take a look.
Mike
--
Satis
On Lu, 14 feb 11, 18:34:01, Mike McClain wrote:
> On Sun, Feb 13, 2011 at 12:49:13PM +0200, Andrei Popescu wrote:
> > According to a quick search seems to imply that a firewall or a router
> > along the way is the culprit. If you are lucky it's the router and a
> > firmware upgrade might solve th
On Sun, Feb 13, 2011 at 12:49:13PM +0200, Andrei Popescu wrote:
> According to a quick search seems to imply that a firewall or a router
> along the way is the culprit. If you are lucky it's the router and a
> firmware upgrade might solve the problem.
>From this I take it you think ecn should b
On Sun, Feb 13, 2011 at 02:18:37AM -0600, Boyd Stephen Smith Jr. wrote:
>
> To get this done automatically at boot, edit /etc/sysctl.conf and add the
> line:
> net.ipv4.tcp_ecn = 0
Done and thank you,
Mike
--
Satisfied user of Linux since 1997.
O< ascii ribbon campaign - stop html mail - www.a
To recap:
It started with me thinking I had a problem with my routing table.
The setup is like so:
cox cable-NetGear routerWindows box
\--Debian box
I can access the windows box through the router via smbclient.
Even with IPtables that ar
On Sb, 12 feb 11, 23:04:59, Mike McClain wrote:
>
> root@/deb40a:~> echo 0 > /proc/sys/net/ipv4/tcp_ecn
> now fetchmail works and I can get urls in firefox
According to a quick search seems to imply that a firewall or a router
along the way is the culprit. If you are lucky it's the router an
In <20110213070459.GA4674@playground>, Mike McClain wrote:
>root@/deb40a:~> echo 0 > /proc/sys/net/ipv4/tcp_ecn
>now fetchmail works and I can get urls in firefox
To get this done automatically at boot, edit /etc/sysctl.conf and add the
line:
net.ipv4.tcp_ecn = 0
--
Boyd Stephen Smith Jr.
On Sat, Feb 12, 2011 at 12:45:39PM +0100, Pascal Hambourg wrote:
>
> At this point, I have two ideas : either a problem with TCP connections
> or specifically with HTTP connections. I would first try to connect to
> other TCP-based services such as SMTP, POP3, FTP... If it fails too,
> then the p
On Fri, 11 Feb 2011 19:16:56 -0800, Mike McClain wrote:
> On Thu, Feb 10, 2011 at 12:57:17PM +, Camale?n wrote:
>>
>> Some cable providers (at least in Spain) tweak their cable modems to
>> allow only one computer to browse the web (by means of "filters" that
>> restrict the access to only on
Andrei Popescu a écrit :
> On Vi, 11 feb 11, 19:20:40, Mike McClain wrote:
>> root@/deb40a:~> wget -v google.com
>> --16:28:14-- http://google.com/
>>=> `google.com/index.html'
>> Resolving google.com... 74.125.227.20, 74.125.227.16, 74.125.227.17, ...
>> Connecting to google.com[74.12
On Vi, 11 feb 11, 19:20:40, Mike McClain wrote:
> On Thu, Feb 10, 2011 at 09:02:32PM +0200, Andrei Popescu wrote:
> > On Jo, 10 feb 11, 10:12:30, Mike McClain wrote:
> > > I've done something to keep browsers that connect just fine via ppp
> > > from connecting via eth0.
> > > Thoughts?
> >
> > No
On Thu, Feb 10, 2011 at 09:02:32PM +0200, Andrei Popescu wrote:
> On Jo, 10 feb 11, 10:12:30, Mike McClain wrote:
> > I've done something to keep browsers that connect just fine via ppp
> > from connecting via eth0.
> > Thoughts?
>
> No, but maybe the output of 'host google.com' and 'wget google.c
On Thu, Feb 10, 2011 at 12:57:17PM +, Camale?n wrote:
>
> Some cable providers (at least in Spain) tweak their cable modems to
> allow only one computer to browse the web (by means of "filters" that
> restrict the access to only one MAC address). To avoid this, there are
> routers that can
On Thu, Feb 10, 2011 at 08:06:07PM +0100, Pascal Hambourg wrote:
> Mike McClain a ?crit :
> >
> > I've done something to keep browsers that connect just fine via ppp
> > from connecting via eth0.
> > Thoughts?
>
> An HTTP proxy setting ?
> That was rather common with dialup connections.
I had to
On Fri, Feb 11, 2011 at 09:51:48AM +, Chris Davies wrote:
> Mike McClain wrote:
> > I've done something to keep browsers that connect just fine via ppp
> > from connecting via eth0.
>
> File > Work offline (or the equivalent) isn't set, is it?
> Chris
No but thanks for the thought.
Mike
--
Mike McClain wrote:
> I've done something to keep browsers that connect just fine via ppp
> from connecting via eth0.
File > Work offline (or the equivalent) isn't set, is it?
Chris
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Cont
Mike McClain a écrit :
>
> I've done something to keep browsers that connect just fine via ppp
> from connecting via eth0.
> Thoughts?
An HTTP proxy setting ?
That was rather common with dialup connections.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "un
On Jo, 10 feb 11, 10:12:30, Mike McClain wrote:
> I've done something to keep browsers that connect just fine via ppp
> from connecting via eth0.
> Thoughts?
No, but maybe the output of 'host google.com' and 'wget google.com' can
help diagnose.
Regards,
Andrei
--
Offtopic discussions among Debi
On Thu, Feb 10, 2011 at 12:32:42PM +0200, Andrei Popescu wrote:
> On Mi, 09 feb 11, 15:27:48, Mike McClain wrote:
>
> [snip]
>
> Here is what I'd do to try troubleshooting this:
> - ping some IP on the internet (8.8.8.8 is one of Google's DNS servers)
> If all this works try 'ping google.com' to
On Thu, Feb 10, 2011 at 10:21:16AM +0100, Pascal Hambourg wrote:
> Hello,
>
> Mike McClain a ?crit :
> >
> > I can access the windows box through the router via smbclient.
> > Even with IPtables that are ACCEPT, ACCEPT, ACCEPT, ... neither lynx
> > or Firefox can access the inet though they c
On Wed, 09 Feb 2011 15:27:48 -0800, Mike McClain wrote:
(...)
> Windows has no problem but the Debian box can still only see the net
> via the phone modem and dialup.
(...)
Just an additional note on this.
Some cable providers (at least in Spain) tweak their cable modems to
allow only on
On Mi, 09 feb 11, 15:27:48, Mike McClain wrote:
[snip]
Here is what I'd do to try troubleshooting this:
- ping internal ip of the router (192.168.1.1)
- ping external ip of the router (you find it somewhere in its status
page)
- ping the router's default gateway and its DNS servers (also from
Hello,
Mike McClain a écrit :
>
> I can access the windows box through the router via smbclient.
> Even with IPtables that are ACCEPT, ACCEPT, ACCEPT, ... neither lynx
> or Firefox can access the inet though they can access the router.
Web browers are poor tools when it comes to check IP co
On 09-Apr-2000 00:33:46 Beavis wrote:
> doesn't work!
Did you do
'ifconfig lo 127.0.0.1 netmask 255.0.0.0' ? (before the route add
command)
Robert:
Thanks for the correction, and the RFC pointer. I've got it clearly
bookmarked now, so I won't make the same mistake again.
Marc
--
Marc Mongeon <[EMAIL PROTECTED]>
Unix Specialist
Ban-Koe Systems
9100 W Bloomington Fwy
Bloomington, MN 55431-2200
(612)888-0123, x417 | FAX: (612)
On Tue, 23 Nov 1999 08:02:43 CST, "Marc Mongeon" writes:
>Jason:
>
>You have nothing else on the ethernet segment that contains the router
>internal interface and the debian eth1 interface, right? First, stop
>paying for 2 IP addresses that you don't need. Assign "internal" IP
>addresses to the r
Jason:
You have nothing else on the ethernet segment that contains the router
internal interface and the debian eth1 interface, right? First, stop
paying for 2 IP addresses that you don't need. Assign "internal" IP
addresses to the router internal and debian eth1 interfaces, from one
of these IP
Here is the current route table, (output of netstat -nr)
131.107.2.0 0.0.0.0 255.255.255.0 U 1500 0 0
eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 3584 0 0 lo
The reason that it doesn't show the 207.158.140.138 address is because it
says tha
28 matches
Mail list logo
