 www.centos.org Forum Index CentOS 6 - General Support  Why can ip_conntrack be interpreted as nf_conntrack?
|
 Bottom  Previous Topic  Next Topic |
|
|
|
|
|---|
Topic options
Threaded
Newest First| Poster | Thread |
|---|
|
Why can ip_conntrack be interpreted as nf_conntrack? | #1 |
|
|---|---|---|---|
|
Regular Board Member
 
Joined: 2007/5/1
From
Posts: 116
|
Hello.
The ip_conntrack, ip_nat_ftp, ip_conntrack_ftp have been renamed to nf_conntrak, nf_nat_ftp and nf_conntrack_ftp. Further, I cannot find ip_... modules, there are only nf_... modules. But I can successfully issue "modprobe ip_conntrack", after that, with "lsmod", I see the nf_conntrack loaded. How can "modprobe" interpret ip_conntrack as nf_conntrack. Thanks. |
||
Posted on: 2012/8/20 14:59
  |
 |
||
taolei
|
Re: Why can ip_conntrack be interpreted as nf_conntrack? | #2 |
|
|---|---|---|---|
|
Peeking in the Member Window
Joined: 2011/12/5
From
Posts: 15
|
Hi,
Can you control /etc/modprobe.d/blacklist.conf file ? |
||
Posted on: 2012/8/21 8:57
|
|
||
|
Re: Why can ip_conntrack be interpreted as nf_conntrack? | #3 |
|
|---|---|---|---|
|
Regular Board Member
Joined: 2007/5/1
From
Posts: 116
|
Hi, hasanakgoz.
I wonder why "modprobe" can interpret ip_conntrack as nf_conntrack (There not exist ip_conntrack module at all). This seems not to be related with blacklist.conf. The following is content of /etc/modprobe.d/blacklist.conf # # Listing a module here prevents the hotplug scripts from loading it. # Usually that'd be so that some other driver will bind it instead, # no matter which driver happens to get probed first. Sometimes user # mode tools can also control driver binding. # # Syntax: see modprobe.conf(5). # # watchdog drivers blacklist i8xx_tco # framebuffer drivers blacklist aty128fb blacklist atyfb blacklist radeonfb blacklist i810fb blacklist cirrusfb blacklist intelfb blacklist kyrofb blacklist i2c-matroxfb blacklist hgafb blacklist nvidiafb blacklist rivafb blacklist savagefb blacklist sstfb blacklist neofb blacklist tridentfb blacklist tdfxfb blacklist virgefb blacklist vga16fb blacklist viafb # ISDN - see bugs 154799, 159068 blacklist hisax blacklist hisax_fcpcipnp # sound drivers blacklist snd-pcsp # I/O dynamic configuration support for s390x (bz #563228) blacklist chsc_sch |
||
Posted on: 2012/8/21 15:18
|
|
||
|
Re: Why can ip_conntrack be interpreted as nf_conntrack? | #4 |
|
|---|---|---|---|
|
Peeking in the Member Window
Joined: 2011/12/5
From
Posts: 15
|
You're right I got it wrong. IPv4 support your system available? ip_conntrack is the old IPv4-only implementation.
|
||
Posted on: 2012/8/24 3:44
|
|
||
 Top Previous Topic Next Topic |
 |
|
You cannot start a new topic.
You can view topic.