just some update

hopefully things will remain quiet (x-fingers). 

- whats the odds of having 3 faulty intermittent nics ? did i say holly 
smokes?:-), all 3 where netgear FA310tx rev-02, watch out for c50, c47, 
c44, goes in smoke that is, got replaced by 3com.

- the netgear adsl modem router, suffered from packet loss at high 
speed, and did not handle traffic correctly, back on dlink 502t.

- there's still a fragmented packet sent to the router and cause it to 
go into wild goose chase, am not sure what people are trying to prove!.

Moussa
-- 
The information contained in this post is copyright of
the poster, and specifically may not be published in,
or used by     http://www.jlaforums.com

Hi Moussa,

> - whats the odds of having 3 faulty intermittent nics ? did i say holly
> smokes?:-), all 3 where netgear FA310tx rev-02, watch out for c50, c47,
> c44, goes in smoke that is, got replaced by 3com.

One think I've always done since my mining days in Kalgoorlie is to
ensure
adequate ventilation, I also ALWAYS drill holes in the top and bottom
of
routers/modems to allow the heat out, I could swear all modern cases
are
designed to ensure equipment fails just outside of warranty in a temp
regulated room, so I would imagine failure would be a lot quicker in a
normal/hot room.

The holes in the side of netgear and netcomm and other brand modems/
routers/ADSL
units are a bit of a joke.

Also make sure you have air flow in the card section of the PS/2 if
its not in a cool spot.
I added a fan to my old PS/2 77i when I was using it as a server, in
the card area to the
left to ensure the air was cycled.

I'll try to bring some cooler weather with me when I get to Perth in 2
weeks time :-)

Cheers

Hi Moussa !

> just some update
> 
> hopefully things will remain quiet (x-fingers). 
> 
> - whats the odds of having 3 faulty intermittent nics ? did i say holly 
> smokes?:-), all 3 where netgear FA310tx rev-02, watch out for c50, c47, 
> c44, goes in smoke that is, got replaced by 3com.
> 
> - the netgear adsl modem router, suffered from packet loss at high 
> speed, and did not handle traffic correctly, back on dlink 502t.
> 
> - there's still a fragmented packet sent to the router and cause it to 
> go into wild goose chase, am not sure what people are trying to prove!.

I now always get "Time Out connecting to ..." from your nntp.
Can ping it with ... okay ... long response time (due to satellite 
connection) but it fails to connect to it via Thunderbird.


Peter from Germany
http://www.mcamafia.de

--- news://freenews.netfront.net/ - complaints: news@netfront.net ---

Hi Peter

In article <ho0e3l$177b$1@adenine.netfront.net>, peterwendt@mcamafia.de 
says...
> 
> Hi Moussa !
> 
> I now always get "Time Out connecting to ..." from your nntp.
> Can ping it with ... okay ... long response time (due to satellite 
> connection) but it fails to connect to it via Thunderbird.
it was great to hear some feedback, i have increased the latency time 
out to 240seconds see if this helps.
i have gone back to my old system setup, and started all fresh 
os/hardware when i first posted this message.
i am looking into linux alternative Debian/(INN) ATM.
the current NNTP server still will be on 24/7, until the new is ready.
 
> 
> 
> Peter from Germany
> http://www.mcamafia.de
> 
> --- news://freenews.netfront.net/ - complaints: news@netfront.net ---

Moussa

-- 
The information contained in this post is copyright of
the poster, and specifically may not be published in,
or used by     http://www.jlaforums.com

Hi Moussa !

>> Hi Moussa !
>>
>> I now always get "Time Out connecting to ..." from your nntp.
>> Can ping it with ... okay ... long response time (due to satellite 
>> connection) but it fails to connect to it via Thunderbird.

> it was great to hear some feedback, i have increased the latency time 
> out to 240seconds see if this helps.

Still no joy - unfortunately.
I first assumed it were a problem with Thunderbird, since I'd recently 
ran the update to 2.0.0.24 (from 2.0.0.20) and the problem first showed 
up afterwards. On the other hand I can reach freenews.netfront.net with 
minor problems. It tends to time out occasionally as well, especially 
when my "housemates" are active on the 'net too and do music streaming.
Normally it connects on second attempt - like just now.

> i have gone back to my old system setup, and started all fresh 
> os/hardware when i first posted this message.
> i am looking into linux alternative Debian/(INN) ATM.
> the current NNTP server still will be on 24/7, until the new is ready.

Just for snorts and giggles I put in my ping stats here:


Ping ps2moussa.homedns.org [124.168.234.114] mit 32 Bytes Daten:

Antwort von 124.168.234.114: Bytes=32 Zeit=1245ms TTL=46
Antwort von 124.168.234.114: Bytes=32 Zeit=1047ms TTL=46
Antwort von 124.168.234.114: Bytes=32 Zeit=1325ms TTL=46
Antwort von 124.168.234.114: Bytes=32 Zeit=1310ms TTL=46


