Re: ping and host
From: Bruno Costacurta (cd1_at_biz.tiscali.be)
Date: 09/18/05
- Next message: David Schwartz: "Re: Socket Timeouts"
- Previous message: Andy Furniss: "Re: Is it possiable to introduce delay and packet loss in linux firewall!"
- In reply to: Bruno Costacurta: "Re: ping and host"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 18 Sep 2005 11:59:04 +0200
Bruno Costacurta wrote:
>>>>Hi,
>>>>
>>>>perhaps it is a "DNS-loadbalancing" ?
>>>>
>>>>greetings
>>>>ruediger
>>>>
>>>
>>> Why do you mean by a "DNS-loadbalancing" ?
>>>
>>> However the problem I mentioned here appears with a Wireless ADSL
>>> Router. I never had these problems with my previous modem (and same DSN
>>> settings).
>>
>> This isnt a "problem" at all - It looks to me as if it's all working
>> okay.
>>
>> DNS load balancing means (in this case) that google have defined more
>> than one IP address for the www.l.google.com host. The idea being that
>> clients will choose one of the supplied IPs at random - so the "load" on
>> the servers is evenly distributed.
>>
>> The reason you see different results with different routers will be
>> because of the routers internal DNS servers' different behaviours.
>>
>> I presume you have configured the ADSL router as the DNS server for your
>> workstations, or that DHCP is doing this for you - yes?
>>
>> The wireless ADSL router is giving you all the IPs returned by the "real
>> world" DNS servers, but your previous modem was making it's own random
>> choice, and giving you just that one IP. Both approaches are okay,
>> although the old modem isnt playing the whole game.
>>
>> Chris
>>
>> --
>> Using linux, IpTables and Rope to filter P2P and other complex
>> protocols.. http://www.lowth.com/rope
>
> Indeed you're right.
> I tried another ADSL router and received same time out, but in this case,
> browsing is working fine.
> So I have to look in another direction for the problem I still have with a
> not working efficiently router D-Link DSL-G604T.
>
Finally it's working : MTU value was incorrect.
Checking using another working wireless router ADSL I found that MTU was
updated after an ISP probing with different value.
As I setup the correct value on previous non-working D-Link for the MTU
(1458 versus 1500 in my case) everything works fine.
Bruno
- Next message: David Schwartz: "Re: Socket Timeouts"
- Previous message: Andy Furniss: "Re: Is it possiable to introduce delay and packet loss in linux firewall!"
- In reply to: Bruno Costacurta: "Re: ping and host"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
