My home network is
Submitted by ajt on Sun 13 Jan 2008
| Switched Ethernet |
![]() 57% | 915 votes |
| Ethernet over mains power circuit |
![]() 0% | 15 votes |
| WiFi |
![]() 15% | 248 votes |
| The Neighbour's WiFi |
![]() 5% | 84 votes |
| Floppynet |
![]() 0% | 3 votes |
| Mixture |
![]() 18% | 288 votes |
| Don't have a home network |
![]() 2% | 39 votes |
| Total 1595 votes |
When a friend brought a notebook with WiFi round once, it picked up three open networks that overlapped on my house...
--
"It's Not Magic, It's Work"
Adam
[ Parent ]
Sometimes I connect other machines to my network, e.g. guests with their laptops, so they can access internet. Sometimes I connect a second network to my machine.
But most of the time, the simple setup suffices. If I need more machines within my network, I use Xen.
I am looking for a solution to replace the workstations with thin clients, but I didn't find machines yet, that fit my ideas.
cb
[ Parent ]
The TV box uses ethernet over powerline to reach the router.
Cheers,
Julien
[ Parent ]
sno
[ Parent ]
i have two wired networks (1500 mtu fast ethernet & jumbo-frame gigabit ethernet) and a wifi network.
the wifi network was originally to accomodate not punching holes in an apartment, but even after relocating all computers to a single room it was still used just because "if it ain't broke, don't fix it". now the wireless network accommodates an internet tablet and the occasionally laptop.
the wired network is a bit complex hardware-wise because i insist on using jumbo frames on the gigabit network and most of the "embedded" fast ethernet hardware (router, ap, printer) isn't jumbo-capable, so there are two networks, jumbo/gigabit & 1500mtu/100Mb, and jumbo-capable computers are dual-homed (necessitating two nics & patch cables per computer, and two switches, one for each network).
i investigated vlans, where the plain network would be 1500 mtu with jumbo frames encapsulated in a vlan (hopefully disregarded by the non-jumbo, non-vlan hardware), but through experimentation in linux you apparently can't have a vlan with a larger mtu than the underlying lan. so one of these days i'm going to spend the money for an intelligent switch, assign by port all the non-jumbo hardware to a 1500 mtu vlan, allow the jumbo-capable boxes to do their own vlan tagging (to talk to both networks), and consolidate this hardware/wiring mess.
does anybody know a better/simpler/different/creative approach to allowing both 1500 & 9000 mtu?
[ Parent ]
I also think at least OpenBSD can sneakily fragment IP packets when bridging between two ethernets with different MTU. IMO having 2 different subnets is a simpler and better way (useless fragmentation loses some bandwidth).
You must already be running different subnets in them anyway, or have some very weird routing setup in your machines.
This will, of course, not work if you want protocols other than IP... but who does? And even then you could tunnel the smaller MTU ethernet within the jumbo ethernet without any real loss, since tunneled 1500 byte packets nicely fit in 9000 bytes with no fragmentation.
[ Parent ]
[ Parent ]
If it wasnt for the fact that I had to run cables and drill into the front room it would be cabling throughout ...
Works ok though when the neighbour is not trying to hack my wifi!!
[ Parent ]
[ Parent ]
I'll eventually get the wife into Linux. The in-laws are a lost cause.
[ Parent ]
[ Parent ]
The ethernet cords break several fire codes in my office, I have no doubt...I haven't detangled them in ages.
[ Parent ]
I procrastinated my choice, as I have various bits of networking hardware, but I'm very impressed with the rfc2549 QoS extensions that I patched over my existing rfc1149 IPoAC homing network.
However, as a redundant local link, I also have some tins and a few bits of string. Then of course, there's always the girlfriend yelling from the other side of the house :-D
Cheers.:wq
[ Parent ]
Regards,
Matthias
[ Parent ]
[ Parent ]
"Beautiful thing, the destruction of words." - Orwell
[ Parent ]

57%