You are not logged in.

#1 2007-01-19 21:31:04

jaxx
Member
From: Estonia ;)
Registered: 2006-11-06
Posts: 17

A problem with Network

Hello!

I have tried a lot how to connect to the internet with arch but i can't do it. I have a computer with Arch and Windows. I have two computers which connect to the internet through a D-Link DI-604 Router, With widnows XP i have no problems to connect to the internet but with Arch i can't.

rc.conf
i dont exactly remember if some were in quotes and some were in the (), but i know the values
lo = "127.0.0.1"
eth0="dhcp"
INTERFACES=(lo eth0)

gateway="default gw 192.168.0.1"
ROUTES=(!gateway)

I also deleted the ! sign in front of the gateway but still nothing.


Excuse my English...

Offline

#2 2007-01-19 21:47:14

YscO
Member
From: Netherlands
Registered: 2006-06-25
Posts: 52

Re: A problem with Network

Can you post the output of the following command:

ifconfig -a

Offline

#3 2007-01-19 21:51:16

pauldonnelly
Member
Registered: 2006-06-19
Posts: 776

Re: A problem with Network

The first thing to do is run "ifconfig eth0". Assuming your interface is actually named "eth0", this will give you some information about it. If there is no inet address then there's something wrong with it's dhcp attempts. If the word UP does not appear in the output (or if running simply "ifconfig" does not list the interface) then it is not enabled, and you'll have to enable it before you can use it. I think it will be disabled on boot if dhcp is failing.

If the interface is up and has an address then ping your router. If you get replies back from it then the problem most likely lies with your gateway setting. Does it actually lie at that address?

Offline

#4 2007-01-19 22:06:09

lilsirecho
Veteran
Registered: 2003-10-24
Posts: 5,000

Re: A problem with Network

I suspect that the system in use may be static IP for the other computers.  If so, dhcp will fail in the arch install.


Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!

Offline

#5 2007-01-19 22:19:43

jaxx
Member
From: Estonia ;)
Registered: 2006-11-06
Posts: 17

Re: A problem with Network

i jsut did the ifconfig -a and got this if there has to be something before this what i write then i could't see it and i don't know how :oops: :
eth0
       Link encap: Ethernet HWaddr:00:0F:EA:61:37:1A
       BROADCAST MULTICAST MTU:1500 Metric:1
       RX packets:1 errors:0 dropped:0 overruns:0 frame:0
       TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
       collisions:0 txqueuelen:1000
       RX bytes:60 (60.0 b) TX bytes:0 (0.0 b)
       Interrupt:19 Base address:0x4000

eth1
       Link ancap:UNSPEC HWaddr 00-0F-EA-00-00-61-5F-82-00-00-00-00-00-00-00-00
       BROADCAST MULTICAST MTU:1500 Metric:1
       RX packets:0 errors:0 dropped:0 overruns:0 frame:0
       TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
       collisions:0 txqueuelen:1000
       RX bytes: 0 (0.0 b) TX bytes: 0 (0.0 b)

lo
       Link encap: Local Loopback
       inet addr:127.0.0.1 MASK 255.0.0.0
       UP LOOPBACK RUNNING MTU:16436 Metric:1
       RX packets:0 errors:0 dropped:0 overruns:0 frame:0
       TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
       collisions:0 txqueuelen:0
      RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

And i check ifconfig eth0 and that gave me these results:
eth0 Link encap: Ethernet HWaddr:00:0F:EA:61:37:1A
       BROADCAST MULTICAST MTU:1500 Metric:1
       RX packets:1 errors:0 dropped:0 overruns:0 frame:0
       TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
       collisions:0 txqueuelen:1000
       RX bytes 60 (60.0 b) TX bytes 0 (0.0 b)
       Interrupt:18 Base address:0xe000

EDIT: Emm static IP is the ip which changes everytime when you connect to the net? i allways forget which one's which
EDIT2: Oh yeah and do i have to have anything in the rc.conf in the MODULES:() Section ?????


Excuse my English...

Offline

#6 2007-01-19 22:36:36

lilsirecho
Veteran
Registered: 2003-10-24
Posts: 5,000

Re: A problem with Network

DHCP changes every time you connect to the internet.(Dynamic big_smile)

STATIC IP means it is static...never changes.

You cannot mix the two through a STATIC IP established system.


Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!

Offline

#7 2007-01-19 22:46:35