Ping-Statistik f��r 124.168.234.114:
     Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
Ca. Zeitangaben in Millisek.:
     Minimum = 1047ms, Maximum = 1325ms, Mittelwert = 1231ms


Values for freenews are very much similar with about 1200ms average.


Peter from Germany
http://www.mcamafia.de

--- news://freenews.netfront.net/ - complaints: news@netfront.net ---

PING ps2moussa.homedns.org (124.168.234.114) 56(84) bytes of data.
64 bytes from 124-168-234-114.dyn.iinet.net.au (124.168.234.114): 
icmp_seq=1 ttl=47 time=450 ms
64 bytes from 124-168-234-114.dyn.iinet.net.au (124.168.234.114): 
icmp_seq=2 ttl=47 time=449 ms
64 bytes from 124-168-234-114.dyn.iinet.net.au (124.168.234.114): 
icmp_seq=3 ttl=47 time=449 ms
64 bytes from 124-168-234-114.dyn.iinet.net.au (124.168.234.114): 
icmp_seq=4 ttl=47 time=452 ms
64 bytes from 124-168-234-114.dyn.iinet.net.au (124.168.234.114): 
icmp_seq=5 ttl=47 time=450 ms
64 bytes from 124-168-234-114.dyn.iinet.net.au (124.168.234.114): 
icmp_seq=6 ttl=47 time=437 ms
64 bytes from 124-168-234-114.dyn.iinet.net.au (124.168.234.114): 
icmp_seq=7 ttl=47 time=438 ms
64 bytes from 124-168-234-114.dyn.iinet.net.au (124.168.234.114): 
icmp_seq=8 ttl=47 time=456 ms

--- ps2moussa.homedns.org ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 6997ms
rtt min/avg/max/mdev = 437.791/448.310/456.858/6.318 ms

Hi

In article <t33pn.37252$Ua.2218@twister2.libero.it>, supervinx@libero.it 
says...
> 
> PING ps2moussa.homedns.org (124.168.234.114) 56(84) bytes of data.
> 64 bytes from 124-168-234-114.dyn.iinet.net.au (124.168.234.114): 
> icmp_seq=1 ttl=47 time=450 ms
> 64 bytes from 124-168-234-114.dyn.iinet.net.au (124.168.234.114): 
> icmp_seq=2 ttl=47 time=449 ms
> 64 bytes from 124-168-234-114.dyn.iinet.net.au (124.168.234.114): 
> icmp_seq=3 ttl=47 time=449 ms
> 64 bytes from 124-168-234-114.dyn.iinet.net.au (124.168.234.114): 
> icmp_seq=4 ttl=47 time=452 ms
> 64 bytes from 124-168-234-114.dyn.iinet.net.au (124.168.234.114): 
> icmp_seq=5 ttl=47 time=450 ms
> 64 bytes from 124-168-234-114.dyn.iinet.net.au (124.168.234.114): 
> icmp_seq=6 ttl=47 time=437 ms
> 64 bytes from 124-168-234-114.dyn.iinet.net.au (124.168.234.114): 
> icmp_seq=7 ttl=47 time=438 ms
> 64 bytes from 124-168-234-114.dyn.iinet.net.au (124.168.234.114): 
> icmp_seq=8 ttl=47 time=456 ms
> 
> --- ps2moussa.homedns.org ping statistics ---
> 8 packets transmitted, 8 received, 0% packet loss, time 6997ms
> rtt min/avg/max/mdev = 437.791/448.310/456.858/6.318 ms

are you able to access the server?, try to post something to 
internal.test

Moussa
-- 
The information contained in this post is copyright of
the poster, and specifically may not be published in,
or used by     http://www.jlaforums.com

hi Peter

In article <ho26jh$vdv$1@adenine.netfront.net>, peterwendt@mcamafia.de 
says...
> 
> Still no joy - unfortunately.
> I first assumed it were a problem with Thunderbird, since I'd recently 
> ran the update to 2.0.0.24 (from 2.0.0.20) and the problem first showed 
> up afterwards. On the other hand I can reach freenews.netfront.net with 
> minor problems. It tends to time out occasionally as well, especially 
> when my "housemates" are active on the 'net too and do music streaming.
> Normally it connects on second attempt - like just now.
i am quite certain is a clogged pipe along the super highway, iinet is 
growing in popularity fast, it grew from local isp to a major payer in 
the telco game, i read a planned upgrade on 29/03 for their external 
link, is about time we had some fiber dammit, the 5 inch cable is 10 
meters from my front door, is been sitting there since 2001.
 

