Must I "append" the LILO to make the eth1 card work?
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.
Must I "append" the LILO to make the eth1 card work?
Hi,
Been several hours working to get two linux boxes to form a simple intranet. Box one is eth1, a firewall box, and box 2 is the DMZ eth0.
Both cards seem recognized. ifconfig works good, both can ping themselves, and localhost, so, I'm reviewing what might NOT be ok... so?
IF an NIC card appears UP and pings, and that box will accept ifconfig changes... that card works? or is there some further redundant file in LILO which must also be toyed with to get two boxes to handshake... thanks for the clues.
piratebiter
should be simple... box a says Howdy, box b says yup, right?
Re: Must I "append" the LILO to make the eth1 card work?
Quote:
Originally posted by piratebiter Box one is eth1, a firewall box, and box 2 is the DMZ eth0.
First of all, the ethx designations refer to NICs in a single machine. That is, within a single computer, the first (or only) installed network interface will be designated eth0; if the box has multiple NICs installed, the numbering will increment from there (second NIC=eth1, third NIC=eth2, etc.).
Quote:
Originally posted by piratebiter IF an NIC card appears UP and pings, and that box will accept ifconfig changes... that card works?
If ifconfig indicatees that the NIC is up and you can ping it, tht's a very good indication that the card itself is functioning correctly.
Quote:
Originally posted by piratebiter or is there some further redundant file in LILO which must also be toyed with to get two boxes to handshake
Nope, the problem lies elsewhere. You need to tell us how the two boxes are networked together (hub? router? switch? crossover cable?) in order for us to get to the root of the problem most quickly.
thanks, I thought IF you can ping andIF ifconfig works then the cards are recognized, they show UP... now what do I have going which might help you help me?
Box 1 is a firewall box with three cards. eth0 to the net static IP DSLmodem... eth1 is to be LAN (haven't done that yet) but it is recognized,
Problem begins with : eth2 on the firewall box to be DMZ... I have it's IP addr as 192.168.1.1 with a netmask of 255.255.255.0 and broadcast is 192.168.1.255, network 192.168.1.0 and gateway 192.168.1.1.
Box 2 is the DMZ server and it's eth0 card: ip addr of 192.168.1.2 with a netmask 255.255.255.0 and broadcast 192.168.1.255, network 192.168.1.0, gateway 192.168.1.1
So I think? they sit on the same subnet. These two boxes are common to/thru a cisco switch which has "lites on" and works fine (totally transparent, i think it looks at MAP not tcp?, anyway). The route is eth1 from the firewall box to the switch and eth0 from the DMZ to the switch.
the hosts file on each box has 127.0.0.1 localhost
192.168.1.1 firewall box
192.168.1.2 DMZ serve
One thing I think I see in routes table is the gateway is *... no address.
so ? why? I've told it the gateway192.168.1.1, right... which is also the firewall card eth1... this is a little hazy for me... the card? has an ip addr same as it's gateway?
see? I'm a little lost huh?
any help is apreciated.
thanks for the reply,
piratebiter
flipped eth0 with eth2 on the firewall box... and the DMZ subnet works. so the ? changes a little... 1. no one else has ever made this dumb error right, mixed up the cables ot avarious cards? ... & how in the heck do I keep track of three ethx cards all with the same driver... 2 905s and a 980. It would be keen to NAME these cards sumthing so I can understand what I'm actually messing with... yet, of course I'm ready to move on... thanks for the help. Time to eat.
p. biter
Originally posted by piratebiter thanks, I thought IF you can ping andIF ifconfig works then the cards are recognized, they show UP
Yes, that would indicate that the cards themselves are working, but it has no bearing on the status of any connectivity between the separate cards.
Quote:
Originally posted by piratebiter eth2 on the firewall box to be DMZ... I have it's IP addr as 192.168.1.1 with a netmask of 255.255.255.0 and broadcast is 192.168.1.255, network 192.168.1.0 and gateway 192.168.1.1.
Box 2 is the DMZ server and it's eth0 card: ip addr of 192.168.1.2 with a netmask 255.255.255.0 and broadcast 192.168.1.255, network 192.168.1.0, gateway 192.168.1.1
So I think? they sit on the same subnet.
Yes, they do. One thing that sounds wrong is the fact that you seem to say that the gateway address of the firewall box is pointing to its own internal (LAN-facing) 192.168.1.1 interface. That should be the gateway IP that all other boxes on your LAN look to, but if I'm understanding your setup, that's not what you want on the firewall box.
Quote:
Originally posted by piratebiter These two boxes are common to/thru a cisco switch which has "lites on" and works fine (totally transparent, i think it looks at MAP not tcp?, anyway).
You mean MAC, not MAP- but yes, that's correct.
Quote:
Originally posted by piratebiter One thing I think I see in routes table is the gateway is *... no address.
can you post your full routing table from box #2?
<edit>
Oops, didn't see your last post. Time me to eat too, so off I go...
hmm... the gateway address on the firewall box eth2 card is the same as the IP address now... yet? what should it be?... right now it is 192.168.1.1 for the IP addr and the gateway addr on that card. It is supposed to look to the DMZ server and be the DMZ gateway card for the firewall. I wonder what the correct gateway addres would be on that card... ? Anyone who knows could assist here. I am pretty new at setting up networks. And I will help by NOT crossing up the cat 5 cables anymore... at least for awhile thanks much for all the asist.
P.Biter
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.