Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
alright, i have two networks in this house i'm living in, and want to set up a fileserver to serve both networks. I have the server here, am familiar with linux, and used this server at home for a while before bringing it here. it is currently working on the first network listed below.
I tried configuring this on my own, and came really close, but some weird things would happen when both networks were connected at once, so i'm looking for a real procedure to do this, so i can find whatever oversight(s) i made. The server is restored to being configured for only the first network, and it works perfectly. Both networks use a flavor of linksys router, with which i'm very familiar (configured tens of them over the years, used them at home and work for 4 years or so)
Network 1: currently working
uses static IPs
gateway is 192.168.0.1
subnet mask 255.255.255.0
Network 2: not configured or anything
gateway is 192.168.1.1
all other default linksys network stuff which i'm sure you're all familiar with
Both NICs are integrated into the motherboard of the server and work fine. I won't bother explaining the weird things that happened when i was configuring them on my own, because i'm sure it was just a mistake or oversight i made.
So i have samba, http, ftp, ssh, and all other kindsa stuff working on the first network fine, and at the very least i want samba working on the second network. I had this working, but the second network connection interfered with all kindsa other stuff that was supposed to work on the first network.
Ideally, all of those services would work on both networks.
I'm familiar with /etc/network/interfaces and i'm sure i can handle whatever else you throw at me, but I'm incredibly anxious to get this working, esp after spending about a week googling, configuring, and doing some experimenting as well.
The server is running debian, and, as i said, it is retroconfigured to just the first network and is fully functional
help! (and thanks)
edit: both networks have active internet connections, and I guess I would somehow need to specify the default network to use for outgoing internet stuff, so i figured you should know that.
Last edited by FliesLikeABrick; 09-13-2005 at 04:00 PM.
Hmmm. I'm not familiar with /etc/network/interfaces (it's all RedHat style at my end).
If that's the way you would normally get a DHCP interface up and running, then yes, I'd do that. Once the interface is up (and assigned an IP address etc), post the output from 'route' and we'll see what DHCP has decided to do to the routing tables.
Once dhclient finishes what it's doing you should have both ethernet devices up, and both should have an IP address. You can check this by running 'ifconfig'.
The two records for eth0 are OK: the:
'192.168.0.0 * 255.255.255.0 U 0 0 0 eth0'
line means anything destined for the 192.168.0.0 subnet should go through eth0 (which is fine).
'default 192.168.0.1 0.0.0.0 UG 0 0 0 eth0'
line means any packets for subnets which aren't known about should go through eth0 to the default gateway, which is 192.168.0.1. (Which is also fine).
Cool. I edited my last post just before you posted there, so you may not have seen the bit about removing the duplicate lines. It shouldn't make any difference though.
P.S. You should probably statically assign the server IP addresses for *both* interfaces, and configure the router on the .1.0 subnet (which is doing DHCP) to reserve the IP address for eth1, so that you don't have to look up which IP address that has been assigned to your server. Not strictly speaking necessary, but it should make things easier should you have to reboot the server.
well unfortunately this server will probably get reset relatively often, and i definately need it to work from boot. so what does the routing table ideally need to look like to survive a reboot, and what else do i need to do to survive a reboot?
edit: ok, i removed the default line for 192.168.1.1, i figured that was what was causing the problems. but how do i keep this from coming back on reboot?
Last edited by FliesLikeABrick; 09-13-2005 at 08:26 PM.