> Just for snorts and giggles I put in my ping stats here:
> 
> 
> Ping ps2moussa.homedns.org [124.168.234.114] mit 32 Bytes Daten:
> 
> Antwort von 124.168.234.114: Bytes=32 Zeit=1245ms TTL=46
> Antwort von 124.168.234.114: Bytes=32 Zeit=1047ms TTL=46
> Antwort von 124.168.234.114: Bytes=32 Zeit=1325ms TTL=46
> Antwort von 124.168.234.114: Bytes=32 Zeit=1310ms TTL=46

that is still not a bad connection compared to 300bps Dial up :-)

> 
> 
> Ping-Statistik fü?r 124.168.234.114:
>      Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
> Ca. Zeitangaben in Millisek.:
>      Minimum = 1047ms, Maximum = 1325ms, Mittelwert = 1231ms
> 
> 
> Values for freenews are very much similar with about 1200ms average.
is it a 2 way ? or one way + dial up for up-link?
satellite connection is greatly affected by clouds, rain and UFOs. :-)
my ADSL connection is 12000/1500.
 
> 
> Peter from Germany
> http://www.mcamafia.de
> 
> --- news://freenews.netfront.net/ - complaints: news@netfront.net ---

Moussa
-- 
The information contained in this post is copyright of
the poster, and specifically may not be published in,
or used by     http://www.jlaforums.com

Hi Moussa,

Here's my 2cts

Ping naar ps2moussa.homedns.org [124.168.234.114]
 met 32 byte gegevens:

Antwoord van 124.168.234.114: bytes=32 tijd=447 ms TTL=41
Antwoord van 124.168.234.114: bytes=32 tijd=446 ms TTL=41
Antwoord van 124.168.234.114: bytes=32 tijd=447 ms TTL=41
Antwoord van 124.168.234.114: bytes=32 tijd=444 ms TTL=41

Ping-stats voor 124.168.234.114:
 Pakketten: verzonden = 4, ontvangen = 4, verloren = 0
 (0% verlies).
De gemiddelde tijd voor het uitvoeren van één bewerking
 in milliseconden:
    Minimum = 444ms, Maximum = 447ms, Gemiddelde = 446ms


tracert ps2moussa.homedns.org
Bezig met het traceren van de route naar ps2moussa.homedns.org 
[124.168.234.114]
via maximaal 30 hops:

  1     *        *        *     Time-out bij opdracht.
  2     *        *        *     Time-out bij opdracht.
  3     *        *        *     Time-out bij opdracht.
  4     *        *        *     Time-out bij opdracht.
  5     *        *        *     Time-out bij opdracht.
  6     *        *        *     Time-out bij opdracht.
  7     *        *        *     Time-out bij opdracht.
  8     *        *        *     Time-out bij opdracht.
  9     *        *        *     Time-out bij opdracht.
 10     *        *        *     Time-out bij opdracht.
 11     *     ^C

I stopped it here. No use kicking a dead horse IMO.

-- 
Jelte,
Admirer of the letter of IBM with blue Ishiki

Hi Moussa !

> i am quite certain is a clogged pipe along the super highway, iinet is 
> growing in popularity fast, it grew from local isp to a major payer in 
> the telco game, i read a planned upgrade on 29/03 for their external 
> link, is about time we had some fiber dammit, the 5 inch cable is 10 
> meters from my front door, is been sitting there since 2001.

Now - that's bad luck I'd say.
I live on the german countryside and we neither have cable-DSL or 
cable-TV. Most of the hardware is from the early 50s with some upgrades 
from the late 80's made for ISDN.

> 
>> Just for snorts and giggles I put in my ping stats here:
>>
>>
>> Ping ps2moussa.homedns.org [124.168.234.114] mit 32 Bytes Daten:
>>
>> Antwort von 124.168.234.114: Bytes=32 Zeit=1245ms TTL=46
>> Antwort von 124.168.234.114: Bytes=32 Zeit=1047ms TTL=46
>> Antwort von 124.168.234.114: Bytes=32 Zeit=1325ms TTL=46
>> Antwort von 124.168.234.114: Bytes=32 Zeit=1310ms TTL=46
> 
> that is still not a bad connection compared to 300bps Dial up :-)

"Winners compare with their goals - loosers compare with others."
;-)

When I started with computers in the late 70s a 300 bps was standard, a 
1200 bps modem was "hitech". Acoustic couplers were standard, real 
hardwired modems illegal. I built my own ones with the AMD "world modem" 
chip ... and did not care about legal consequences. (Never got caught 
however). I used my ZX Spectrum 48K with serial interface and selfmade 
modem to connect to the first FIDO boxes in about 85 / 86. It had lesser 
OS overhead ...

>>
>> Ping-Statistik fü?r 124.168.234.114:
>>      Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
>> Ca. Zeitangaben in Millisek.:
>>      Minimum = 1047ms, Maximum = 1325ms, Mittelwert = 1231ms
>>
>>
>> Values for freenews are very much similar with about 1200ms average.

