Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Maybe I'm having one of those days, but I'm more than a bit confused...
I've got two ethernet ports on my computer. One on a linksys card and one not. I don't know what the one that's not is hooked to--I assume it's the motherboard?
Anyway, the one hooking into the linksys card works fine. That's where I get my internet from. Patch cable from a router. It uses eth0.
Now my problem is, how do I get an eth1 for the other port? I can just see this as being a dumb question, but hell if I know what I'm doing...
Er.. Yeah, there's no driver (I think). Funny thing is, I don't know how to figure out what to do about it. eth1 doesn't exist as of yet. My problem is getting it there. I gather that the driver sticks it there, so to speak. The NIC is fine, btw.
I've done a fair bit of networking (in my house, that is). Wired/wireless networks with different cables and such through linux and winblows. Just had one of those days, I suppose.
Anyway, the thing is, this ethernet port is (I suppose) on my motherboard. That's about as far as my knowledge goes. If I knew what driver to install, I could probably blunder my way through it; I've done it before.
Maybe I..., no, I'm sure I'm not entirely sure I know what I'm talking about. If you can work your way through that sentence... But it just seems to me that it should be something generic that would just "work," so to speak, since it's not an actual ethernet card. Minimal fiddling with it.
Er.. Yeah, there's no driver (I think). Funny thing is, I don't know how to figure out what to do about it. eth1 doesn't exist as of yet. My problem is getting it there. I gather that the driver sticks it there, so to speak. The NIC is fine, btw.
That's right. No driver = no eth1 (or is that "driver => eth1" ? )
Quote:
Originally Posted by MiniMe001
I've done a fair bit of networking (in my house, that is). Wired/wireless networks with different cables and such through linux and winblows. Just had one of those days, I suppose.
experience is relative
Quote:
Originally Posted by MiniMe001
Anyway, the thing is, this ethernet port is (I suppose) on my motherboard. That's about as far as my knowledge goes.
You suppose?
I don't suppose it makes much difference, but why on earth don't you know?
(I must be missing something!)
Quote:
Originally Posted by MiniMe001
If I knew what driver to install, I could probably blunder my way through it; I've done it before.
hmmm ... yes ... more action ... less talk.
Post info as requested and we'll get to that stage.
Quote:
Originally Posted by MiniMe001
Maybe I..., no, I'm sure I'm not entirely sure I know what I'm talking about.
We got that bit
Quote:
Originally Posted by MiniMe001
If you can work your way through that sentence...
Can't read minds as well as I used to ... most of mine's gone
Quote:
Originally Posted by MiniMe001
But it just seems to me that it should be something generic that would just "work," so to speak, since it's not an actual ethernet card. Minimal fiddling with it.
I'm not going to bash you right now, as I've had a few drinks.
If you stop guessing about what's going on and how 'it' works, we can
get on with the task at hand ... finding out what 'it' is.
Quote:
Originally Posted by MiniMe001
Whichever, how do I figure out what to install?
1. Learn to read my posts before I start drinking? 8)
2. Take more time to research the information required for a post,
than it takes to type it.
lspci isn't installed and portage (gentoo) can't find it. I'll install it tomorrow.
I think it's on my motherboard, because I don't see anywhere else it could be. I know just about zip about hardware. It's up there where the PS2 and usbs are, though. I dunno what else it could be hooked to, so I figure it's the motherboard. Where the [] are in this:
Right,
the only network-related module I can see in that list is tulip.
I assume that would be for your linksys card.
As your motherboard would have to be reasonably recent to have sata,
I'm guessing you probably have some sort of gigabit ethernet that's
not supported by your current kernel.
Please help us to help you:
1. supply motherboard brand & model. If you don't know it, google for the brand & model of the computer until you do.
2. find the kernel version you are running
Code:
$ uname -a
3. supply output from lspci (lspci is part of the 'pciutils' package)
1)
computer: vpr matrix ft-2100pe
all I can find is that it's an Intel RAID-capable board. the vpr matrix site doesn't have it and google gives like 6 or 7 results. :/
It does say integrated 10/100 ethernet, though.
2)
2.6.11-gentoo-r3 #1 SMP Wed Jun 15 10:32:19 CDT 2005 i686 Intel P4 2.4GHz GenuineIntel GNU/Linux
Funny, June 15 is my birthday. :P
Looking at the spec sheet for the FT2100-PE (on the vpr site)
Quote:
Network Card Intel Pro 10/100 Integrated NIC
A bit of (patient) googling will eventually reveal references to
eepro, eepro100 or e100 (not sure of the differences)
Examing the documentation installed with your kernel source:
(you say you're running gentoo so I assume you've got the kernel source)
you'll find an INDEX for the network drivers in
/usr/src/linux/Documentation/networking/00-INDEX (or similar)
Code:
$ locate Documentation | grep networking | grep INDEX
Looking in that file, you'll find:
Quote:
e100.txt
- info on Intel's EtherExpress PRO/100 line of 10/100 boards
Which describes the driver and how to use it.
That being said, try
Code:
# modprobe e100
# ifconfig -a
and post the output.
If the modprobe command fails try eepro and/or eepro100
I've got the windows box set up as..
IP: 123.10.1.2
Subnet mask: 255.255.255.0
Default gateway: ??? (blank) >> What do I put here? <<
And what do I put for the DNS server stuff?
I assume that eth0 on the Linux box connects to a some sort of modem/router.
Completely change the 123.x.x.x ... it's not in the range of IP's reserved
for private use ... it will only cause you grief later. I suggest you use a
class C address subrange like 192.168.0.x or 192.168.2.x (making it a different
subrange to the one on eth0 should also make things easier)
Let's assume you use 192.168.0.101 for eth1 on the Linux box.
So, on the windows box:
IP: 192.168.0.2 (say)
NM: 255.255.255.0
GW: 192.168.0.101
2. Make the linux box do port forwarding:
# echo 1 > /proc/sys/net/ipv4/ip_forward
3. If you have iptables installed then you need to make a rule
to masquerade the packets from/to the windows box:
# iptables -t nat -A POSTROUTING -s 192.168.0.2 -j MASQUERADE
4. As far as DNS goes, there are a few ways of approaching it:
a) install a package like dnsmasq and set the dns of the windows
box to the ip of your linux box
b) just use normal masquerading and set the dns of the windows box
to the same setting that your linux box uses (isp or modem).
c) install bind on your linux box.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.