• Registered: 2009-02-02
  • Posts: 547

Topic: Alpha Networking Thread

Taking an idea from alef, here is a thread for any networking issues/answers-to-issues for the alphas, as I'm assuming there will be more than one - hopefully this will prevent the already 10 page long alpha thread from hitting 30 by monday.

----------------------------------------------------------------------

My networking issues: Broadcom wireless card not supported
Solution: thanks to Richs-lxh --> http://crunchbanglinux.org/forums/topic … er-alpha1/  (at least until corenominal adds the support out of the box)

  • Kuno
  • #! Die-hard
  • Offline
  • From: Osnabrück - DE
  • Registered: 2009-01-09
  • Posts: 549

Re: Alpha Networking Thread

First in... smile

So, since i just managed an successful install from usb on my EEE901: networkmanager detects my hardware and wifi connection (router) correctly - but won't connect to the www. On my desktop, nm tells me "Network not found", though i'm on a working cable connection... hmm

Edit: Now after having tried to manually edit the the ip-settings for 10 minutes without succes, now suddenly wifi works with entering a static ip. Btw: Connection is not encrypted, router set to only accept certain MAC-Adresses...

  • From: Rio de Janeiro, RJ, Brasil
  • Registered: 2009-09-21
  • Posts: 31

Re: Alpha Networking Thread

First attempt ...
I need to set up my connection manually, but can not save the configuration because it says I have no privileges. What should I do?
PS: I'm using live cd

Last edited by Luke_Linux (2010-03-22 02:04:58)

Virus? What virus?
  • From: Nowhere, Indiana
  • Registered: 2009-10-17
  • Posts: 288

Re: Alpha Networking Thread

@Kuno

I have been using debian-testing a few weeks and have similar issues with network manager.

my solution:

remove network-manager and use command line dhclient.

if you are hooked up at eth0 then running

dhclient

as root should connect you, and no that wont change the status of network-manager applet it stills shows disconnected.

wireless you just use the iwconfig to essid and then run dhclient and that will do it.

lifes not that much more difficult without an applet or manager. but it would be cool if it worked.

failure is only a negative way to describe a learning experience.
i am constantly learning. smile

monkeybritt's Website

  • Registered: 2010-01-26
  • Posts: 275

Re: Alpha Networking Thread

I don't have any network problems until now, what was different with 9.04 where I had to re-enter the 26 character WPA2 key everytime I booted neutral But that's fixed now for me!:P

I have a Intel WiFi link 5100 which uses the ipw2200 firmware wink

Meh. Interested for a Dropbox alternative? Go to https://launchpad.net/tart
  • Kuno
  • #! Die-hard
  • Offline
  • From: Osnabrück - DE
  • Registered: 2009-01-09
  • Posts: 549

Re: Alpha Networking Thread

Luke_Linux wrote:

First attempt ...
I need to set up my connection manually, but can not save the configuration because it says I have no privileges. What should I do?
PS: I'm using live cd

This message i have on my desktop, but as it (cable-)connects anyway, i don't care so much. But will try monkeybritt's solution.

On eee-pc ESSID was found out of the box, but though nm said "connection established", it did not.
Had to cut the connection first, then nm would accept my changes in ip4-settings. Now it'soK. Don't know about behaviour in a secured
network yet, will have to take my eee to the office to test...

  • From: Deep in The Swedish Woods
  • Registered: 2008-11-28
  • Posts: 578

Re: Alpha Networking Thread

The WNIC on my wifes Eee PC 1001 HA isn't recognized this time either... sad
I will post the hardware specs as I get home tonight.

My artwork at deviantART   |    My Tweet   | My upcoming web page
Nulla dies sine GIMP!
ASUS Eee PC 1000 HE | 2GB | 120GB OCZ Vertex 2 SSD | #! Statler

Zwopper's Website

  • Registered: 2009-03-23
  • Posts: 354

Re: Alpha Networking Thread

Andreas wrote:

I don't have any network problems ...

I have a Intel WiFi link 5100 which uses the ipw2200 firmware wink

Interesting - the debian installer asked me to provide the ipw2200 firmware :-?

Wireless (offcause) didn't work with broadcrap: 

01:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)
03:00.0 Ethernet controller: Attansic Technology Corp. L1e Gigabit Ethernet Adapter (rev b0)
  • From: Minnesota, USA
  • Registered: 2010-03-22
  • Posts: 5

Re: Alpha Networking Thread

SOLVED - http://crunchbanglinux.org/forums/post/60530/#p60530

I am also experiencing networking issues.

My problem is similar to Kuno's first post, though NM shows that I am indeed connected to the (correct) ESSID but Iceweasel is unable to connect to the internet.

Even more strange is that I am able to ping websites and receive replies in the terminal. <ping www.google.com>

I did a quick search of the debian forum and tried a suggestion of switching to WiFiWiz as a network manager, but there are unsatisfied dependancies and synaptic is unable to communicate with the repos.

I have not tried a wired connection yet (that will be tonight) but am very curious why there is an issue.  I have loaded debian lenny on this laptop before and did not have any problem with the iceweasel internet connection (or NM for that matter.)

Seeing as how the connection appears correct in NM and I am able to ping from the terminal I'm sure it is a software issue, but I don't have any experience tracking down and solving issues such as this.

Please note that I have been using #! 10 alpha i686 build loaded to a USB stick using netbootin.  I have loaded the iso into virtualbox, but i have never used a virtualization software before and am having issues passing the network connection through to the VM. 

All of that being the case, I might not have any issue if I install directly to a local hdd. 

All in all, though, the alpha seems to work flawlessly and I am very much looking forward to the stable release.

Last edited by thinner321 (2010-03-23 05:43:42)

  • Registered: 2008-11-25
  • Posts: 4,363

Re: Alpha Networking Thread

thinner321 wrote:

I am also experiencing networking issues.

My problem is similar to Kuno's first post, though NM shows that I am indeed connected to the (correct) ESSID but Iceweasel is unable to connect to the internet.

Even more strange is that I am able to ping websites and receive replies in the terminal. <ping www.google.com>

Have you disabled ipv6 in Iceweasel?

  • From: Minnesota, USA
  • Registered: 2010-03-22
  • Posts: 5

Re: Alpha Networking Thread

omns wrote:
thinner321 wrote:

I am also experiencing networking issues.

My problem is similar to Kuno's first post, though NM shows that I am indeed connected to the (correct) ESSID but Iceweasel is unable to connect to the internet.

Even more strange is that I am able to ping websites and receive replies in the terminal. <ping www.google.com>

Have you disabled ipv6 in Iceweasel?

Thank you very much for the prompt and very sound advise.  I apologize for what was apparently a poorly researched problem on my part.  I was sure that it was something simple.

I will definitely know to try this simple fix in the future. 

In either Iceweasel or Firefox, by typing about:config in the url dialog box and then filtering for "ipv6" the "network.dns.disableIPv6" toggle will be brought up.  After right clicking, selecting "toggle" to change the operator to "true," and restarting all was well and here I am currently posting from the live environment.

I will be installing on a new drive immediately.

  • From: Lost River Lake
  • Registered: 2009-02-19
  • Posts: 514

Re: Alpha Networking Thread

