LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 10-12-2008, 12:46 PM   #1
corteplaneta
Member
 
Registered: Jul 2007
Distribution: archlinux, ubuntu, slackware
Posts: 58

Rep: Reputation: 15
Complex Dual-NIC Problems


Hi everyone,

So I've got ndiswrapper installed & installed the driver for a 00:0a.0 Ethernet controller: ADMtek NC100 Network Everywhere Fast Ethernet 10/100 (rev 11).

My ndiswrapper -l is stating nc100 : driver installed & device (1317:0985) present.

My /etc/modprobe.d/ndiswrapper file contains the line "alias eth1 ndiswrapper"...

I've ran modprobe ndiswrapper..

And still NO eth1 interface appears from ifconfig output!!!

Is it possible the driver simply isn't supported? Or am I missing some kind of step here?

Any help would be greatly appreciated! Thanks!

(by the way, I tried using the tulip driver as well to no avail)

Last edited by corteplaneta; 10-13-2008 at 10:06 PM.
 
Old 10-12-2008, 05:09 PM   #2
Matir
Moderator
 
Registered: Nov 2004
Location: San Jose, CA
Distribution: Ubuntu
Posts: 8,507

Rep: Reputation: 118Reputation: 118
Does iwconfig show any interfaces? This would show any recognized wifi interfaces.
 
Old 10-12-2008, 05:42 PM   #3
corteplaneta
Member
 
Registered: Jul 2007
Distribution: archlinux, ubuntu, slackware
Posts: 58

Original Poster
Rep: Reputation: 15
bash-3.1# iwconfig
lo no wireless extensions.

sit0 no wireless extensions.

eth0 no wireless extensions.

I don't have wireless (or even wireless support in my kernel)..just to clarify this is a wired NIC.
 
Old 10-12-2008, 06:00 PM   #4
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,254

Rep: Reputation: 635Reputation: 635Reputation: 635Reputation: 635Reputation: 635Reputation: 635
After googling your ethernet card, it should be supported by the 'tulip' module. You shouldn't need ndiswrapper, as far as I know. Try the following command as root:
Code:
# modprobe tulip
Then see if `ifconfig -a` shows any interfaces (other than lo). If it does, run `netconfig` as root to set up your network.
 
Old 10-12-2008, 06:29 PM   #5
corteplaneta
Member
 
Registered: Jul 2007
Distribution: archlinux, ubuntu, slackware
Posts: 58

Original Poster
Rep: Reputation: 15
I tried this before & had no results..I will try it again, though, after uninstalling ndiswrapper driver.
 
Old 10-12-2008, 06:37 PM   #6
corteplaneta
Member
 
Registered: Jul 2007
Distribution: archlinux, ubuntu, slackware
Posts: 58

Original Poster
Rep: Reputation: 15
Ok, it seems as if there's some progress...

bash-3.1# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:0A:E6:C5:5C:31
inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20a:e6ff:fec5:5c31/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:343997 errors:0 dropped:0 overruns:0 frame:0
TX packets:196534 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:490451030 (467.7 MiB) TX bytes:16446058 (15.6 MiB)
Interrupt:11 Base address:0xec00

eth1 Link encap:Ethernet HWaddr 00:04:5A:81:B4:40
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)
Interrupt:10 Base address:0xd000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
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)

sit0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-65-74-00-00-00-00-00-00-00-00
NOARP MTU:1480 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)

I can see eth1, but running netconfig eth1 as root & running "/etc/rc.d/inet1 restart" the output of eth1 remains the same. Any ideas?
 
Old 10-12-2008, 09:25 PM   #7
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,254

Rep: Reputation: 635Reputation: 635Reputation: 635Reputation: 635Reputation: 635Reputation: 635
I'm pretty sure netconfig will ONLY configure eth0 (sorry about that). You would have to manually edit /etc/rc.d/rc.inet1.conf and then restart the interface using `/etc/rc.d/rc.inet1 restart`.

