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.
I have an SBC with ethernet and wifi devices. If, for example, I assign the ethernet device to 192.168.15.200 and the wifi to 192.168.15.150 both with netmask 255.255.255.0, whichever device was brought up first works but the second one doesn't e.g. I can ping the first address/device from another computer on the network but not the second. If I ifconfig down the first device, I can then ping the second. What am I not configuring correctly?
Hmm...okay, I'll mess around with the addresses. Shouldn't I also have to change the netmask to 255.255.0.0 to get that different subnet to work?
As for not using DHCP, I do that on my laptop and the Airport has it running but the SBCs are faceless so I would have no clue what the address might be each time I boot it and no way of figuring it out without plugging in the serial console cable.
netmask 255:255:255:0 is correct for class C IPv4 addresses (private addresses) like 192.168.x.x
Those first two bytes define the address class, the third defines the subnet within the class and the fourth byte defines the host (0..254), so all three bytes effectively define the subnet (the one's in the mask, 255=0xff).
Don't know about Airport. Some devices allow you to associate fixed IP's with physical (MAC) addresses (so-called "Static DHCP", an oxymoron). I believe all Airports will allow you to interrogate the DHCP table to learn what address has been assigned.
And, that might not work for you.
If I understand your topology correctly (not at all sure I do), what I'm suggesting may not be possible. If both interfaces need to connect to the Airport, they will need to be on the same subnet as its LAN... You may need more advanced routing on the SBC...