A DNS Server related issue? I have been using Statler Alpha 1 for a few days now on a desktop machine with ethernet connection. The only slight problem [with networking*] I have encountered so far is that I cannot use the nodename when I SSH from my laptop in the home network. That is, "ssh piraja@crunchdebang.local" produces just "ssh: Could not resolve hostname crunchdebang.local: Name or service not known", but "ssh piraja@10.0.0.4" connects with no problem. The same when I try to ping the desktop machine. It's quadruple boot (#! Statler, #! 9.04, Debian Queeze, Windows XP) and the other Linuxes do not have the same issue. So the problem seems to be on the server side, or maybe I'm just missing something. (Yes, I'm sure the nodename/hostname is crunchdebang, from Crunch+Deb+Bang, a.k.a. Crunch DeBang or Crunch De Bang.)
__
[* I haven't been able to configure my Kyocera Mita FS-1010 laser printer either, but that's another issue. Somehow, everything seems to go perfectly with Foomatic-GUI, during the config process (using either the proposed driver or PPD file), but the printer remains as if non-existent.]

Last edited by Piraja (2010-03-23 08:20:07)

I never use smilies, but there are exceptions that prove the rule wink
Now playing: Last.fm
  • Kuno
  • #! Die-hard
  • Offline
  • From: Osnabrück - DE
  • Registered: 2009-01-09
  • Posts: 549

Re: Alpha Networking Thread

Kuno wrote:

On eee-pc ESSID was found out of the box, but though nm said "connection established", it did not.
Had to cut the connection first, then nm would accept my changes in ip4-settings. Now it'soK. Don't know about behaviour in a secured
network yet, will have to take my eee to the office to test...

I have to correct myself here... Wifi connection with wpa is not really stable - in fact most of the time i can't even connect. So i will try to change from nm to wicd like proposed here: http://crunchbanglinux.org/forums/topic … d-for-wpa/

  • Kuno
  • #! Die-hard
  • Offline
  • From: Osnabrück - DE
  • Registered: 2009-01-09
  • Posts: 549

Re: Alpha Networking Thread

Just an update: I manged to get my wifi on EEEPC 901 working in the wpa secured network. Since network-manager did not want to connect at first (though it saw the ESSID ), i followed richs-lxh's advice above and replaced NM with wicd. There i had the same problem as before: ESSID found, but connecting failed. But wicd at least gave me a message like "wrong passphrase". So i started to edit the wifi-router settings: Router-settings were: Security: WPA-PSK, Encryption: TKIP+AES. i Then changed encryption to TKIP only - and bingo!
Wicd connected without a hiccup. I then removed wicd and reinstalled network-manager. NM also connected without problems.
So for me the wifi - problem indeed was an encryption-problem with both wicd and NM.

For this issue:

NM tells me "Network not found", though i'm on a working cable connection

This is solved by editing  /etc/NetworkManager/nm-system-settings.conf and changing "managed=false" to "managed=true" - as proposed by slapfish and papparonny in the alpha-thread. smile

  • Registered: 2009-09-07
  • Posts: 84

Re: Alpha Networking Thread

I have installed Statler Xfce x64 to an AMD Turion x64 Lappie. With the CD install of statler I had my ethernet cable connected. The text install setup the network fine - so it said. I finished the install w/o a hitch. Then came up to desktop @ first boot, no wireless network seen (no wireless card driver installed?) but also no wired connection. I did what Monkeybritt mentions above - used dhclient, which gave me a connection. Then used synaptic to uninstall network manager and install wicd. Wicd allows me to connect to the wired network automatically. I also went ahead and installed the broadcom-sta-common package and rebooted. But still no wireless detected.

So the question is, how do I get Statler to recognize my wireless card, install it and get my wireless connect up? If no one has a clear fix for this in Alpha1, then an explicit workaround using Monkeybritt's solution above would be great. His comment:

wireless you just use the iwconfig to essid and then run dhclient and that will do it.

sounds cool, but I don't know how to apply it. In addition, I can't find iwconfig. I installed iw, but don't know how to use it. So if the workaround is necessary, can someone help me with more explicit instructions.

Thanks
   
    Peace

  • Registered: 2009-09-07
  • Posts: 84

Re: Alpha Networking Thread

Well, I got it working by using these instructions:
http://crunchbanglinux.org/forums/topic … er-alpha1/
The solution @ the top of the thread got my rig to use wicd and get a signal, but it had to be redone @ reboot.
So I posted a workaround @ the 10th post of the above thread. Perhaps it might work for someone else too.

Peace

Last edited by tshann (2010-03-26 07:46:27)

  • From: A narrowboat, English canals
  • Registered: 2010-01-23
  • Posts: 52

Re: Alpha Networking Thread

Corenominal

Can we include madwifi (or at least ath5k) on the list of drivers for future releases.

I have now compiled it for my pcmcia Atheros card but had to download 40mb of Linux Headers to do so. On my 10 year old Compaq Presario 1200 with only 6GB HD, that's a little too much. Out of the box functionality is one of the good things about !#.

Yes, I know it's only alpha 1.0, but we have high expectations.

Dan

Dan
  • From: Arizona
  • Registered: 2009-03-21
  • Posts: 15

Re: Alpha Networking Thread

so far everything is working here, my wireless is detected out of the box using wpa and wpa2 , but I had to remove network manager and install wicd using synaptics, because I was getting disconnected every 5 minutes or so using network manager, my wireless usb's adapters were recognized out of the box, I am using linlsys wusb-54gc, and like I said , it works out of the box

jessie

For everyone else, the pain of transformation is the sharpest memory they have of their human life. I remember nothing of being human.
  • From: Santa Fe, NM, USA
  • Registered: 2009-09-14
  • Posts: 1,349

Re: Alpha Networking Thread

I don't have a 'networking' question, just a great networking comment.

I use 2 USB Modems . . . usually.

The older one, I've has for about 2 years now ... it works with every Linux distro in the world.  Outta the box.

The newer is a Cricket A600 USB Modem requiring the installation of the 'usb_modeswitch' ... doesn't work with many distros, as some of the older kernels do not support these yet.
There are several fix-it/work-arounds in several Forums (Arch, Mint, Ubuntu, and Ubunutu-Geeks) With help from these is how I've managed to get this Modem working.

Well, I don't know what made me try it in Statler . . . the A600 USB Modem worked ... outta the box.  No 'usb_modeswitch' ... it just works!!!

Registered Linux User: #497030
LinuxMint Forum | DeviantART page | Lost-in-the-Box Forum  |  Ask.Debian
#!Crunchbang 'Statler' (Openbox) -- LinuxMint-Debian-Fluxbox Edition
  • semog
  • #! Member
  • Offline
  • From: Portugal
  • Registered: 2010-03-23
  • Posts: 53

Re: Alpha Networking Thread

i have a litle problem but just solved with broadcom b43-fwcutter driver

but  now i can make my dell 1510 b/g/n work based on broadcom 4322 that need broadcom sta driver but i just compile install and nothing work so someone can help me solve this?

  • From: Lost River Lake
  • Registered: 2009-02-19
  • Posts: 514

Re: Alpha Networking Thread

Quoting myself from a few days ago:

Piraja wrote:

A DNS Server related issue? I have been using Statler Alpha 1 for a few days now on a desktop machine with ethernet connection. The only slight problem [with networking] I have encountered so far is that I cannot use the nodename when I SSH from my laptop in the home network. That is, "ssh piraja@crunchdebang.local" produces just "ssh: Could not resolve hostname crunchdebang.local: Name or service not known", but "ssh piraja@10.0.0.4" connects with no problem. The same when I try to ping the desktop machine. It's quadruple boot (#! Statler, #! 9.04, Debian Queeze [sic], Windows XP) and the other Linuxes do not have the same issue. So the problem seems to be on the server side, or maybe I'm just missing something. (Yes, I'm sure the nodename/hostname is crunchdebang, from Crunch+Deb+Bang, a.k.a. Crunch DeBang or Crunch De Bang.)

Well, since I realized that Conky was having intermittent "problems getting a response from 'localhost' on port 6600", I just tried changing the lines in /etc/hosts from the initial

127.0.1.1 localhost
127.0.0.1 crunchdebang.home.network      crunchdebang

to the following single line

127.0.1.1       crunchdebang.home.network       localhost crunchdebang

and that solved both the Conky/MPD issue and the name server issue; now I can SSH from my laptop to the desktop machine (crunchdebang.local) in my home network.

Last edited by Piraja (2010-04-01 14:33:04)

I never use smilies, but there are exceptions that prove the rule wink
Now playing: Last.fm
  • Registered: 2009-03-23
  • Posts: 354

Re: Alpha Networking Thread

I have noticed that ipw2200 seams to crash sometimes (not sure about the frequency, because this is just at testing machine I use infrequently - mostly as a media server).

Symptom: All of a sudden I can't connect to the network. /var/log/messages says:

Apr 17 21:28:49 crunchbang kernel: [32042.718094] ipw2200: Firmware error detected.  Restarting.

But the restart apparantly doesn't solve things.  -Any ideas?

  • Registered: 2009-03-23
  • Posts: 354

Re: Alpha Networking Thread

Yes ^ happens quite often. Again today anyways. It might be related to some torrent traffic that the computer redirects to a slow(!) samba share? Does anybody knows what might be going on? Is it just the firmware (ipw2200) that is errorprone?