Language Selection

English French German Italian Portuguese Spanish

a simple network question

Filed under
Hardware

Hello Forum!

I have a simple network question. I have a Linux Distribution on a lapton and I have the network hardware ready so so that I can connect to the internet. I already have a computer connected to the internet. So I suppose in order to have two computers I need some sort of hub device. Can anyone offer a suggestion about this?

Hub

So I guess I can just go to my local electronics / computer parts store and buy a hub. I wonder if my internet service provider needs to be informed about all this.

re: hub

A hub won't work if you only get 1 public IP from your ISP.

As mentioned, you probably need a cheap cable/dsl firewall (hard to tell exactly since you don't give the details of your existing setup).

Not only does that do the NAT (so you can have numerous private IP's and only 1 public IP) but most come with both a WAP and wired ports. For a few bucks more, you can get one that does SPI, which adds a layer of protection to simple NAT'd firewalls.

I wouldn't obsess over the brand, all the cheap ones (i.e. $40-$80) perform pretty much the same functions and for that price - anything over a year of 24/7 operation is bonus time in my book.

re: hub

well, a hub would work if he wanted to do masqing and forwarding through his desktop. Set up dhcpd or use static internal ips... even a crossover cable would work for connection sharing if he's trying to get by real cheap.

But yeah I agree the best advice is to get a router with the built in firewall and forwarding stuff. As stated, I'd suggest a wireless router so he could fully enjoy that laptop.

Get a router

It's unclear from your initial post whether you

- want to configure the computer you already have connected (to...what...a cable modem?) to share your Internet connection with other computers (which would also require two NICs in that PC, right?) or
- if you're just looking for the easiest way to connect your (let's assume) cable modem to more than one computer.

Getting a router, connecting your cable modem to it, and then connecting multiple computers to the router's ports would be the easiest solution (unless you know or want to learn how to configure a computer to act as a router).

Plus you'd get the benefit of the router acting as a firewall, since they usually do NAT. And Internet connection setup would also be very easy, since routers usually do DHCP.

(My experience with Netgear is good. I have an old (out of production) Netgear RP114 that's been solid. When we got wireless laptops, I bought a (ubiquitous) Linksys WRT54G to replace it, but found that the Linksys choked on bittorrent traffic, which caused me to have to frequently reboot the cable modem. So now the Linksys is plugged into the Netgear and is acting as a switch.)

As long as you've just got a half dozen computers or less on a home network with a broadband connection, you usually don't have to tell your ISP. But read your TOS to be sure.

(I defer to Susan. She's got way more experience than me.)

- Andrew

re: network question

Well, if you're going to do the firewall/forwarding from the desktop, a hub would work - or even just a crossover cable and another nic. But if you'd rather let the new device do the forwarding, then get a switch. Most have a firewall built in that will forward traffic to and from your cable or dsl modem. Any good commercial switch will work. In fact, if it's a laptop, you might even prefer to get a wireless router (which have rj-45 slots for your desktop).

I've had some bad experiences with netgears, in that they don't seem to last long. dlink and linksys are pretty good I reckon.

More in Tux Machines

Security Leftovers

  • Someone is putting lots of work into hacking Github developers [Ed: Dan Goodin doesn't know that everything is under attack and cracking attempts just about all the time?]
    Open-source developers who use Github are in the cross-hairs of advanced malware that has steal passwords, download sensitive files, take screenshots, and self-destruct when necessary.
  • Security Orchestration and Incident Response
    Technology continues to advance, and this is all a changing target. Eventually, computers will become intelligent enough to replace people at real-time incident response. My guess, though, is that computers are not going to get there by collecting enough data to be certain. More likely, they'll develop the ability to exhibit understanding and operate in a world of uncertainty. That's a much harder goal. Yes, today, this is all science fiction. But it's not stupid science fiction, and it might become reality during the lifetimes of our children. Until then, we need people in the loop. Orchestration is a way to achieve that.

Leftover: Development (Linux)

  • Swan: Better Linux on Windows
    If you are a Linux user that has to use Windows — or even a Windows user that needs some Linux support — Cygwin has long been a great tool for getting things done. It provides a nearly complete Linux toolset. It also provides almost the entire Linux API, so that anything it doesn’t supply can probably be built from source. You can even write code on Windows, compile and test it and (usually) port it over to Linux painlessly.
  • Lint for Shell Scripters
    It used to be one of the joys of writing embedded software was never having to deploy shell scripts. But now with platforms like the Raspberry Pi becoming very common, Linux shell scripts can be a big part of a system–even the whole system, in some cases. How do you know your shell script is error-free before you deploy it? Of course, nothing can catch all errors, but you might try ShellCheck.
  • Android: Enabling mainline graphics
    Android uses the HWC API to communicate with graphics hardware. This API is not supported on the mainline Linux graphics stack, but by using drm_hwcomposer as a shim it now is. The HWC (Hardware Composer) API is used by SurfaceFlinger for compositing layers to the screen. The HWC abstracts objects such as overlays and 2D blitters and helps offload some work that would normally be done with OpenGL. SurfaceFlinger on the other hand accepts buffers from multiple sources, composites them, and sends them to the display.
  • Collabora's Devs Make Android's HWC API Work in Mainline Linux Graphics Stack
    Collabora's Mark Filion informs Softpedia today about the latest work done by various Collabora developers in collaboration with Google's ChromeOS team to enable mainline graphics on Android. The latest blog post published by Collabora's Robert Foss reveals the fact that both team managed to develop a shim called drm_hwcomposer, which should enable Android's HWC (Hardware Composer) API to communicate with the graphics hardware, including Android 7.0's version 2 HWC API.

today's howtos

Reports From and About Cloud Native Computing Foundation (CNCF)