> is it a 2 way ? or one way + dial up for up-link?
> satellite connection is greatly affected by clouds, rain and UFOs. :-)
> my ADSL connection is 12000/1500.

It is a 2-way connection with 1000 Kbps downlink / 128 Kbps uplink.
The "economical solution". I could have gotten a faster one, but the 
pricing is somewhat hyperbolical and not just a bargain compared with 
cable-DSL, which -in addition- is combined with a flatrate phone link.
I still use my ISDN phone while the internet connection is a totally 
independent and separate hardware and connection. Have the ISDN dial-in 
as a backup, though. Gives the same result for your nntp however, so I 
don't think it has much to do with the way the information is routed or 
its timing in general.


Peter from Germany
http://www.mcamafia.de

--- news://freenews.netfront.net/ - complaints: news@netfront.net ---

Hi Moussa !

Get the same problem with Netscape newsreader as well.
So it is
a) independent from the way / type of connection (sat-DSL or ISDN dial-in)
b) independent from the newsreader SW

Authentification problem ?
On another machine I get the message "Connection refused" ... ?


Peter from Germany
http://www.mcamafia.de

--- news://freenews.netfront.net/ - complaints: news@netfront.net ---

Hi Jelte !

> Here's my 2cts
> 
> Ping naar ps2moussa.homedns.org [124.168.234.114]
> met 32 byte gegevens:
> 
> Antwoord van 124.168.234.114: bytes=32 tijd=447 ms TTL=41
> Antwoord van 124.168.234.114: bytes=32 tijd=446 ms TTL=41
> Antwoord van 124.168.234.114: bytes=32 tijd=447 ms TTL=41
> Antwoord van 124.168.234.114: bytes=32 tijd=444 ms TTL=41
> 
> Ping-stats voor 124.168.234.114:
> Pakketten: verzonden = 4, ontvangen = 4, verloren = 0
> (0% verlies).
> De gemiddelde tijd voor het uitvoeren van één bewerking
> in milliseconden:
>    Minimum = 444ms, Maximum = 447ms, Gemiddelde = 446ms

Would guess it is a normal range. Something similar comes out for me, 
when I test the connection via ISDN Dial-In.

> tracert ps2moussa.homedns.org
> Bezig met het traceren van de route naar ps2moussa.homedns.org 
> [124.168.234.114]
> via maximaal 30 hops:
> 
>  1     *        *        *     Time-out bij opdracht.
>  2     *        *        *     Time-out bij opdracht.
>  3     *        *        *     Time-out bij opdracht.
>  4     *        *        *     Time-out bij opdracht.
>  5     *        *        *     Time-out bij opdracht.
>  6     *        *        *     Time-out bij opdracht.
>  7     *        *        *     Time-out bij opdracht.
>  8     *        *        *     Time-out bij opdracht.
>  9     *        *        *     Time-out bij opdracht.
> 10     *        *        *     Time-out bij opdracht.
> 11     *     ^C
> 
> I stopped it here. No use kicking a dead horse IMO.
> 

:-)

Look:


Routenverfolgung zu ps2moussa.homedns.org [124.168.234.114]  über 
maximal 30 Abschnitte:

   1     1 ms     1 ms     1 ms  1.a2c-net246.astra2connect.com 
[212.56.246.1]
   2   904 ms   927 ms   871 ms  172.16.211.254
   3   664 ms   977 ms  1053 ms  213.169.121.69
   4   883 ms   703 ms  1290 ms  213.169.121.117
   5   879 ms   736 ms   767 ms  Ceres-Venus-850.astra-net.com 
[212.56.230.238]
   6  1025 ms   742 ms   868 ms  109.120.64.1
   7   903 ms   928 ms   947 ms  217.239.40.53
   8   915 ms   907 ms   904 ms  62.156.138.146
   9  1639 ms   923 ms   839 ms  i-10-0-0.paix-core02.bi.reach.com 
[202.84.251.73]
  10  1313 ms  1375 ms  1799 ms  i-13-0.sydp-core04.bx.reach.com 
[202.84.140.105]
  11   995 ms   983 ms  1299 ms  static.net.reach.com [134.159.160.58]
  12  1275 ms  1771 ms  1503 ms  te1-0-0.per-qv1-bdr2.iinet.net.au 
[203.215.20.69]
  13  1107 ms  1263 ms  1107 ms  te9-1.per-qv1-bng1.iinet.net.au 
[203.215.4.37]
  14  1074 ms  1171 ms  1616 ms  124-168-234-114.dyn.iinet.net.au 
[124.168.234.114]

Ablaufverfolgung beendet.


