current and rc.inet1.conf

Tshane · 12-06-2021, 01:21 AM

Does the new net conf file have a way of taking IP's we need to add to loopback?

in the past we just add it in rc.inet1 under 127.0.0.1
but this was wiped out with an update (not been updating the server for a while, i know, our bad), looking to find a way that future updates don't catch us sleepy hollows out again.

Windu · 12-06-2021, 01:27 AM

In slackware-current, the loopback address is still set to 127.0.0.1. I wonder if you broke something else?

Nobby6 · 12-06-2021, 06:35 AM

Quote:

Originally Posted by Tshane

Does the new net conf file have a way of taking IP's we need to add to loopback?

in the past we just add it in rc.inet1 under 127.0.0.1
but this was wiped out with an update (not been updating the server for a while, i know, our bad), looking to find a way that future updates don't catch us sleepy hollows out again.

I've found it's best to use rc.local to assign an extra IP to loopback

GazL · 12-06-2021, 08:36 AM

If you're looking for a way to setup virtual addresses, then I'd suggest using a 'dummy' interface rather than messing with aliases on loopback. It's what we used to use in the ppp/slip dialup days.

Tshane · 12-07-2021, 01:11 AM

Quote:

Originally Posted by GazL

If you're looking for a way to setup virtual addresses, then I'd suggest using a 'dummy' interface rather than messing with aliases on loopback. It's what we used to use in the ppp/slip dialup days.

Do you have experience with F5 ltm's? adding to loopback is what their docs say to do

Tshane · 12-07-2021, 01:14 AM

Quote:

Originally Posted by Nobby6

I've found it's best to use rc.local to assign an extra IP to loopback

thats one option I guess but that could be subject to overwrite too if we are not paying attention?
I was trying to see if the network configuration file would accept loopback , being the interfaces configuration file 'n all

GazL · 12-07-2021, 04:00 AM

Quote:

Originally Posted by Tshane

Do you have experience with F5 ltm's? adding to loopback is what their docs say to do

Nope. Never even heard of F5. All I can say is that in the old days we'd use 'dummy' to provide persistent addresses for this sort of stuff.

Whether F5 requires the address to be attached to lo specifically, or not, I can't speak to.

rinaldij · 12-07-2021, 12:31 PM

/etc/hosts?

Nobby6 · 12-08-2021, 12:11 AM

Quote:

Originally Posted by Tshane

thats one option I guess but that could be subject to overwrite too if we are not paying attention?
I was trying to see if the network configuration file would accept loopback , being the interfaces configuration file 'n all

if you're not paying attention, even rc.inet1.conf can be overwritten

I've always found rc.local the safewst option.

But if you insist, remember that rc.inet1 calls and "runs" that conf file to set its variables, although never tried it, no reason why you couldn't put your ip addr foo in there, since its loopback, it wont be affected by anything else that file does.

Nobby6 · 12-08-2021, 12:20 AM

Quote:

Originally Posted by GazL

Nope. Never even heard of F5. All I can say is that in the old days we'd use 'dummy' to provide persistent addresses for this sort of stuff.

Whether F5 requires the address to be attached to lo specifically, or not, I can't speak to.

They dont require it specifically, but its recommended since loopback does not participate in ARP