Allocating a particular network config to a specific network card on startup

More
3 years 4 months ago #274211 by Waldemar
So I've dropped a second network card into my Linux box so that I can access a shared folder over on my Windows CAD machine (and do away with the somewhat tedious USB stick file transfers...)

All working very nicely, but one thing that I'd like to do is set the Linux OS to automatically select the correct network for the intended purpose - for example: occasionally on start-up Linux will assign the Ethernet Connection to Mesa 7i96 config to the network card that's connected to the local network and the Ethernet Connection to Laptop config to the network card that's plugged into the Mesa card.

It's simply a case of assigning the correct network config to the relevant hardware to fix this at the start of the session, but it would be nice if it was all set correctly on start-up.

Any ideas?

Wal.

image missing http://waldemar.x10host.com/misc/IMG_20230625_185837109_MFNR.jpg

Please Log in or Create an account to join the conversation.

More
3 years 4 months ago #274213 by tommylight

Please Log in or Create an account to join the conversation.

More
3 years 4 months ago #274227 by rodw
Should just happen. set a fixed IP address for your mesa card eg 10.10.10.1 and leave the other one to use DHCP. eg should end up in the 192.168.1.X range assuming your router is 192.168,1.1

Please Log in or Create an account to join the conversation.

More
3 years 4 months ago #274230 by Waldemar
Hi rodw,

Yep - both IPs are static - I'll try using DHCP for the connection to the laptop - I'm not using a router though, just s simple 5 port switch, so that may present an issue (the laptop is in the 192.168 range - also on a static IP).

tommylight - I'll have a dig around.

Wal.

Please Log in or Create an account to join the conversation.

More
3 years 4 months ago #274241 by tommylight
Mesa boards should be wired dirrctly to the PC, never through a hub or switch.
That was my initial thought on the issue, but skipped as it should be mentioned everywhere.
Apparently ut is not mentioned enough. :)
Also, use two subnets, meaning, set the Mesa board to 10.10.10.10 and edit the PC accordingly.
The following user(s) said Thank You: rodw

Please Log in or Create an account to join the conversation.

More
3 years 4 months ago #274243 by Waldemar
Sure thing - the Mesa is directly wired to the on-board ethernet and the additional card is doing the biz for the networking side of things.

Mesa uses the 10.10... network ID and the networking config is on something totally different. It all works wonderfully, just the luck of the draw when it comes to which config the OS assigns to which card on startup.

One way around this is to not power up my control box (which houses the Mesa card) until the OS has booted, that way the system always assigns the networking config to the card that's connected to the network and the Mesa connection goes active when I fire up the control box and the Mesa card gets power. It's odd that this happens, but it's no big deal, I was just wondering if you could force a network card to adopt a config (the same config) on startup.

Wal.

Please Log in or Create an account to join the conversation.

Time to create page: 0.559 seconds
Powered by Kunena Forum