It looks like the interface is now recognized, so it should just be a configuration issue at this point.

Last edited by T3slider; 10-12-2008 at 09:27 PM.
 
Old 10-12-2008, 09:56 PM   #8
corteplaneta
Member
 
Registered: Jul 2007
Distribution: archlinux, ubuntu, slackware
Posts: 58

Original Poster
Rep: Reputation: 15
Thanks, that solved my problem! I really appreciate all the help, T3slider. The NIC still does not work, but I think it might just be broken, as I know everything in the config is right.
 
Old 10-12-2008, 10:28 PM   #9
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,254

Rep: Reputation: 635Reputation: 635Reputation: 635Reputation: 635Reputation: 635Reputation: 635
If you are using DHCP, you could try running `dhcpcd eth1` and see if you get an IP address in your `ifconfig -a` output. If you get an IP but can't ping google.com, for example, try pinging the IP address instead (`ping 72.14.207.99`). If you get a response with the IP and not the domain name, then your DNS server is not being used correctly (check /etc/resolv.conf).

I would suggest bringing down your eth0 interface first and then trying to get eth1 working (assuming it's not broken), just in case there are some conflict issues. You can stop your eth0 interface by running `/etc/rc.d/rc.inet1 eth0_stop` (or just running `ifconfig eth0 down`).
 
Old 10-12-2008, 10:52 PM   #10
corteplaneta
Member
 
Registered: Jul 2007
Distribution: archlinux, ubuntu, slackware
Posts: 58

Original Poster
Rep: Reputation: 15
Ok, good call, for some reason after stopping eth0 eth1 began to work. Let me clarify a few things here on what I'm attempting to do. I have two NICs in my computer, eth0 & eth1. I originally had my main network (to gateway 192.168.1.1) connected to eth0, and eth1 connected via crossover cable to another linux machine (whose gateway was set to eth1's IP). I could not ping machines hooked up to the crossover cable from either machine. After stopping eth0 & plugging my main network connection into eth1, I was once again able to ping 192.168.1.1, so I know the card is not broken. I could not ping 72.14.207.99 until I brought eth0 back up again (even though the crossover cable was now plugged into this card). My resolv.conf file contains both nameservers I use. Now I still cannot ping back and forth from the machines hooked up the crossover cable (eth0 -> other linux PC). This does sound like a conflict, is there any way to check & resolve this issue? Thanks!
 
Old 10-13-2008, 12:05 PM   #11
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,254

Rep: Reputation: 635Reputation: 635Reputation: 635Reputation: 635Reputation: 635Reputation: 635
I'm afraid I have no experience with that type of thing, so I won't be much help. However, I would suggest changing the title if you can, since people who don't read every thread are going to assume this is a WiFi problem. Since I don't have a laptop, I don't really read those threads very carefully myself, and some others may not read them at all. However, if you make the title more informative as to your current (more complex and less repetitive) networking problem, you may get some better help.
 
Old 10-13-2008, 05:11 PM   #12
corteplaneta
Member
 
Registered: Jul 2007
Distribution: archlinux, ubuntu, slackware
Posts: 58

Original Poster
Rep: Reputation: 15
Hey, don't sweat it, I appreciate the help!
 
Old 10-13-2008, 05:12 PM   #13
robel
Member
 
Registered: Oct 2008
Location: Norway
Distribution: Slackware
Posts: 61

