Things are finally running very smoothly. The WWW site and internet connection have not missed a beat in the last week or so. The internet link is still requiring periodic restarts, but we hope to have that fixed quickly. We are just waiting on new firewall software before changing the configuration of the network. The change from public to private addresses in the DMZ has been quite successful. This will allow us to implement a multi-homed internet link at some point in the future.
Thursday, March 28, 2002
28-March-2002 : WWW Site
Things are finally running very smoothly. The WWW site and internet connection have not missed a beat in the last week or so. The internet link is still requiring periodic restarts, but we hope to have that fixed quickly. We are just waiting on new firewall software before changing the configuration of the network. The change from public to private addresses in the DMZ has been quite successful. This will allow us to implement a multi-homed internet link at some point in the future.
Things are finally running very smoothly. The WWW site and internet connection have not missed a beat in the last week or so. The internet link is still requiring periodic restarts, but we hope to have that fixed quickly. We are just waiting on new firewall software before changing the configuration of the network. The change from public to private addresses in the DMZ has been quite successful. This will allow us to implement a multi-homed internet link at some point in the future.
Wednesday, March 20, 2002
20-March-2002 : ADSL and Server Failure
ADSL is now working correctly. I am restarting the modem every few hours automatically to ward off issues that I have been seeing with the modem.
Our main server failed on Saturday causing an outage of several hours. Added to this were some routing issues to do with address translation and the Alcatel Speedtouch Pro ADSL modem. Specifically pinholing does not seem to work well with this modem, and settings seem to be lost on reboot.
ADSL is now working correctly. I am restarting the modem every few hours automatically to ward off issues that I have been seeing with the modem.
Our main server failed on Saturday causing an outage of several hours. Added to this were some routing issues to do with address translation and the Alcatel Speedtouch Pro ADSL modem. Specifically pinholing does not seem to work well with this modem, and settings seem to be lost on reboot.
Friday, March 08, 2002
8-March-2002 : ADSL
Once again ADSL should be working well. I have powered down the DIALUP connection, and I am running on ADSL only at the moment. I needed to restart the ADSL modem again this evening due to packet losses. I have not yet worked out why - Is it Telstra or Me? Or AlwaysOnline?
Once again ADSL should be working well. I have powered down the DIALUP connection, and I am running on ADSL only at the moment. I needed to restart the ADSL modem again this evening due to packet losses. I have not yet worked out why - Is it Telstra or Me? Or AlwaysOnline?
Wednesday, March 06, 2002
6-March-2002 : ADSL : Spoke too soon
OK... Spoke too soon... I am having problems with my connection. An example is
traceroute to www.alwaysonline.net.au (202.181.16.9), 30 hops max, 38 byte packets
1 reactor (203.42.174.62) 0.726 ms 0.545 ms 0.432 ms
2 syd-h427.adsl.AlwaysONLINE.net.au (202.181.20.30) 2.268 ms 12.582 ms 1.71 5 ms
3 * * 172.31.26.15 (172.31.26.15) 32.430 ms
4 172.31.52.15 34.415 ms 37.715 ms 37.988 ms
5 Syd-ADSL.lnk.alwaysonline.net.au (203.22.184.198) 39.167 ms 35.974 ms 37.768 ms
6 vzdy.AlwaysONLINE.net.au (202.181.16.9) 37.541 ms 37.598 ms 39.795 ms
PING www.alwaysonline.net.au (202.181.16.9) from 203.42.174.49 : 56(84) bytes of
data.
64 bytes from vzdy.AlwaysONLINE.net.au (202.181.16.9): icmp_seq=33 ttl=59 time=3
9.925 msec
64 bytes from vzdy.AlwaysONLINE.net.au (202.181.16.9): icmp_seq=34 ttl=59 time=3
9.924 msec
64 bytes from vzdy.AlwaysONLINE.net.au (202.181.16.9): icmp_seq=35 ttl=59 time=3
9.913 msec
--- www.alwaysonline.net.au ping statistics ---
36 packets transmitted, 3 packets received, 91% packet loss
round-trip min/avg/max/mdev = 39.913/39.920/39.925/0.230 ms
Note the packet losses... This is a killer to TCP/IP. And worse is that
OK... Spoke too soon... I am having problems with my connection. An example is
traceroute to www.alwaysonline.net.au (202.181.16.9), 30 hops max, 38 byte packets
1 reactor (203.42.174.62) 0.726 ms 0.545 ms 0.432 ms
2 syd-h427.adsl.AlwaysONLINE.net.au (202.181.20.30) 2.268 ms 12.582 ms 1.71 5 ms
3 * * 172.31.26.15 (172.31.26.15) 32.430 ms
4 172.31.52.15 34.415 ms 37.715 ms 37.988 ms
5 Syd-ADSL.lnk.alwaysonline.net.au (203.22.184.198) 39.167 ms 35.974 ms 37.768 ms
6 vzdy.AlwaysONLINE.net.au (202.181.16.9) 37.541 ms 37.598 ms 39.795 ms
PING www.alwaysonline.net.au (202.181.16.9) from 203.42.174.49 : 56(84) bytes of
data.
64 bytes from vzdy.AlwaysONLINE.net.au (202.181.16.9): icmp_seq=33 ttl=59 time=3
9.925 msec
64 bytes from vzdy.AlwaysONLINE.net.au (202.181.16.9): icmp_seq=34 ttl=59 time=3
9.924 msec
64 bytes from vzdy.AlwaysONLINE.net.au (202.181.16.9): icmp_seq=35 ttl=59 time=3
9.913 msec
--- www.alwaysonline.net.au ping statistics ---
36 packets transmitted, 3 packets received, 91% packet loss
round-trip min/avg/max/mdev = 39.913/39.920/39.925/0.230 ms
Note the packet losses... This is a killer to TCP/IP. And worse is that
6-March-2002 : ADSL
ADSL should be running properly now. I would not be surprised if there were a few problems with the switchover. Moving things over has been a bit stressful, and required some changes to the way that we do things. With luck things should run smoothly now.
ADSL should be running properly now. I would not be surprised if there were a few problems with the switchover. Moving things over has been a bit stressful, and required some changes to the way that we do things. With luck things should run smoothly now.