jaxx
Member
From: Estonia ;)
Registered: 2006-11-06
Posts: 17

Re: A problem with Network

Hmm
Oook The ISP sends the router everytime when the router connects a new ip, and the ips for the computers are allways the same 192.168.0.110 for me so how should i configure the rc.conf Network section???


Excuse my English...

Offline

#8 2007-01-20 02:25:09

lilsirecho
Veteran
Registered: 2003-10-24
Posts: 5,000

Re: A problem with Network

It seems it should be:

  eth0="dhcp"

This assumes the gateway you have listed is the correct gateway for your system.

In my system, my ISP has assigned a staticIP and a gateway together so I am required to ID my IP and my gateway in arch at the eth0 entry and gateway entry.

I am not certain that you need a gateway with DHCP.

I see two eth0 and eth1.  Perhaps eth1 could be useful.


Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!

Offline

#9 2007-01-20 12:50:58

jaxx
Member
From: Estonia ;)
Registered: 2006-11-06
Posts: 17

Re: A problem with Network

When i used eth1 then it said that there is no such device. I have tried alot of different things but still nothing...
I configured the Router that if my MAC address will try to conenct then it will give me my ip but still nothing...
any more ideas????

EDIT: Could you tell me what is MTU ????
I just remember that the MTU in the ifconfig -a command  on eth0 was 1500, and now i just noticed that the MTU in the router configuration is 1492, is it an important discovery lol


Excuse my English...

Offline

#10 2007-01-20 15:42:25

lilsirecho
Veteran
Registered: 2003-10-24
Posts: 5,000

Re: A problem with Network

MTU is maximum transmission unit and is typically 1500 on an ethernet LAN.

You can read about it on google.

It seems it is automatic with ethernet LAN.

If all else fails, try using a router slot that the other computers are plugged in on.

Green lights on both ends of the Cat cable connections must be observed.

Perhaps listing your rc. conf will help to see any typos...


Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!

Offline

#11 2007-01-20 16:11:35

jaxx
Member
From: Estonia ;)
Registered: 2006-11-06
Posts: 17

Re: A problem with Network

Emm any ideas how can i get my rc.conf file big_smile without writeing it on the paper and then rewriting it here??

EDIT:Ok here is my rc.conf
#
# /etc/rc.conf - Main Configuration for Arch Linux
#

#
# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/unimaps
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE=
HARDWARECLOCK="localtime"
TIMEZONE=Canada/Pacific
KEYMAP=us
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

#
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by hwdetect
MOD_BLACKLIST=()
#
# Modules to load at boot-up (in this order)
#   - prefix a module with a ! to blacklist it
#
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

#
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="Jaxx"
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
lo="lo 127.0.0.1"
eth0="dhcp"
INTERFACES=(lo eth0)
#
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
#
# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network-profiles
#
#NET_PROFILES=(main)
#
# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng !hotplug !pcmcia network netfs crond)

# End of file

When i restart network (/etc/rc.d/network restart) i get this:
::Stopping Network                       [Done]
:: Starting Network                       [Failed]
and if i take the ! away in thefront of the gateway (ROUTES=(gateway) )
and i restart the network i get this
:: Stopping Network                      [Done]
::Starting Network                        [Failed]
connect: Network is unreachable


Excuse my English...

Offline

#12 2007-01-20 16:55:01

Snarkout
Member
Registered: 2005-11-13
Posts: 542

Re: A problem with Network

It sounds like the wan port of your DLINK is what is getting its IP via dhcp (the router asks for an IP, the ISP provides it with one), and that you have assigned static (non-changing) IPs for the computers on your LAN.

Windows XP running on this same box has a working network, correct?  If you look at the control panel network settings in XP do you see a dot in "Obtain an IP address automatically" or is the dot in "Use the following IP address?"

My current guess is that your DLINK isn't serving IP addresses via DHCP, and that you'll need to change the DLINK settings or you'll need to edit your /etc/rc.conf to use a static IP.  The other option (assuming I correctly understand all of the info you've given us) is that your NIC isn't working correctly with linux.  Could you please post the output of

dmesg | grep -i eth

?


Unthinking respect for authority is the greatest enemy of truth.
-Albert Einstein

Offline

#13 2007-01-20 17:21:53

lilsirecho
Veteran
Registered: 2003-10-24
Posts: 5,000

Re: A problem with Network

Noted your LOCAL TIME setting as CANADA/PACIFIC...is that correct for your locale?

