You are not logged in.

#1 2005-08-04 19:38:34

Lazy_Warrior
Member
From: Denmark
Registered: 2005-08-04
Posts: 10

Two identical NIC, dhcp won't work

Hi,
I'm a bit new to archlinux, but I like the idea of not being too tied up on how you solve a problem  big_smile

I'm trying to make a router with archlinux, I've done this before with gentoo (the same machine) and there were no problems.
Now I can't get the two NIC to work at the same time.

When I have with cards installed, only the local IP works, the NIC taht is setup with dhcp, doesn't work.
With only one NIC installed dhcp works great.

It doesn't matter which NIC I configure as dhcp, the result is the same.

I'm using hotplug to find the nics, and I have nothing in modprobe.conf.
I've tried to pass parameters to the alias
eht0 xxx
eth1 xxx
options xxx irq=10,11 io=e100,e500

xxx = the module in the installation guide.

I'm all out of ideas, couls someone pleae help?

thanx in advance

Offline

#2 2005-08-05 05:51:51

cactus
Taco Eater
From: t͈̫̹ͨa͖͕͎̱͈ͨ͆ć̥̖̝o̫̫̼s͈̭̱̞͍̃!̰
Registered: 2004-05-25
Posts: 4,622
Website

Re: Two identical NIC, dhcp won't work

Lazy_Warrior wrote:

I'm using hotplug to find the nics, and I have nothing in modprobe.conf.

simple solution might be to try putting them in modprobe.conf (or /etc/rc.conf MODULES array)


"Be conservative in what you send; be liberal in what you accept." -- Postel's Law
"tacos" -- Cactus' Law
"t̥͍͎̪̪͗a̴̻̩͈͚ͨc̠o̩̙͈ͫͅs͙͎̙͊ ͔͇̫̜t͎̳̀a̜̞̗ͩc̗͍͚o̲̯̿s̖̣̤̙͌ ̖̜̈ț̰̫͓ạ̪͖̳c̲͎͕̰̯̃̈o͉ͅs̪ͪ ̜̻̖̜͕" -- -̖͚̫̙̓-̺̠͇ͤ̃ ̜̪̜ͯZ͔̗̭̞ͪA̝͈̙͖̩L͉̠̺͓G̙̞̦͖O̳̗͍

Offline

#3 2005-08-05 15:01:59

Lazy_Warrior
Member
From: Denmark
Registered: 2005-08-04
Posts: 10

Re: Two identical NIC, dhcp won't work

Hi
Thanx for the advice, but it didn't help.
I added the module from the install guid (which works fine with just one card inserted) to the MODULES array in rc.conf.

I do not know if this brungs any light to it; this is what I have in my rc.conf as interfaces:

lo="lo 127.0.0.1"
eth0="eth0 192.168.0.1 netmask 255.255.255.0 broadcast 192.168.0.255"
eth1="dhcp"
INTERFACES=(lo eth0 eth1)

I've also tried this as eth1:

eth1="eth1 dhcp"

but it didn't help.

Are there any other things I could try?

Offline

#4 2005-08-05 15:47:03

phrakture
Arch Overlord
From: behind you
Registered: 2003-10-29
Posts: 7,879
Website

Re: Two identical NIC, dhcp won't work

Lazy_Warrior wrote:
lo="lo 127.0.0.1"
eth0="eth0 192.168.0.1 netmask 255.255.255.0 broadcast 192.168.0.255"
eth1="dhcp"
INTERFACES=(lo eth0 eth1)

Total stab in the dark....
maybe try bringing them up in a different order?
INTERFACES=(lo eth1 eth0)?

Offline

#5 2005-08-05 16:04:51

Lazy_Warrior
Member
From: Denmark
Registered: 2005-08-04
Posts: 10

Re: Two identical NIC, dhcp won't work

Nopes, that didn't do the trick either.

If just I had an idea of what could be wrong, it wouldn't be this frustrating.

Offline

#6 2005-08-05 16:37:40

jerrym
Member
From: Kannapolis, NC
Registered: 2005-07-08
Posts: 60

Re: Two identical NIC, dhcp won't work

i've never used modprobe.conf but like you say with only one nic, dhcp works. i do have a few questions though?

what ip is eth1 pulling from dhcp? is it connected directly to a cable modem (or dsl)? what is connected to eth0?