That's how the SAT-link looks like. So it works. At least.
Uh - latest try resolves a different IP for ps2moussa: 203.214.7.98
And a slightly faster transfer.


Peter from Germany
http://www.mcamafia.de


--- news://freenews.netfront.net/ - complaints: news@netfront.net ---

Hi peter


"Peter H. Wendt" <peterwendt@aol.com> wrote in message 
news:ho2hu4$1fj1$1@adenine.netfront.net...
> Hi Moussa !
>
> Get the same problem with Netscape newsreader as well.
> So it is
> a) independent from the way / type of connection (sat-DSL or ISDN dial-in)
> b) independent from the newsreader SW
>
> Authentification problem ?
> On another machine I get the message "Connection refused" ... ?
someone is blocking port 119
try port 3119 instead

>
>
> Peter from Germany
> http://www.mcamafia.de
>
> --- news://freenews.netfront.net/ - complaints: news@netfront.net ---

Moussa

Hi !

As a funny fact: the connection works again. Momentarily ? I hope not.
It is the 203.214.7.98 adress.

-- 
Very friendly greetings from Peter in Germany
http://members.aol.com/mcapage0/mcaindex.htm

*** Reply to: peterwendt@mcamafia.de only ! ***

'Tag Peter,

"Peter H. Wendt" <peterwendt@mcamafia.de> schreef in bericht 
news:ho2ipo$1h2f$1@adenine.netfront.net...
> Hi Jelte !
>
<snip>
>
> Would guess it is a normal range. Something similar comes out for me, when 
> I test the connection via ISDN Dial-In.

Yes, pretty straightforward. Mine is a 4Mb/1Mb ADSL-link.

>
>> tracert ps2moussa.homedns.org

<snip>

>
> Look:
>
>
> Routenverfolgung zu ps2moussa.homedns.org [124.168.234.114]  über maximal 
> 30 Abschnitte:
>
>   1     1 ms     1 ms     1 ms  1.a2c-net246.astra2connect.com 
> [212.56.246.1]
>   2   904 ms   927 ms   871 ms  172.16.211.254
>   3   664 ms   977 ms  1053 ms  213.169.121.69
>   4   883 ms   703 ms  1290 ms  213.169.121.117
>   5   879 ms   736 ms   767 ms  Ceres-Venus-850.astra-net.com 
> [212.56.230.238]
>   6  1025 ms   742 ms   868 ms  109.120.64.1
>   7   903 ms   928 ms   947 ms  217.239.40.53
>   8   915 ms   907 ms   904 ms  62.156.138.146
>   9  1639 ms   923 ms   839 ms  i-10-0-0.paix-core02.bi.reach.com 
> [202.84.251.73]
>  10  1313 ms  1375 ms  1799 ms  i-13-0.sydp-core04.bx.reach.com 
> [202.84.140.105]
>  11   995 ms   983 ms  1299 ms  static.net.reach.com [134.159.160.58]
>  12  1275 ms  1771 ms  1503 ms  te1-0-0.per-qv1-bdr2.iinet.net.au 
> [203.215.20.69]
>  13  1107 ms  1263 ms  1107 ms  te9-1.per-qv1-bng1.iinet.net.au 
> [203.215.4.37]
>  14  1074 ms  1171 ms  1616 ms  124-168-234-114.dyn.iinet.net.au 
> [124.168.234.114]
>
> Ablaufverfolgung beendet.
>

You would have thought that routing via sat would cut down on the number of 
hops, but . . . 14??
Not very efficient IMO.
But, as you say, it works.

>
> That's how the SAT-link looks like. So it works. At least.
> Uh - latest try resolves a different IP for ps2moussa: 203.214.7.98
> And a slightly faster transfer.

