Linux may be losing this average Jill

[nishtya]

http://www.knoppix.net/forum/viewtop...?p=59647#59647

To get cable up and running the score:
Windows 98SE - five minutes (includes reboot but not including time to find mobo CD)
Linux - 4 hours, burnt dinner and a pounding headache

I can no longer imagine I am going to be able to network this PC and my other without heavy duty tranquilization. The thought of throwing a router into this mix and another computer with a different nic and a different distro. YIKES. Not to mention I am toying with the idea of wireless so I don't have to fish a wall? I don't think I can do what needs to be done in linux, I have been messing about with linux for quite a few months now but there is no way I think I am going to be able to do this. In my wildest nightmares, how many hours (or days?) will it take me to network?

[CrashedAgain]

http://www.knoppix.net/forum/viewtopic.php?p=59647#59647

To get cable up and running the score:
Windows 98SE - five minutes (includes reboot but not including time to find mobo CD)
Linux - 4 hours, burnt dinner and a pounding headache

I can no longer imagine I am going to be able to network this PC and my other without heavy duty tranquilization. The thought of throwing a router into this mix and another computer with a different nic and a different distro. YIKES. Not to mention I am toying with the idea of wireless so I don't have to fish a wall? I don't think I can do what needs to be done in linux, I have been messing about with linux for quite a few months now but there is no way I think I am going to be able to do this. In my wildest nightmares, how many hours (or days?) will it take me to network?

It appears from your other post that you now have your netcard working (I think). The router should be easy, at least in my case it just worked, I didn't have to set up anything. I don't have wireless, I have seen some posts that indicate it may not be so easy.
Once you have both computers able to internet through the router, networking is a piece of cake. You have to start ssh on both machines (Knoppix->Services->Start SSH services) then just type 'fish://<username or root>@<other machine ip address>' (eg:[email protected]) in konqueror & you should be rewarded with a request for the other computer's password, then be connected to the other machine.
see this post:
http://www.knoppix.net/forum/viewtopic.php?t=12327

Unfortunately, you are right about the hours of searching, burnt dinner & headaches. It took me a year to stumble across the 'fish://' solution. Linux (& KDE) really needs better organized and searchable help files.

Windows was not easy either. It took several weeks to get my two computers connected using windows "Direct Cable Connection" & I never did get it working right. The final straw was interference from some file in my over-bloated HP 990C printer driver (40Megs for a printer driver!!) which killed the DCC connection. So score one for Linux.

[mzilikazi]

http://www.knoppix.net/forum/viewtopic.php?p=59647#59647

To get cable up and running the score:
Windows 98SE - five minutes (includes reboot but not including time to find mobo CD)
Linux - 4 hours, burnt dinner and a pounding headache

Turn oven down to a lesser temp so it cooks slower and drink a good French wine. ok ok......

I can no longer imagine I am going to be able to network this PC and my other without heavy duty tranquilization. The thought of throwing a router into this mix and another computer with a different nic and a different distro. YIKES. Not to mention I am toying with the idea of wireless so I don't have to fish a wall? I don't think I can do what needs to be done in linux, I have been messing about with linux for quite a few months now but there is no way I think I am going to be able to do this. In my wildest nightmares, how many hours (or days?) will it take me to network?

Don't fret networking. A router is easy to set up and has absolutely nothing to do with your operating system. Ideally your wireless router will also have RJ45 (wired) ports.

What kind of connection do you have? (A)DSL, Dial-up, Cable, ISDN, Satellite?

Over simplified it's like this; Your Internet connection goes to the router. The router says "hmm, this packets is addressed to computer 192.168.1.100, and this one belongs to 192.blah blah blah......... and that's all it does in regards to routing. Now also there is the hardware firewall where you decide what ports to open and which to close. Ideally your ports will show as "steallthed".

Most routers have a web based interface for configuration. Simply point your browser to the URL provided in the manual. Usually something like: http://192.168.1.1/

K.I.S.S. Don't try to have an instant multi-machine LAN. Connect the router and then connect one machine. Do it with CAT5 cable. Get one box working. Go from there and add another box and then go for the wireless connection on one one machine. (this is addressing the headache issue again). Of course post your questions or problems here. There are lots of networking gurus that frequent this forum.