Rep: Reputation: 15
Quote:
Originally Posted by corteplaneta View Post
Ok, good call, for some reason after stopping eth0 eth1 began to work. Let me clarify a few things here on what I'm attempting to do. I have two NICs in my computer, eth0 & eth1. I originally had my main network (to gateway 192.168.1.1) connected to eth0, and eth1 connected via crossover cable to another linux machine (whose gateway was set to eth1's IP). I could not ping machines hooked up to the crossover cable from either machine. After stopping eth0 & plugging my main network connection into eth1, I was once again able to ping 192.168.1.1, so I know the card is not broken. I could not ping 72.14.207.99 until I brought eth0 back up again (even though the crossover cable was now plugged into this card). My resolv.conf file contains both nameservers I use. Now I still cannot ping back and forth from the machines hooked up the crossover cable (eth0 -> other linux PC). This does sound like a conflict, is there any way to check & resolve this issue? Thanks!
Try:
tcpdump -n -i eth0 icmp or arp
and
tcpdump -n -i eth1 icmp or arp
simultaneously while pinging the computers that doesn't answer.

Can you see the traffic? (ARP, ICMP)
Is it on the correct NIC?
 
Old 10-13-2008, 06:27 PM   #14
corteplaneta
Member
 
Registered: Jul 2007
Distribution: archlinux, ubuntu, slackware
Posts: 58

Original Poster
Rep: Reputation: 15
With my current configuration, here is the output of the commands...


Code:
bash-3.1# tcpdump -n -v -i eth0 icmp | tcpdump -n -v -i eth1 icmp | ping 192.168.1.8 << trouble machine
PING 192.168.1.8 (192.168.1.8) 56(84) bytes of data.
tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
From 192.168.1.5 icmp_seq=1 Destination Host Unreachable  << this is my local machine??
From 192.168.1.5 icmp_seq=2 Destination Host Unreachable
From 192.168.1.5 icmp_seq=4 Destination Host Unreachable
From 192.168.1.5 icmp_seq=5 Destination Host Unreachable
From 192.168.1.5 icmp_seq=7 Destination Host Unreachable
From 192.168.1.5 icmp_seq=8 Destination Host Unreachable

--- 192.168.1.8 ping statistics ---
10 packets transmitted, 0 received, +6 errors, 100% packet loss, time 9010ms
, pipe 2
0 packets captured
0 packets received by filter
0 packets dropped by kernel
0 packets captured
0 packets received by filter
0 packets dropped by kernel
Code:
bash-3.1# tcpdump -n -v -i eth0 arp | tcpdump -n -v -i eth1 arp | ping 192.168.1.8
PING 192.168.1.8 (192.168.1.8) 56(84) bytes of data.
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes
From 192.168.1.5 icmp_seq=2 Destination Host Unreachable
From 192.168.1.5 icmp_seq=3 Destination Host Unreachable
From 192.168.1.5 icmp_seq=5 Destination Host Unreachable
From 192.168.1.5 icmp_seq=6 Destination Host Unreachable
From 192.168.1.5 icmp_seq=9 Destination Host Unreachable
From 192.168.1.5 icmp_seq=11 Destination Host Unreachable
From 192.168.1.5 icmp_seq=12 Destination Host Unreachable

--- 192.168.1.8 ping statistics ---
13 packets transmitted, 0 received, +7 errors, 100% packet loss, time 12033ms
, pipe 2
12 packets captured
12 packets received by filter
0 packets dropped by kernel
2 packets captured
2 packets received by filter
0 packets dropped by kernel
So why exactly do you think this is telling me my local machine is unreachable when I'm obviously attempting to ping 192.168.1.8?

And what's even stranger is that after toying with this for a while, and running simply tcpdump (whilst pinging 192.168.1.8 in a separate shell)..I get the following output