Tried a tracert again just now:
New IP :-)
Same time-outs :-(

Tried to reach 203.214.7.98 :
"The connection to the server was reset while the page was loading."

Tried to reach 203.214.7.98:3119 :

200 NNTP-Server Classic Hamster Vr. 2.1 (Build 2.1.0.11) (post ok) says: Hi!
500 Command not implemented.
500 Command not implemented.
500 Command not implemented.
500 Command not implemented.
500 Command not implemented.
500 Command not implemented.
500 Command not implemented.
500 Command not implemented.
500 Command not implemented.

At l(e)ast the hamster says "Hi"

Moussa, you've got talking rodents!

-- 
Jelte,
Admirer of the letter of IBM with blue Ishiki 

Starting Nmap 4.53 ( http://insecure.org ) at 2010-03-20 21:50 CET
Interesting ports on 203-214-7-98.dyn.iinet.net.au (203.214.7.98):
Not shown: 1713 filtered ports
PORT    STATE SERVICE
119/tcp open  nntp

Port 119 is open ...

Hi

In article <EDapn.148896$9f6.182636@twister1.libero.it>, 
supervinx@libero.it says...
> 
> Starting Nmap 4.53 ( http://insecure.org ) at 2010-03-20 21:50 CET
> Interesting ports on 203-214-7-98.dyn.iinet.net.au (203.214.7.98):
> Not shown: 1713 filtered ports
> PORT    STATE SERVICE
> 119/tcp open  nntp
> 
> Port 119 is open ...

i know i left it open, both ports pointing to 119

Moussa
-- 
The information contained in this post is copyright of
the poster, and specifically may not be published in,
or used by     http://www.jlaforums.com

In article <OKCdnWz1aMC1fDnWnZ2dnUVZ_i2dnZ2d@westnet.com.au>, 
peterwendt@mcamafia.de says...
> 
> Hi !
> 
> As a funny fact: the connection works again. Momentarily ? I hope not.
> It is the 203.214.7.98 adress.
i replicated the port service on the router, that seems has done the 
trick, either someone is hijacking port 119, or a glitch in ipcop.

am using IPcop 1.9 beta

Moussa
-- 
The information contained in this post is copyright of
the poster, and specifically may not be published in,
or used by     http://www.jlaforums.com

Hi guys...

> > As a funny fact: the connection works again. Momentarily ? I hope not.
> > It is the 203.214.7.98 adress.
> i replicated the port service on the router, that seems has done the
> trick, either someone is hijacking port 119, or a glitch in ipcop.
>
> am using IPcop 1.9 beta
>
> Moussa

Just to throw in my Euro 0,10

>ping ps2moussa.homedns.org

Pinging ps2moussa.homedns.org [124.150.54.37] with 32 bytes of data:

Reply from 124.150.54.37: bytes=32 time=430ms TTL=46
Reply from 124.150.54.37: bytes=32 time=434ms TTL=46
Reply from 124.150.54.37: bytes=32 time=425ms TTL=46
Reply from 124.150.54.37: bytes=32 time=421ms TTL=46

Ping statistics for 124.150.54.37:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 421ms, Maximum =  434ms, Average =  427ms

>tracert ps2moussa.homedns.org

 Tracing route to ps2moussa.homedns.org [124.150.54.37] over a maximum of 30
hops:
   1    10 ms     2 ms     2 ms  192.168.1.126
   2     *        *        *     Request timed out.
   3     8 ms    32 ms    36 ms  glfd-cam-1b-ge911.network.virginmedia.net
[80.4.30.153]
   4     9 ms    16 ms    25 ms
glfd-core-1b-ge-114-0.network.virginmedia.net [195.182.181.229]
   5    20 ms    57 ms    12 ms  glfd-bb-1b-ge-220-0.network.virginmedia.net
[213.105.175.89]
   6    10 ms    10 ms     8 ms  glfd-bb-1a-ae0-0.network.virginmedia.net
[213.105.172.5]
   7    45 ms    32 ms    33 ms  213.152.245.49
   8    47 ms    45 ms    36 ms  so-1-3-0.mpr1.lhr3.uk.above.net
[64.125.28.197]
   9    40 ms    32 ms    71 ms  xe-1-1-0.mpr2.lhr3.uk.above.net
[64.125.27.158]
  10    33 ms    41 ms    53 ms  195.66.226.166
  11   103 ms   102 ms   119 ms  i-11-2.nwk-core01.bx.reach.com
[202.84.144.141]
  12   183 ms   172 ms   170 ms  i-14-1-1.wil-core02.bi.reach.com
[202.84.141.134]
  13   324 ms   324 ms   339 ms  i-2-0.sydp-core04.bx.reach.com
[202.84.140.101]
  14   356 ms   323 ms   324 ms  static.net.reach.com [134.159.160.58]
  15   398 ms   391 ms   389 ms  ge4-2.per-qv1-bdr2.iinet.net.au
[203.215.20.65]
  16   407 ms   414 ms   389 ms  te9-1.per-qv1-bng1.iinet.net.au
[203.215.4.37]
  17   419 ms   440 ms   423 ms  ps2moussa.homedns.org [124.150.54.37]
  Trace complete.

This is from my laptop [192.168.1.32] via 802.11b 11Mbps to my Buffalo
WZR-RS-G54 Access Point/Gateway [192.168.1.126] and on via Cable Modem/Fibre
as below:

System Information Model   WZR-RS-G54 Ver.2.43
AirStation Name   AP000D0B47F8AC
DHCP Server   Enabled
Wireless Settings   MAC Address 00:07:40:FE:2F:56
Wireless Driver WLI-MPCI-G54 Ver.3.60.9.0
Wireless Mode Mixed
SSID WLANG0
Wireless Channel 2
Frame Bursting Enabled
Encryption Mode WEP
Privacy Separator Disabled
SSID Broadcast Enabled
MAC Filtering  Disabled
WDS Bridge  Enabled [Wireless Bridge (WDS) Dedicated Mode:Disabled ]
Output Power  100%

LAN Settings   MAC Address 00:0D:0B:47:F0:9C
IP Address 192.168.1.126
Subnet Mask 255.255.255.0

WAN Settings   DHCP Client (Online)

----------------------------------------------------------------------------
----

Connection Established Time 2010/03/19 23:38:58
Lease Expiration Time 2010/03/26 23:38:58
Domain Name
Host Name gateway1
DHCP Server Address 62.253.131.62

----------------------------------------------------------------------------
----

IP Address 81.100.55.64
Subnet Mask 255.255.252.0
MTU Value 1500
DNS1(Primary) 194.168.4.100 (auto)
DNS2(Secondary) 194.168.8.100 (auto)
DNS3: 10.112.112.121 (auto)

----------------------------------------------------------------------------
----

PPTP Client (Idle)

----------------------------------------------------------------------------
----

MAC Address 00:0D:0B:47:F0:9D

Default Gateway   81.100.52.1 WAN (auto)

-- 
Cheers,
    Tim Clarke (a.k.a. WBST)
    Guildford, U.K.

Forgot to mention, my "cable" service is supposedly 10Mbps bandwidth.
-- 
Cheers,
    Tim Clarke (a.k.a. WBST)
    Guildford, U.K.

hi

In article <YJzpn.15687$dx1.1773@newsfe29.ams2>, 
WBSTClarke@googlemail.com says...
> 
> Hi guys...
you should consider buying a power plant :-)
i once get told, that your network design should fit your personality 
:-)
take me for example

(Internet)-[adsl]-red-[ipcop]-Green--[192.168.1]-------(LAN)
         bridgeMode   [ipcop]-Blue---[192.168.2]--[linksys]--(wifi)
                      [ipcop]-Orange-[192.168.3]-(DMZ)-[192.168.3.119]
                                                          NNTP Server   
don't mind the blue Cat5E spaghetti runs :-)

Moussa
-- 
The information contained in this post is copyright of
the poster, and specifically may not be published in,
or used by     http://www.jlaforums.com

Hi Moussa,

> hi
>
> you should consider buying a power plant :-)
> i once get told, that your network design should fit your personality
> :-)
> take me for example
>
> (Internet)-[adsl]-red-[ipcop]-Green--[192.168.1]-------(LAN)
>          bridgeMode   [ipcop]-Blue---[192.168.2]--[linksys]--(wifi)
>                       [ipcop]-Orange-[192.168.3]-(DMZ)-[192.168.3.119]
>                                                           NNTP Server
> don't mind the blue Cat5E spaghetti runs :-)
>
> Moussa

