IP configuration

[sdi]

Hi,

I have an old Suse 8 installation on a vmware-host, where I had to change ip-adresses. Now something isn't working as it shouldn't:
- Proftpd isn't recognizing the old pw's (coming from a my-sql db)

I am not a real expert on linux, that's why I hope to get some help from you here.

The question is: where is the adress "192.168.1.37" configured on my machine?
the Mysql daemon is running on this IP.

I can ping it:

web10:~ # ping 192.168.1.37
PING 192.168.1.37 (192.168.1.37) from 192.168.1.37 : 56(84) bytes of data.
64 bytes from 192.168.1.37: icmp_seq=1 ttl=64 time=0.024 ms
64 bytes from 192.168.1.37: icmp_seq=2 ttl=64 time=0.023 ms

ifconfig result:

web10:~ # ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:0C:29:79:47:DF
          inet addr:88.198.100.35  Bcast:88.198.100.39  Mask:255.255.255.248
          inet6 addr: fe80::20c:29ff:fe79:47df/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:563 errors:0 dropped:0 overruns:0 frame:0
          TX packets:272 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:58845 (57.4 Kb)  TX bytes:23467 (22.9 Kb)
          Interrupt:19 Base address:0x2024

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:63 errors:0 dropped:0 overruns:0 frame:0
          TX packets:63 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5807 (5.6 Kb)  TX bytes:5807 (5.6 Kb)

sit0      Link encap:IPv6-in-IPv4
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

route:

web10:~ # route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
88.198.100.32    0.0.0.0         255.255.255.248 U     0      0        0 eth0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
0.0.0.0         88.198.100.33    0.0.0.0         UG    0      0        0 eth0

Any idea where else the IP 192.168.1.37 is configured?

[Mudgen]

Have you looked in proftpd.conf? I think there's a directive that tells proftpd where the sql backend is.

You don't really say why you're looking for 192.168.1.37, so there's not much to go on.

[Irithori]

OffTopic, but imho important:
That SuSE 8 now has a public IP?

You might want to consider a reinstall with a more recent version.
SuSE 8 was released in 2002.

[sdi]

Have you looked in proftpd.conf? I think there's a directive that tells proftpd where the sql backend is.

You don't really say why you're looking for 192.168.1.37, so there's not much to go on.

Yes, I have looked into that, that's how I found at that the mysqld is running on 192.168.1.37.

I would like to know where and how this IP has been set up. As I don't see this IP active when I do a "nslookup".

Very strange!

[sdi]

OffTopic, but imho important:
That SuSE 8 now has a public IP?

You might want to consider a reinstall with a more recent version.
SuSE 8 was released in 2002.

yes, it has and had a public IP, no updates have been done since ages on that machine though, but never had any issues.

Well, there are about 30 hosts running on it, mysql, proftpd (chrooted), exim for sending mails, and a custom made webconfig panel made by someone.

I am not able to do a update to a more recent version, as I really don' know how this system has been set up.

I have some other debian servers, which I regulary update.

The best thing would be to move those hosts to another updated server, but I am sure I will run into many problems then, as on this Suse server the Mysql databases are still v.4. And how should I move the webhosts?

Any idea?

[Irithori]

I would like to know where and how this IP has been set up. As I don't see this IP active when I do a "nslookup".

No offence, but shouldnt you be the one to know?

The nslookup fail indicates, that DNS is not setup properly.
At least it misses some entries.

May I suggest that you first get an overview and document what you have where and *document* what you find.
- Which serverhardware?
- Hardwarestatus?
- Hardware support still valid?
- Which networks/VLANs are used and for what? production, out-of-band, backup, storage,..
- DNS ok?
- Backup ok?
- Restore also?
- Which OSes are used?
- Patchlevel?
- Which daemons run where and why?
- Are they controlled by the package manager or are they customized source installs?
- If so, why was this done?
- Which applications run where and why?
- You say, there is a customized webpanel. Is this still needed or can it be replaced with a more recent and standard version?
- etc

As for the migration of the webhosts:
There will surely be problems: encoding, database issues, new php/perl/python/whatever.

So I would install a new machine in parallel and work on the issues until a migration plan is formulated.

[sdi]

Thanks for your reply.

The server works fine now after the IP-change. It is a vmware 2 guest.

I think I'll leave this machine as it is and urge the customers on it to get moved to a more recent system ... and shut this down within this yr then.

But I am still wondering where that ip is configured as it is up and running.

[Irithori]

As greyhairweenie mentioned: look into proftpd.conf.