|
Lars,
Thank you for the suggestion. I tried it and looked at the man page again.
However, I still get a similar response.
/lib/modules/2.2.17/ipv4/ip_masq_ftp.o: unresolved symbol
ip_masq_skb_replace_Rsmp_672fb649
/lib/modules/2.2.17/ipv4/ip_masq_ftp.o: unresolved symbol
ip_masq_control_add_Rsmp_78be8c78
/lib/modules/2.2.17/ipv4/ip_masq_ftp.o: unresolved symbol
ip_masq_put_Rsmp_5e752b0d
/lib/modules/2.2.17/ipv4/ip_masq_ftp.o: unresolved symbol
ip_masq_new_Rsmp_1cc34fd1
/lib/modules/2.2.17/ipv4/ip_masq_ftp.o: unresolved symbol
ip_masq_in_get_Rsmp_3fbd43b0
/lib/modules/2.2.17/ipv4/ip_masq_ftp.o: unresolved symbol
unregister_ip_masq_app_Rsmp_bbc84e34
/lib/modules/2.2.17/ipv4/ip_masq_ftp.o: unresolved symbol
ip_masq_listen_Rsmp_8e292da2
/lib/modules/2.2.17/ipv4/ip_masq_ftp.o: unresolved symbol
ip_masq_out_get_Rsmp_27b7c4d9
/lib/modules/2.2.17/ipv4/ip_masq_ftp.o: unresolved symbol
register_ip_masq_app_Rsmp_938aa0b0
/lib/modules/2.2.17/ipv4/ip_masq_ftp.o: insmod
/lib/modules/2.2.17/ipv4/ip_masq_ftp.o failed
/lib/modules/default/ipv4/ip_masq_ftp.o: unresolved symbol
ip_masq_skb_replace_Rsmp_672fb649
/lib/modules/default/ipv4/ip_masq_ftp.o: unresolved symbol
ip_masq_control_add_Rsmp_78be8c78
/lib/modules/default/ipv4/ip_masq_ftp.o: unresolved symbol
ip_masq_put_Rsmp_5e752b0d
/lib/modules/default/ipv4/ip_masq_ftp.o: unresolved symbol
ip_masq_new_Rsmp_1cc34fd1
/lib/modules/default/ipv4/ip_masq_ftp.o: unresolved symbol
ip_masq_in_get_Rsmp_3fbd43b0
/lib/modules/default/ipv4/ip_masq_ftp.o: unresolved symbol
unregister_ip_masq_app_Rsmp_bbc84e34
/lib/modules/default/ipv4/ip_masq_ftp.o: unresolved symbol
ip_masq_listen_Rsmp_8e292da2
/lib/modules/default/ipv4/ip_masq_ftp.o: unresolved symbol
ip_masq_out_get_Rsmp_27b7c4d9
/lib/modules/default/ipv4/ip_masq_ftp.o: unresolved symbol
register_ip_masq_app_Rsmp_938aa0b0
/lib/modules/default/ipv4/ip_masq_ftp.o: insmod
/lib/modules/default/ipv4/ip_masq_ftp.o failed
/lib/modules/default/ipv4/ip_masq_ftp.o: insmod ip_masq_ftp failed
When looking through the man pages I found reference to a "default"
directory in the /lib/modules path. I didn't have one, so I made a link to
the directory of the current kernel version.
Whenever I run insmod to try and insert the module to the kernel, I get the
ip_masq_ftp failed error.
I wish it would be more specific when it says "unresolved symbol". Running a
-v doesn't produce any more info.
-----Original Message-----
From: Lars Marowsky-Bree [mailto:lmb@xxxxxxx]
Sent: Wednesday, November 29, 2000 9:32 AM
To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: RE: Source IP address
On 2000-11-29T09:33:22,
Nathan Polonski <Nathan.Polonski@xxxxxxxxxxxx> said:
> Horms,
> I ran the Bastille script against the server, and during that script I
> enabled the ip_masq_ftp module.
> However, I am not quite sure how to test to make sure that the module is
> being loaded properly.
>
> If I run insmod -v -p ip_masq_ftp.o in my /lib/modules/2.2.17 directory I
> get the following ouput:
You should be using "modprobe ip_masq_ftp". This will also load all the
modules ip_masq_ftp depends on.
Sincerely,
Lars Marowsky-Brée <lmb@xxxxxxx>
Development HA
--
Perfection is our goal, excellence will be tolerated. -- J. Yahl
_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://www.in-addr.de/mailman/listinfo/lvs-users
|
