Departures and network debugging
Dec. 27th, 2013 09:07 pmA lazy morning with the calm only broken by a panic over the near-burning of the roast potatoes for lunch. Mere minutes before we were due to arrive, an old schoolfriend I hadn't seen for 6–7 years happened to drop by only to find himself invited to join us. After lunch my uncle and my granny sorted out their remaining packing, waiting out a couple of appalling hail showers before making an early departure for London.
With the unpredictable weather making a walk a chancy prospect, pater & I spent the afternoon trying to debug the downstairs networking. Connected directly to the secondary router, I noticed that it had been configured to use a different subnet to the primary making it inaccessible without additional routing. After correcting this and putting the secondary back in place, we found that we still couldn't ping it or see any broadcasts from it.
Investigating further, we found that the ethernet-over-power adaptor it using to communicate with the primary router seemed to have lost synchronisation. When we replaced it with a properly synchronised adaptor, the router came on-line and ground floor wifi performance improved from a crawl to blindingly fast. Excelsior!
With the unpredictable weather making a walk a chancy prospect, pater & I spent the afternoon trying to debug the downstairs networking. Connected directly to the secondary router, I noticed that it had been configured to use a different subnet to the primary making it inaccessible without additional routing. After correcting this and putting the secondary back in place, we found that we still couldn't ping it or see any broadcasts from it.
Investigating further, we found that the ethernet-over-power adaptor it using to communicate with the primary router seemed to have lost synchronisation. When we replaced it with a properly synchronised adaptor, the router came on-line and ground floor wifi performance improved from a crawl to blindingly fast. Excelsior!