Snarkout mentions the check in XP windows for the IP selection which will put the cause in better perspective.


Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!

Offline

#14 2007-01-20 18:08:04

jaxx
Member
From: Estonia ;)
Registered: 2006-11-06
Posts: 17

Re: A problem with Network

Emm the local time isint correct i know that, i havent changed that, And my Windows XP has the 'Obtain an IP adress automatically'.
All the things you said is correct. I allso tried with the Static IP with DLINK (in the DLINK configuration window it was called Static dhcp IP) but i coulnd get it to work.
When i put  Static ip starting network said it was Done but i coulnd do anything exept ping my own address....
And now i will go check the output of dmesg | grep -i eth

Is there a better way to copy that output, that output is pretty big and writing it down on the paper and back here is pretty time-consuming, i dont have a Floppy Rom, but how about to use a usb mass storage device? but i dont know how to use it, like how to mount and how to copy the log file on it....  :oops:  :oops:  :oops:  :oops:


Excuse my English...

Offline

#15 2007-01-20 18:47:04

lilsirecho
Veteran
Registered: 2003-10-24
Posts: 5,000

Re: A problem with Network

Static IP is assigned by an ISP and cannot be self-generated.  It is entered in response to the ISP assignment in rc.conf.

In re; printout of dmseg...only that portion applying to eth0..ethernet is needed... copy that part and paste into forum....

Perhaps correcting the time parameters will correct your difficulty.....

Others have had time-related problems recently...time in the future is the worst affliction!!


Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!

Offline

#16 2007-01-20 19:02:00

jaxx
Member
From: Estonia ;)
Registered: 2006-11-06
Posts: 17

Re: A problem with Network

Well there was only one line with eth0 in it, at least i think so.

Jan 20 20:50:45 Jaxx eth0: forcedeth.c:subsystem:01458:e000 bound to 0000:00:14.0

and i found something about the eth1 too

Jan 20 20:50:45 Jaxx eth1394 eeth1: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
There was something before that too but i dont think this is something important to the internet access, these IEEE-1394 ports are on my motherboard in the case, they are not on the rear panel..


Excuse my English...

Offline

#17 2007-01-20 19:19:29

lilsirecho
Veteran
Registered: 2003-10-24
Posts: 5,000

Re: A problem with Network

My recent upgrade this day reports udev changes...

It recommends reading /etc/udev/readme-udev-arch.txt for details concerning internet, persistent internet and module inconsistency with respect to eth0/eth1 and sound card switching.

It may have the answer for your difficulty....


Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!

Offline

#18 2007-01-20 20:15:19

jaxx
Member
From: Estonia ;)
Registered: 2006-11-06
Posts: 17

Re: A problem with Network

Tried those things, but still i couldnt get it to work, maybe i did something wrong. Any more ideas? But how can kernel switch the soundcard and the eth0/eth1??


Excuse my English...

Offline

#19 2007-01-20 20:48:32

lilsirecho
Veteran
Registered: 2003-10-24
Posts: 5,000

Re: A problem with Network

Perhaps the router needs to be reset in order to recognize a new computer interface.

I am out of ideas at this point.


Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!

Offline

#20 2007-01-20 20:54:17

jaxx
Member
From: Estonia ;)
Registered: 2006-11-06
Posts: 17

Re: A problem with Network

Well i did it before but i will do it again, But i had to reinstall windows before i put Arch on my computer so then i didnt reset my router. But if this helps, i installed arch with the base install cd...  in the everything.log i read that arch didn't get anything from the router... and yeah i have a DSL connection with a dynamic ip, what hae i missed hmm...
I just reinstalled arch, i thought maybe there was some little mistakes but, still nothing, so i will reset and configure my router again, and try to connect to the router with arch, i will send feedback if something happenes or something....

EDIT: I even used a Ubuntu LiveCD and i couldn't get to the internet  :?  and i did a reset and still nothing, with Arch i tried with eth0="dhcp" and ROUTES=(gateway) and when i restarted the network it said that it is unreachable, i didn't right now try it without the ROUTES=(!gateway) i will try it right now.... BRB
Still nothing...

But one question. How can i disalbe that IEEE-1394 (eth1) from loading when Arch is booting up????? I am thinking like Arch wants to use that for network access.

I got the IEEE-1394 disabled from BIOS but still nothing.