Linux & wireless. Those silly manufacturers (I'd rather call them something much worse than silly) don't make it easy. Attempts have been made to provide compatibility lists for wireless cards and Linux but........

1) These lists are compiled from emails, posts, etc. from users. I bought a card listed as 'works perfectly out of the box' and it did. Problem was that WEP didn't. Well the poster apparently didn't feel that was an issue.

2) Blasted manufacturers change chipsets on us all the time. A card model 123.blah might have a Prism2 chip today and an Atheros tomorrow with no model number change. What's more it is often difficult to know which chipset you're buying due to:

a) Mail order
b) Card design (cannot see the chipset)
c) Idiot salesperson.

Watch out for SSF (Short Serial Flash) cards. What's that? The chip has no firmware stored on it. It must be loaded everytime you boot. Sure, that makes for easy firmware upgrades but..... it's more complicated to configure and by no means do they work any better (or easier) than other cards.

Some cards work with Linux by using a 'wrapper' around the windows driver. I.E. driverloader and ndiswrapper. This may be an alternative.

I hear alot of good things about USB wireless.

One of the best resources I've seen for networking is here.

Suggestion:

Take a Knoppix cd (if they'll let you boot it), a Linux laptop or maybe even your own pc to the store to test the wireless card before buying. Maybe you have access to a store with liberal exchange policies.

Fret not, you'll do fine. I'll shut up now.......

[nishtya]

thanks but I am going to hold off on the networking for a bit. This took a lot out of me. I was eyeing my direct x games I couldn't play online because I had been on dialup. And here I am with windows go zoomzoom internet. Tempting. Much more fun than battling every evening with this sort of stuff.

I have linux up on the cable although I am not really comfortable about how it is configured, it just doesn't seem right. Know what I mean? That fix is way too obscure. Oh, I did do shields up. Dead stealth in windows due to zonealarm but I flunked in linux. Port 1024 open. Any ideas? I use guarddog to configure iptables because I am hopeless at understanding the chains, bows arrows, whatever

[mzilikazi]

I have linux up on the cable although I am not really comfortable about how it is configured, it just doesn't seem right. Know what I mean?

Ummm actually no....I don't Tell us.

[eco2geek]

Nishtya: I don't believe you're going to ditch Linux for a second. You've been bitten by the bug; you've put a lot of work into it. Face it: you're hooked.

Dunno anything about configuring wireless (plenty out there who do, though), but a router that uses DHCP and NAT (network address translation) doesn't require you to do any more configuration in Linux than it does to get a cable modem connection going.

Graphically, mine sort of looks like this:

Cable modem ---------> Router --------------------> Ethernet card in computer
xxx.xxx.xxx.xxx -------- 192.168.0.1 --------------- 192.168.0.x
(IP assigned by ISP) -- (internal IP of router) --- (IP assigned by router using DHCP)

You must remember to change the administrator password on your router. There are books on home networking out there that list the default passwords of popular SOHO routers.

I just installed BH7a on a new partition, and couldn't get Internet access. Come to find out that eth0 is now the firewire port, and eth1 is my ethernet port (thanks, Kano). Almost tore some hair out over that.

[gowator]

I have to agree with every last thing mzilikazi said.

Networking and linux are a perfect pair.

Some golden rules.... if you want to run an ethernet network or use a TCP/IP protocol then use a ethernet card.

70% of real linux networking problems are USB modems....
The other 29% are issues with WiFi and lack of config tools which is basically a legislation issue from the USA.

1% are real problems with the NIC .... or its too new.

The rest of the problems are usually ... user created.

Windows users expectations of networking are very weird in *nix terms. The idea of browsing the network and using CIFS/Samba stuff is just something Windows users viewed as networking...

linux is far more down to earth.... if you wanna set the system clock or sens X windows its all the same ..whereas windows makes everything complicated and then sticks a GUI over the top for some things that hide how complex it all is.


eco2geek: yep thanks kano!
I wasted 30 minutes getting networking up.... then ran netcardconfig and chose eth1.... (firewire was already finding itself as a NIC in BH6 btw)

however I cant see how anyone who understands a bit of networking cant do this...


nishta: If you are trying to fdo this from a liveCD then its hardly permanant and if you are using a HD install then the standard knoppix one is NOT the standard linux way, certainly not the standard debian way...

If you want to do this I would use kanotix or a Debian install.

Which one would depend on how you wanna upgrade or not....
Kano has a new BH monthly and BH = bug hunter, the idea is to install and test....
A stable woody install of debian would just sit and work...
only change what you need when you need to (like adding wifi support) and it will probably be easier...

settle down and decide if you wanna reinstall monthly or once a year?

[j.drake]

Networking and linux are a perfect pair.

Surely you must be joking! (at least w/r/t wlan)

I find (Knoppix, anyway, don't know about other flavors of linux, but I expect they're worse) to be INCREDIBLY weak when it comes to wlan card detection. Take a look at the buglists, and figure out what percentage are attributable to failure to detect wlan cards (armchair guess - probably close to 25%, but I'm not going to take the time to count). I know that I posted one bug for the 2004-05-17 release, that is still unresolved (haven't even bothered to post it to the 2004-08-16 list until they catch up with, or at least acknowledge, the earlier lists). Take a look at the networking forum - my bet is that it's about 50% wlan card detection and config problems. If you're really a stat junkie, what percentage of those are still unresolved?

Thank goodness I use wired ethernet. I tinkered around with a Microsoft 802.11b card in a laptop, becuase I was going on vacation and thought it would come in handy. Tried it with Knoppix - it said it couldn't find the prism2 drivers in a certain folder. When I posted the problem here , I got maybe one reply from someone who basically told me that I should know better than to use a Microsoft product with Linux, implying some kind of conspiracy in marketing the cards (not one of the more thoughtful responses I've seen here). Looked for the drivers on the web, and found out that prism 2 is one of the more popular wlan chipsets, so there's really no excuse for this. Did some poking around and FOUND the driver on the Knoppix disk (it was in the kernel 2.4 branch, but the startup was looking for it in the 2.6 branch, because I was booting 2.6). Tried to boot 2.4, but it didn't boot at all. And since I'm not doing a hd install, there's not a whole lot of editing that will solve this problem. (BTW, this issue remains my poster child for why it is a mistake to have two kernels in one release - too hard to keep things sorted our without error).

AY, CARAMBA!!! I'm with Nishtya - who needs this aggravation?? Fortunately, I didn't need the wireless card OR Knoppix on my vacation (Windows performed flawlessly), and, like I said, my home setup doesn't use wireless. So I blew it off as one of those things that Windows can do that Linux can't (and to be fair, there are a lot of things Linux can do that Windows can't - don't mean to imply that either is necessarily better overall, but everything I've seen leads me to believe that wlan is not exactly Knoppix's finest acheivement).

Anyway, Nish, I'm not saying that someone here couldn't get it working for you, but I bet I could fish those wires for you a lot faster than someone could solve your Knoppix wlan problem!! (no, that's not an offer!)

jd

[gowator]

Surely you must be joking! (at least w/r/t wlan)

OK 25-29.... -ish....

70% of real linux networking problems are USB modems....
The other 29% are issues with WiFi and lack of config tools which is basically a legislation issue from the USA.

The problem is the FCC rule that says 'the user must not be able to change the power level' which unfortunately means not open sourcing the driver and needing closed source firmware....

its really a unhappy coincidence and obviously not meant to do this but the effect is to hold back wlan detection....and proper config and leave developers almost guessing....

several of the manufactuerers want to release the drivetr specs but can't ....

Its not really fair on knoppix to blame knoppix....

For the lack of driver in 2.6 for the prism I understand the problem but again if you did a HD install it might work which is what I was saying earlier..about using kanotix...then you can set it up permanantly.

Some golden rules.... if you want to run an ethernet network or use a TCP/IP protocol then use a ethernet card.

perhaps thats not clear enough but I should have said ethernet or fast ethernet.
Wifi Emulates ethernet but its NOT ethernet.
So I was saying implicitly the same as you....

[champagnemojo]

Kanotix contains wireless drivers not included with Knoppix. It picks up my acx-100 based card at boot-up....though I haven't really bothered trying to configure it yet (I only have wireless access at work and have never needed wireless here...but I got the card for $5 after rebate so I figured what the heck). Anyways though, find out what drivers are in Kanotix and what cards are well-supported and I don't imagine it would be too much of a hassle. If you insist on wireless that is.