Only if you're interested...

Fibre --> Abit Cable Modem (have spare due to some confusion at Virgin Media
when supplying me with a free upgrade to my purchased 3Com "Tailfin", which
I've had since the NTL "pilot" of cable connectivity here in Guildford,
circa 1999/2000) --> #1 Buffalo WZR-RS-G54 802.11b/g bursting Access
Point/Bridge/Gateway <= 125Mbps claimed when used with compatible 802.11g
cards and drivers, from which it gets a little flexible/complicated...

Bridged to #2 Buffalo WZR-RS-G54 (WLANG1) upstairs, where most of the
laptops live, with or without wireless 802.11b or 802.11g cards and/or
1000/100/10Base-T cards through an ES-T4 8-port Gigabit switch to one of the
WZR's 100Base-T ports.

Connected to Ethernet segment 192.168.1.x via IBM 8222 8-port hub and then
onto the 10Base2 coaxial cable for most of the PS/2s and PC Servers I have,
including my "master" OS/2 Warp Server based 9595A (P90 only) for file
serving and repository plus logon account management on the Intranet here
and also serving as the primary router to the downstairs (server room)
16Mbps Token-Ring segment for "other purposes" (APPN, APPC and other
networking protocols and architectures, for example).

These base 10Base2 and 16Mbps Token-Ring segments can, optionally, be
bridged/routed together via either or both of an IBM 8229-00n
Ethernet/Token-Ring Bridge and/or an IBM 8274-913 (sort-of) LAN RouteSwitch
with redundant PSUs and multiple multi-port Ethernet (10BaseT and 100BaseT)
and Token-Ring (4Mbs/16Mbps) "blades".

Most of the NetFinitys, having built-in 100BaseT and additional failover
(whoever invented that word and its usage should be shot) 100BaseT adapters
will, eventually be set up on the 100BaseT (currently notional) LAN
"segment", which may become the backbone segment with the 10BaseT/2 stuff
being "relocated" from 192.168.1.x to, say, 192.168.3.x and bridged/routed
accordingly.