He may look like an idiot and talk like an idiot but don't let that fool you. He really is an idiot.
- - - Groucho Marx

Registered Linux User #319935
Registered Linux Machine #204881

Offline

#7 2005-08-05 17:19:33

cactus
Taco Eater
From: t͈̫̹ͨa͖͕͎̱͈ͨ͆ć̥̖̝o̫̫̼s͈̭̱̞͍̃!̰
Registered: 2004-05-25
Posts: 4,622
Website

Re: Two identical NIC, dhcp won't work

maybe try circumventing the init process and see if anything new hops out.

after you get started up, try manually calling dhclient (or dhcpcd...i dont remember which one arch has offhand) on both interfaces..see if anything happens. Check the logs too. I believe both dhclient and dhcpcd log to syslog when something goes bonkers...

dhclient eth0
dhclient eth1

of course, if arch uses dhcpcd, then adjust accordingly.  wink


"Be conservative in what you send; be liberal in what you accept." -- Postel's Law
"tacos" -- Cactus' Law
"t̥͍͎̪̪͗a̴̻̩͈͚ͨc̠o̩̙͈ͫͅs͙͎̙͊ ͔͇̫̜t͎̳̀a̜̞̗ͩc̗͍͚o̲̯̿s̖̣̤̙͌ ̖̜̈ț̰̫͓ạ̪͖̳c̲͎͕̰̯̃̈o͉ͅs̪ͪ ̜̻̖̜͕" -- -̖͚̫̙̓-̺̠͇ͤ̃ ̜̪̜ͯZ͔̗̭̞ͪA̝͈̙͖̩L͉̠̺͓G̙̞̦͖O̳̗͍

Offline

#8 2005-08-05 17:24:40

jackmetal
Member
From: US
Registered: 2005-06-13
Posts: 164

Re: Two identical NIC, dhcp won't work

Yep, arch uses dhcpcd (at least mine does)  ;-)

I've noticed any dhcp errors in the errors log

/var/log/errors.log

--

Some of the world's greatest feats were
accomplished by people not smart enough
to know they were impossible.
-- Doug Larson

Offline

#9 2005-08-05 20:02:21

Lazy_Warrior
Member
From: Denmark
Registered: 2005-08-04
Posts: 10

Re: Two identical NIC, dhcp won't work

<Jerrym>
Eth1 is connected directly to the DSL-modem, no dial-up is needed.
Eth0 is connected to the LAN through a switch containing my working computer smile
I'm not sure which card is eth0 and eth1 so I switch the cables each time I try to be sure.

<Cactus>
I've tried dhcpcd eth0 and eth1 with the same results.
A timeout while waiting for a valid response fomr DHCP server

<jackmetal>
Below are the result of "tail /var/log/errors.log". I had to type it manually since I use another computer.

ACPI: Unable to locate RSDP
shpchp: acpi_shchprm:get_device PCI ROOT HID fail=0x1001
dhcpcd: timed out waiting for a valid DHCP server response
dhcpcd: recvfrom: Network is down
devfsd: action_compat: error unlinking: "vcs1" No such file or directory
devfsd: action_compat: error unlinking: "vcsa1" No such file or directory

I hope this tells you something, I can't make much out of it except for the timeout. I have no clue of what the other things are.

Offline

#10 2005-08-05 20:14:45

phrakture
Arch Overlord
From: behind you
Registered: 2003-10-29
Posts: 7,879
Website

Re: Two identical NIC, dhcp won't work

Lazy_Warrior wrote:

Eth1 is connected directly to the DSL-modem, no dial-up is needed.
...
A timeout while waiting for a valid response fomr DHCP server
...

dhcpcd: timed out waiting for a valid DHCP server response
dhcpcd: recvfrom: Network is down

Ok, two things - DHCP *is* actually working, so it's not a problem with DHCP per-se, the problem is the DSL.

You're going to need to use rp-pppoe or something like that, or reconfigure the DSL modem to use "PPPoE on the Modem" (mine has that option).

When working with DSL, PPPoE needs to be functioning.  More modern DSL modems just do it for you - mine does, but it wasn't enabled by default.  You also have the option of talking to the modem itself to handle pppoe (rp-pppoe does this) - this is called "PPPoE on the Client" by my modem.

Offline

Board footer

Powered by FluxBB