Jump to content

davewantsmoore

Members
  • Content Count

    17,646
  • Donations

    $0.00 
  • Joined

  • Last visited

  • Days Won

    17

davewantsmoore last won the day on April 22 2017

davewantsmoore had the most liked content!

Community Reputation

5,820 Superstar

About davewantsmoore

  • Rank
    Log! It's big, it's heavy, it's wood.
  • Birthday October 16

Profile Fields

  • Location
    Hobart
  • Country
    Australia

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. If you have two seperate networks .... then the only way they can communicate with each other is if a router passes traffic between them. You only want to have one router. If you want two seperate networks to travel down one single cable .... then you need to use "VLAN". Typically you would connect a switch (that supports VLANs) to the end of the cable .... and then all the devices to the switch. My suggestion is similar to Ric. Setup the two subnets using the interface grouping of your router. This will mean that everything (I understand including somethings you don't want) down the "far end of the house" are now on the new network.... That will have to do you for now. Set it up with DHCP or manually assigned addresses, whatever. Now, see what is working (or not). You will need to methodically troubleshoot things. eg. can the IPs on the "audio" network ping each other? Can they ping IPs on the other network?.... can they get to the internet .... etc. etc. Once you have that all working. ie. everything can talk to everything (there might be a number of issues to resolve, before it does) ..... then you can proceed to the next part, which is advertise BOTH networks down the cable to the far end of the house, and have your switch decode the VLAN IDs. I don't know if/how Roon remotes/clients will behave like this ..... if it relies on "broadcast" to find each other ... then it won't work. You may have to manually tell clients about the server, etc. If you engage a professional you want. Two LAN subnets configured on the router VLAN configured on the router and switch A "trunk" setup between the router and switch Specific ports on the switch configured to be one (or the other) LAN This should allow everything to work .... except for anything in one network which relies on "broastcast" to find things (which are in the other network). That will need to be setup manually. ie. on your ipad (or whenever) in the "not audio" network, it won't magically find your Roon player. You'll need to tell the ipad about the roon device..
  2. No. If more traffic than the computer needs to know about is arriving at the computers network port, then the computer needs to "think about it"... which interrupts what it would be otherwise doing (playing music). If someone has a system designed around a computer which is sensitive to such things (extra network traffic interrupting it) .... then it might be a benefit.
  3. If you manually assign an IP to a computer, then it will always "take it just fine".... ie. it won't tell you if it's wrong (it assume you get it right). It just won't work (or work right). I don't understand what you mean. What didn't work? If you manually assigned IPs to the computers, then releasing and renewing does nothing. Did you manually assign IPs to the computer? Have you set it back to "automatic"?
  4. If that's the case, then they'll all need to be in the new (eg. 192.168.2.x) network subnet .... so, defeats the purpose. If you want to do it the way you're describing (one cable linking all the computer at the other other end of the house... but not all on the same network segment) .....then that is where you need to use "VLAN"s.
  5. ... but was the one which was on offer. Who though? ... and how? OPEL in the country? ... with an upgrade beyond ADSL to what? .... and what of the city? Nobody wanted to roll out VDSL on reasonable terms.... so FTTH? HFC? Who would/could agree to do that?... at a price/terms less than what NBN paid? It really is tough one..... we made such a very poor decision re: Telstra. Analysts at the time said it would haunt us for many decades.
  6. Changing the baffle shape will likely need tweaks to driver placement and crossover to make it gel. Changing the tweeter is going to need a whole new crossover design.
  7. I would just put it in a small sealed box, and use a (sub)woofer
  8. I had a play with the nexel drivers used. If the cabinet is the right height for you, and bass output is enough, then I'm sure you won't be disappointed. TG does great work.
  9. Most switches support it. TPLink imply all their gear goes. https://www.tp-link.com/au/support/faq/697/?utm_medium=select-local (This will also provide tips on how to enable it on the PCs)
  10. Ok. I think I have figured it out for your TPLink router. It's difficult not having the device here (so not sure where to tell you to click precisely), and the manual is not particularly helpful. I think Ric was on the right track. Interface grouping (Page 31/32) Try this.... Create a new interface group (Audio) Add one or more LAN interfaces to the group (everything connected to these LAN port(s) will be in the new subnet) Now, under LAN setting, I expect you will be able to setup LAN settings for this new (audio) group. [See the pic on page 32, where it say sat the top "Group = Default" ..... well, get up a page with these settings for "Group = Audio" somehow. Eg. IP = 192.168.2.1, subnet mask = 255.255.255.0, DHCP, you could set this up (or just turn it off, and assign the IPs on the audio computer manually). Then setup the audio computer with IP= 192.168.2.x, mask = 255.255.255.0, and gateway = 192.168.2.1 ... and you should be good to go.
  11. Yes, you almost certainly can. Configure the audio computers to have IP addresses in a new subnet (ie. not inside your existing subnet) Configure your router to pass traffic between the your old subnet and the new one you added (assuming you need that - you likely do) Eg. If you existing network is 192.168.1.x (subnet mask = 255.255.255.0 or /24) .... then put the audio computers on IP addresses in 192.168.2.x (255.255.255.0) .... and set the router up so it knows about these two networks and passes traffic between them. Jumbo? As long as it is enabled in the router/switch .... then it should be as simple as a config setting in your network card on your computers.
  12. Probably..... but to what degree depends on how it's regulated. ie. There's a big difference between a totally lawless monopoly, and one which has to jump through well constructed regulatory hoops (ie. ones which deliver outcomes which are worth trading for said monopoly). ie. not all monopoly is created equal.
  13. I don't agree. "At a fraction of the cost" ..... what magic pudding is this? Yes, lower upfront costs to the taxpayer. Telstra was offering to build the entire NBN at "zero cost", in return for being the "only ISP". So, sure - we could all have FTTN today, with some FTTH at Telstra discretion..... paying Telstra prices for Telstra service quality (whatever that would be). We only have to look at "Telstra Velocity" to see what that would/could be like. Perhaps if the government had of regulated such a project really well ..... then perhaps if could have worked.
  14. It is... from my (admittedly quick) glance at the spec sheet, I would expect the Dayton model to have better performance there.
×
×
  • Create New...