DHCP Server
The DI-604 can be setup as a DHCP Server to distribute IP addresses to the LAN network.

But if i disable that dhcp server stuff?? Any ideas what will happen??
What does WAN mean??

Ok i disabled taht dhcp server  and that was not a good idea, and now i have no more ideas either oh btw when someone(sry cant remember your name right now) asked me to copy the output on dmesg, is it the same when Arch boots up and there are all the loading stuff? if not then you have to explain to me how can i see the all output of dmesg because i can only see the last part of it.


Excuse my English...

Offline

#21 2007-01-20 22:13:29

Snarkout
Member
Registered: 2005-11-13
Posts: 542

Re: A problem with Network

But one question. How can i disalbe that IEEE-1394 (eth1) from loading when Arch is booting up????? I am thinking like Arch wants to use that for network access.

add eth1394 to your mod_blacklist array in /etc/rc.conf


Unthinking respect for authority is the greatest enemy of truth.
-Albert Einstein

Offline

#22 2007-01-20 22:20:50

Snarkout
Member
Registered: 2005-11-13
Posts: 542

Re: A problem with Network

Also, if you are using dhcp, !gateway is probably fine.  So far, it appears the issue is that you aren't pulling an IP.  XP apparently pulls an IP from your dlink just fine, so it's reasonable to expect linux to do the same.  Forcedeth, IIRC, is an nvidia module - I think there may be better drivers for that type of interface, but in general that one should work fine.  Is this an nforce mobo (you may have mentioned, but I don't have time to re-read everything right now)?  If so, does

lsmod | grep forcedeth

return anything?

I doubt that the eth1394 adapter is your entire issue since the ubuntu livecd doesn't work either - IIRC ubuntu blacklists that module by default since it is so rarely used and so often causes headaches.  It is a good idea to blacklist it though.


Unthinking respect for authority is the greatest enemy of truth.
-Albert Einstein

Offline

#23 2007-01-20 23:01:45

jaxx
Member
From: Estonia ;)
Registered: 2006-11-06
Posts: 17

Re: A problem with Network

I got the IEEE-1394 disabled from BIOS but still nothing.
Quote:
DHCP Server
The DI-604 can be setup as a DHCP Server to distribute IP addresses to the LAN network.

But if i disable that dhcp server stuff?? Any ideas what will happen??
What does WAN mean??

Ok i disabled taht dhcp server and that was not a good idea, and now i have no more ideas either oh btw when someone(sry cant remember your name right now) asked me to copy the output on dmesg, is it the same when Arch boots up and there are all the loading stuff? if not then you have to explain to me how can i see the all output of dmesg because i can only see the last part of it.

That was me, i dint see that you wrote these last posts, and yes my mobo is nforce i will see what do the give me

Emm the lsmod gives a lot of stuff but grep forcedeth nothing, the cursor just blinks on the next line

[root@jaxx ~]grep forcedeth
_

and when i press ctrl+Z it stoppes

[1]+ Stopped                 grep forcedeth
[root@jaxx ~]_

[/code]


Excuse my English...

Offline

#24 2007-01-20 23:21:01

Snarkout
Member
Registered: 2005-11-13
Posts: 542

Re: A problem with Network

WAN = Wide Area Network which, in this case, means anything on the internet side of the dlink.

LAN = Local Area Network which, in this case, means your computers.

You probably want your dlink to serve DHCP IPs - disabling that service means that you have to manually assign static IPs to the computers on your LAN.

dmesg is a utility that allows you to see what's in your kernels logging buffer - after a boot, the output of "dmesg" will essentially be the same as what you see scrolling by during boot up, with a few exceptions.

Does running the command (as root) "dhcpcd" give you an error?  If so, what is it?

Does running the command (as root)

ifconfig eth0 192.168.0.200 netmask 255.255.255.0

give you an error?  If so, what is it?

Does either of these commands give you a new IP and allow you to get online?


Unthinking respect for authority is the greatest enemy of truth.
-Albert Einstein

Offline

#25 2007-01-20 23:24:01

Snarkout
Member
Registered: 2005-11-13
Posts: 542

Re: A problem with Network

You want to run that command exactly as I typed it - that will look through the output of lsmod for the forcedeth module.

To kill the grep command you have backgrounded you want to run the command "fg" and then do a ctrl+c to kill the process.


Unthinking respect for authority is the greatest enemy of truth.
-Albert Einstein

Offline

Board footer

Powered by FluxBB