Code:
bash-3.1# tcpdump
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
19:24:10.319316 IP 192.168.1.8.45806 > nsvip01.windstream.net.domain:  37567+ A? www.linuxmint.com.MSHOME. (42)
19:24:15.319855 IP 192.168.1.8.56218 > nsvip02.windstream.net.domain:  37567+ A? www.linuxmint.com.MSHOME. (42)
19:24:20.320514 IP 192.168.1.8.45806 > nsvip01.windstream.net.domain:  37567+ A? www.linuxmint.com.MSHOME. (42)
19:24:25.321079 arp who-has xanderbox.localhost tell 192.168.1.8
19:24:25.321101 arp reply xanderbox.localhost is-at 00:0a:e6:c5:5c:31 (oui Unknown)
19:24:25.321473 IP 192.168.1.8.53505 > nsvip02.windstream.net.domain:  37270+ A? www.linuxmint.com. (35)
19:24:30.321772 IP 192.168.1.8.52826 > nsvip01.windstream.net.domain:  37270+ A? www.linuxmint.com. (35)
19:24:35.322382 IP 192.168.1.8.53505 > nsvip02.windstream.net.domain:  37270+ A? www.linuxmint.com. (35)
19:24:40.322990 IP 192.168.1.8.52826 > nsvip01.windstream.net.domain:  37270+ A? www.linuxmint.com. (35)
19:24:45.323765 IP 192.168.1.8.43336 > nsvip02.windstream.net.domain:  28452+ A? www.linuxmint.com.MSHOME. (42)
19:24:50.324480 IP 192.168.1.8.41472 > nsvip01.windstream.net.domain:  28452+ A? www.linuxmint.com.MSHOME. (42)
19:24:55.325145 IP 192.168.1.8.43336 > nsvip02.windstream.net.domain:  28452+ A? www.linuxmint.com.MSHOME. (42)

12 packets captured
12 packets received by filter
0 packets dropped by kernel
..the machine I'm trying to connecto to is running Linux Mint, except when I try this again, I get no output from tcpdump.

Oh, and now I'm just confused. Now after running tcpdump on eth0 on both machines, I can see

"19:41:20.669541 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: ICMP (1), length: 84) 192.168.1.8 > xanderbox.localhost: ICMP echo request, id 12897, seq 185, length 64" on the 192.168.1.5 machine,

and the opposite (as in 192.168.1.5 > xravtop.local: ICMP echo request) on the other machine...yet this is a long time after I stopped pinging? And it's still going.

EDIT:

Ok, you are correct, the wrong interface is being used. When pinging -I eth0, I get a ping response from 192.168.1.8, but I cannot ping 192.168.1.5 from the 192.168.1.8 machine. How do I correctly configure this so that the two can communicate?

Any ideas?

Last edited by corteplaneta; 10-13-2008 at 06:40 PM.
 
Old 10-13-2008, 09:49 PM   #15
corteplaneta
Member
 
Registered: Jul 2007
Distribution: archlinux, ubuntu, slackware
Posts: 58

Original Poster
Rep: Reputation: 15
Problem solved. I had to manually edit my routing table as such..

Code:
bash-3.1# route del default
bash-3.1# route add default gw 192.168.1.1 dev eth0
bash-3.1# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.8     0.0.0.0         255.255.255.255 UH    0      0        0 eth1
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth0
bash-3.1# ping google.com
PING google.com (209.85.171.99) 56(84) bytes of data.
64 bytes from cg-in-f99.google.com (209.85.171.99): icmp_seq=1 ttl=232 time=115 ms
64 bytes from cg-in-f99.google.com (209.85.171.99): icmp_seq=2 ttl=232 time=109 ms
Thanks for the help guys..now if I can just figure out how to get a sort of internet-connection-sharing working between the two boxes..adding 192.168.1.1 as a default gateway for the route I created just breaks it..

Last edited by corteplaneta; 10-13-2008 at 10:06 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Wifi and ndiswrapper issues NoahT1BM Linux - Software 2 05-09-2008 12:24 PM
Ndiswrapper Issues BlindFate Linux - Wireless Networking 2 03-26-2008 04:54 PM
ndiswrapper and broadcom issues DJCreation Linux - Wireless Networking 1 01-17-2007 06:22 AM
Broadcom, ndiswrapper issues. Noctaire Linux - Wireless Networking 3 12-04-2005 11:53 AM
issues with ndiswrapper frogg609 Linux - Wireless Networking 1 08-16-2004 10:42 AM


All times are GMT -5. The time now is 06:11 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration