In any case it lead to 'route flap' as the PC swapped between the two signals interminably.
Now I have three ssids on the three furthest apart channels and let the device pick the strongest. Mostly it does, since the places I am in tend to favour one over the other two, massively.
I live somewhere with no cat5, wifi propagation is a bit lacking, and every room is going through a separate MCBO (so powerline is going to be slow). However there is CT100 from every room to an aerial amp in the loft.
My current plan is to run Bonded MoCA ethernet-over-coax which coexists with DVB-T by using the same bit of spectrum as satellite would do. It's popular in the US with cable TV companies, but not popular over here.
I bought a couple of these gigabit adaptors:
formatting link
but I'm going to return them and order some of these 2.5Gbit versions:
formatting link
they get more stock (8-10 weeks they said).
They work a bit like ADSL - the box filters off TV to one port, and then presents ethernet on an RJ45. It behaves essentially like shared-medium ethernet. For the coax you need a F-type splitter and a filter to stop the power backfeeding into the aerial amp.
It looked similar. I think I remember it being brown and was a 19" 1U RM unit (I took the ears off and had it on a shelf, high in the Customer Service office as it was central to the building).
D-Link or Netgear but for some reason Allied Telesis comes to mind?
It would automatically isolate a badly terminated segment so that protected the rest of the company from someone thinking it was ok to play with the cabling etc (like adding an extension to the T piece to move their PC across the room). <rolls eyes>
The first network I installed used vampires and eight port vampire hubs.
An Intel NRM.
The ethernet cards were a pair of multibus (IT) cards.
I had 2500m of yellow cable manufactured in the UK as there were no suppliers and the company wanted a minimum order to tool up.
It all worked very well even though the cable was hung out of a window across to the roof of an adjacent build for a while while underground ducts were built.
It didn't run TCP/IP, that didn't exist except in labs at the time.
I'm sure people here have above the average number of interlinked smoke detectors.
wired interlinkeds have to be on the same circuit as otherwise there'd be leakage between different circuits from the voltage on the interconnect wire.
Solwise do leaky feeder cable where you can put 30 - 50 metres of feeder of coax onto an access point and the whole cable becomes an access point, so you can then use devices so many metres from the cable.
ideal if you have a long narrow house/garden or tunnels
I had a segment running 10Base5 off the AUI port on the repeater. As you say, both vampire taps and properly terminated ones down a corridor (in the roof space) and AUI drop cables going either way to AUI ports on the back of the Combi NE2000 (compatible) cards. ;-)
Pioneering days. ;-)
I went to such a temporary install that stayed out there too long and was hit by lightening (or impulse noise at least), taking out one of our Muxes.
NetBIOS was one of the fastest protocols for local networks (lowest overhead), something many visitors to out site commented on. Then I built and installed a Netware server so added IPX/SPX and only later included TCP/IP when we stared adding various gateways and let the Unix boys play on our LAN. ;-)
I feel very lucky in my career. I was into electronics when The Post Office needed electronic service Techs. I was working as a Datacomms Field Support Tech when modems and Leased Lines between offices were the norm, then Kilostream / ADSL / X.25 / Frame Relay etc.
Then when running the Co customer 'Help Desk' I was also given the task of bringing the Co up to speed with it's IT / internal Network (installing one ... and building the PC's and servers etc) and did so, mostly in my own time after work and out of my own interest. ;-)
As long as I looked after our customers and the local (and remote [1]) staff, I was pretty much left alone to do my own thing. ;-)
I was later able to make use of some of those experiences via IT training.
Cheers, T i m
[1] That ended up going International as all the other (and Head!) offices wanted to join 'our' MS Mail system. ;-)
You can get round that a bit by enabling fast roaming on the APs if they support it. It allows caching of credentials and makes handovers much faster to different APs. Some also have a mechanism for an AP to boot a client off if the link quality is suffering.
No indeed and also of course there is not very much between a mains supply and the sensitive bits of your computer and interface bits. Somebody I know had one go rogue and blow up a computer on board Ethernet chip. I blame the Chinese! Brian
HomeOwnersHub website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.