The 7013-J50 is currently Ethernet 100BaseT only and not fully set up (plus
I've got to get up to speed on AIX 5L v5.1 for that to become a reality),
but could well play a role there.

The PC Server 500 and 520 S/390s do much of their SNA emulated
interconnectivity (pretend channel-to-channel, a.k.a. CTC) over another
16Mbps Token-Ring segment (192.168.32.x) using LANStreamer adapters and the
Multiprise will join them, along with *real* ESCON CTC connectivity over
multi-mode fibre (62.5 nanometer, IIRC) once I can get the PC Server S/390s'
drivers for the MCA Type-5 adapters sorted and working from the 3172 OS/2
driver stuff that I have to hand. All S/390-based stuff, of course, also
have Ethernet connectivity (often dual, one for the S/390 "side" and one for
the OS/2 TCP/IP stack "side") via Dual EtherStreamers on the Ethernet
backbone segment (192.168.1.x) with one of the PC Server S/390s acting as
router to the "S/390 backbone" (192.168.32.x).

The Pioneer DRM-6NX 6-CD Network Server (external port 808hangs off one of
the primary Access Point/Bridge/Gateway's 100BaseT ports and there's another
that needs some work, which will probably go off a port of the "other"
Access Point/DSL Gateway that connects my other, notionally backup,
broadband service via TalkTalk. That still needs a lot of configuration and
setup details working out to provide a more seamless alternate access
outbound and, later, inbound. Just don't hold your breath on these last
points, they're unlikely to be completed soon.

As for the Pioneer DRM-500X, I've no idea when I'll get back to finishing
the OS/2 driver that I started development on, but "it's on the list".
-- 
Cheers,
    Tim Clarke (a.k.a. WBST)
    Guildford, U.K.

Hi Moussa !

>> As a funny fact: the connection works again. Momentarily ? I hope not.
>> It is the 203.214.7.98 adress.
> i replicated the port service on the router, that seems has done the 
> trick, either someone is hijacking port 119, or a glitch in ipcop.
> 
> am using IPcop 1.9 beta

Now you are back to another IP (124.150.54.37 that is) it times out again.

Hmmm.


Peter from Germany
http://www.mcamafia.de

--- news://freenews.netfront.net/ - complaints: news@netfront.net ---

Hi Peter

In article <ho8451$2lot$1@adenine.netfront.net>, peterwendt@mcamafia.de 
says...
> 
you might not be aware, we got hit by nasty freaking storm yesterday 
with gusty winds and hail the size of a golf ball, which did cause allot 
of damage, power outage etc..., the storm continued during the night 
time with lightning and power surges, we expecting another front this 
morning according to the weather bureau, they also lost their radar (got 
hit by lightning so i have been told).

http://www.bom.gov.au/cgi-bin/wrap_fwo.pl?IDW28201.txt
http://www.bom.gov.au/weather/wa/forecasts/perth.shtml

you can follow most of the action here
http://www.bom.gov.au/products/IDR123.loop.shtml#skip

> 
> Now you are back to another IP (124.150.54.37 that is) it times out again.
if this is the case then, i would say they have routing problem on their 
hand or faulty hardware at the exchange, i will call the ISP and lodge a 
complain.

> 
> Hmmm.
> 
> 
> Peter from Germany
> http://www.mcamafia.de
> 
> --- news://freenews.netfront.net/ - complaints: news@netfront.net ---

Moussa

-- 
The information contained in this post is copyright of
the poster, and specifically may not be published in,
or used by     http://www.jlaforums.com

Hi Moussa !

> you might not be aware, we got hit by nasty freaking storm yesterday 
> with gusty winds and hail the size of a golf ball, which did cause allot 
> of damage, power outage etc..., the storm continued during the night 
> time with lightning and power surges, we expecting another front this 
> morning according to the weather bureau, they also lost their radar (got 
> hit by lightning so i have been told).
> 
> http://www.bom.gov.au/cgi-bin/wrap_fwo.pl?IDW28201.txt
> http://www.bom.gov.au/weather/wa/forecasts/perth.shtml
> 
> you can follow most of the action here
> http://www.bom.gov.au/products/IDR123.loop.shtml#skip

We got a blue-sky, very sunny and quiet day yesterday with daytime 
temperature at about 15 - 18�C. It dropped to 3 - 5�C in the night 
however. Not ideal for camping outside in a tent ...

>> Now you are back to another IP (124.150.54.37 that is) it times out again.
> if this is the case then, i would say they have routing problem on their 
> hand or faulty hardware at the exchange, i will call the ISP and lodge a 
> complain.

Now you are back to a 203.214.22.190 and it works again.

-- 
Very friendly greetings from Peter in Germany
http://www.mcamafia.de/mcapage0/mcaindex.htm

*** Reply to: peterwendt@mcamafia.de only ! ***