Gabriel,
i use the 2.6.23 kernel, so i can't tell you exeactly what you need to
change in youre 2.6.2 kernel config to make this work. Sorry about that.
I can give you the kernel configuration file (.config) i used. Note that
there might be variables defined here that are not present yet in the
.22 kernel or others that you have and i don't. But the basic idea is to
disable the HPET and enable the RTC stuff again.
You can change them directly in the .config or use the make xconfig or
make menuconfig. After, build youre kernel again see if you get the
interrupts.
>grep RTC .config
CONFIG_RTC=m
CONFIG_GEN_RTC=m
CONFIG_GEN_RTC_X=y
CONFIG_RTC_LIB=m
CONFIG_RTC_CLASS=m
# RTC interfaces
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set
# SPI RTC drivers
# Platform RTC drivers
CONFIG_RTC_DRV_CMOS=m
CONFIG_RTC_DRV_DS1553=m
CONFIG_RTC_DRV_STK17TA8=m
CONFIG_RTC_DRV_DS1742=m
CONFIG_RTC_DRV_M48T86=m
CONFIG_RTC_DRV_M48T59=m
CONFIG_RTC_DRV_V3020=m
# on-CPU RTC drivers
>grep HPET .config
# CONFIG_HPET_TIMER is not set
# CONFIG_HPET is not set
>grep TIM .config
CONFIG_GENERIC_TIME=y
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_X86_CYCLONE_TIMER=y
# CONFIG_HPET_TIMER is not set
CONFIG_X86_PM_TIMER=y
# CONFIG_IPV6_OPTIMISTIC_DAD is not set
# CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION is not set
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
# CONFIG_HANGCHECK_TIMER is not set
# CONFIG_PRINTK_TIME is not set
CONFIG_TIMER_STATS=y
CONFIG_KTIME_SCALAR=y
João Gabriel G. Granado Rodrigues wrote:
Hello there!
Thank you very much for your reply, Ernst!
I am sorry but I couldn't understand exactly what is the problem and how
do I fix it...
I did build my kernel from source, doing the things recommended in
readme.redhat of nistnet:
turn off module versioning and
install the enchanced real time clock support as module
Also before making nistnet i had to
- apply a patch before making nistnet as in:
http://www.stabellini.net/nistnet.html
<http://www.stabellini.net/nistnet.html>
- change the code of nistnet_table.c myself (This is because I am using
a more recent kernel (2.6.22-9) than the patch is good for, and there
was a modification on the kernel I use... I can get you more details if
you want)
I am not a linux expert, so it's possible I made some mistake in these
steps...
To call nistnet, I do make the famous steps of:
mknod /dev/hitbox c 62 0
mknod /dev/nistnet c 62 1
chown root /dev/hitbox
chown root /dev/nistnet
mknod /dev/mungebox c 63 0
chown root /dev/mungebox
mknod /dev/spybox c 64 0
chown root /dev/spybox
and then I do a:
rmmod rtc
modprobe nistnet
cnistnet -u
my output for: cnistnet -G is:
Emulator is: On
Average processed packet overhead 3 usec
Average unprocessed packet overhead 3 usec
Average hash tries 0
The command: cat /proc/interrupts shows 0 interrupts for irq 8.
I can see this is a problem, but I don't know why this happens, and
neither how to fix it...
Thank you for your patience!
Gabriel
On Nov 21, 2007 8:10 AM, Ernst van der Plas <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Gabriel,
youre nistnet irq 8 is kernel module is not running. It is installed
but it does not reveive any interrupts. From the 'cat' you send it seems
youre are using the HPET timers instead of the rtc timer.
youre system:
8: 0 IO-APIC-edge fast_rtc
my system which does work.
8: 1409690531 0 IO-APIC-edge fast_rtc
Where youres says 0: this is the number of irq 8 interrupts you had. I
build the kernel from source and disabled the HPET timers and enabled
the RTC timers. Then when you want to start nistnet, do a rmmod of the
rtc-cmos, cause that is holding irq 8. Optionally you can install the
module rtc, since nistnet wants to deinstall it.
Regards,
Ernst
ps please keep this on the list, so more people can react to it.
João Gabriel G. Granado Rodrigues wrote:
> Hello Ernst!
>
> I was giving another try on my nistnet installation, and I realized I
> could make the drops rule to work, but no the delay.
> If I do
>
> cnistnet -a :.icmp :.icmp --drop 50
>
> It works fine... but if I do (removing the other rule first)
>
> cnistnet -a :.icmp :.icmp --delay 10
>
> I get 100% of packet loss when I try to ping the nistne machine.
Also,
> my output for
>
> cnistnet -s :.icmp :.icmp --delay 10
>
> shows me that I have the ping packets in my queue (qsize = 10). If I
> flush nistnet (cnistnet -F) the pings are all answered.
>
> In a e-mail you sent to me, you taught about irq 8...
> this is the output for my cat /proc/interrupts
> [EMAIL PROTECTED] nistnet-3.0a]# cat /proc/interrupts
> CPU0
> 0: 294 IO-APIC-edge timer
> 1: 2 IO-APIC-edge i8042
> 6: 5 IO-APIC-edge floppy
> 7: 0 IO-APIC-edge parport0
> 8: 0 IO-APIC-edge fast_rtc
> 9: 1 IO-APIC-fasteoi acpi
> 12: 748209 IO-APIC-edge i8042
> 14: 39142 IO-APIC-edge libata
> 15: 0 IO-APIC-edge libata
> 16: 2119810 IO-APIC-fasteoi HDA Intel,
[EMAIL PROTECTED]:0000:01: 00.0
> 17: 1863766 IO-APIC-fasteoi eth0
> 18: 2 IO-APIC-fasteoi uhci_hcd:usb1, ehci_hcd:usb5
> 19: 0 IO-APIC-fasteoi uhci_hcd:usb2
> 20: 14334 IO-APIC-fasteoi uhci_hcd:usb3
> 21: 0 IO-APIC-fasteoi uhci_hcd:usb4
> 22: 125578 IO-APIC-fasteoi libata
> NMI: 0
> LOC: 23581948
> ERR: 0
> MIS: 0
>
> This means it is right or not?
>
> Thank you for your help!
>
> Gabriel
>
> On Oct 24, 2007 7:17 AM, Ernst van der Plas <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
> <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> wrote:
>
> Hi,
>
> can you draw youre setup. I used 2.6.23 and the next setup
which
> works fine.
>
> ----------- -------------------------------
-----------
> |172.16.77.1|---|172.16.77.2 nistnet
172.16.76.2|---------|172.16.76.1|
> ----------- -------------------------------
-----------
>
> You also need to check if there are interrupts commong on irq
8, in "cat
> /proc/interrupts". These are are needed by nistnet to get the
delay
> working. If you use drop does that work ?
>
> regards,
> Ernst
>
>
>
>
> João Gabriel G. Granado Rodrigues wrote:
> > Well, just updating things...
> >
> > these are my outputs:
> >
> > [EMAIL PROTECTED] nistnet-3.0a]# cnistnet -R
> > cnistnet -a poseidon.laas.fr <http://poseidon.laas.fr> <
http://poseidon.laas.fr>
> <http://poseidon.laas.fr <http://poseidon.laas.fr>>
> telemaque.laas.fr <http://telemaque.laas.fr>
<http://telemaque.laas.fr>
> > < http://telemaque.laas.fr> --delay 10.000
> > cnistnet -a telemaque.laas.fr <http://telemaque.laas.fr>
<http://telemaque.laas.fr <http://telemaque.laas.fr>>
> <http://telemaque.laas.fr>
> > poseidon.laas.fr <http://poseidon.laas.fr> <
http://poseidon.laas.fr> <
> http://poseidon.laas.fr> --delay 10.000
> >
> > [EMAIL PROTECTED] nistnet-3.0a]# cnistnet -G
> > Emulator is: On
> > Average processed packet overhead 6 usec
> > Average unprocessed packet overhead 3 usec
> > Average hash tries 0
> >
> >
> > Well, i've tried a few sugestions and when I do (i removed
the others
> > rules):
> >
> > cnistnet -a *MailScanner warning: numerical links are often
> malicious:*
> > *MailScanner warning: numerical links are often malicious:*
> *MailScanner warning: numerical links are often malicious:*
0.0.0.0 <http://0.0.0.0> <*MailScanner warning: numerical links are
often malicious:* http://0.0.0.0> <*MailScanner warning: numerical
links are
> often malicious:* *MailScanner warning: numerical links are
often malicious:* http://0.0.0.0> *MailScanner warning: numerical
> links are often
> > malicious:* *MailScanner warning: numerical links are often
> malicious:* *MailScanner warning: numerical links are often
malicious:* 0.0.0.0 <http://0.0.0.0> <*MailScanner warning:
numerical links are often malicious:* http://0.0.0.0> <*MailScanner
warning:
> numerical links are often malicious:* *MailScanner warning:
numerical links are often malicious:* http://0.0.0.0> --delay 10
> >
> > my network stops working. I believe this is sign nistnet
works (maybe
> > not as it should)
> >
> > then when I switch to this rule:
> >
> > cnistnet -a *MailScanner warning: numerical links are often
> malicious:*
> > *MailScanner warning: numerical links are often malicious:*
> *MailScanner warning: numerical links are often malicious:*
0.0.0.0:0 <http://0.0.0.0:0> <*MailScanner warning: numerical links
are often malicious:* http://0.0.0.0:0> <*MailScanner warning:
numerical links
> are often malicious:* *MailScanner warning: numerical links
are often malicious:* http://0.0.0.0:0>.icmp *MailScanner warning:
> numerical links
> > are often malicious:* *MailScanner warning: numerical
links are
> often malicious:* *MailScanner warning: numerical links are
often malicious:* 0.0.0.0:0 <http://0.0.0.0:0> <*MailScanner
warning: numerical links are often malicious:* http://0.0.0.0:0>
<*MailScanner
> warning: numerical links are often malicious:* *MailScanner
warning: numerical links are often malicious:* http://0.0.0.0:0
> >.icmp --delay 1
> >
> > my network works fine, but if i try to ping, this is what
i get:
> >
> > [EMAIL PROTECTED] ~]$ ping telemaque
> > PING telemaque.laas.fr <http://telemaque.laas.fr>
<http://telemaque.laas.fr>
> < http://telemaque.laas.fr> (*MailScanner warning:
> > numerical links are often malicious:* *MailScanner warning:
> numerical links are often malicious:* *MailScanner warning:
numerical links are often malicious:* 140.93.2.191
<http://140.93.2.191> <*MailScanner warning: numerical links are
often malicious:* http://140.93.2.191>
> > <*MailScanner warning: numerical links are often malicious:*
> *MailScanner warning: numerical links are often malicious:*
http://140.93.2.191>) 56(84) bytes of data.
> >
> > --- telemaque.laas.fr <http://telemaque.laas.fr> <
http://telemaque.laas.fr> <
> http://telemaque.laas.fr> ping statistics ---
> > 14 packets transmitted, 0 received, 100% packet loss, time
12999ms
> >
> > No packets at all!
> >
> > any idea?
> >
> > gabriel
> > On 10/23/07, *João Gabriel G. Granado Rodrigues *
> > < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> <mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>
> <mailto: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
> <mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>>> wrote:
> >
> > Hello there!
> >
> > After a few days of a lot of tries, i finally succeeded to
> compile
> > NistNet on Fedora Core 7, using kernel 2.6.22.9-91.
> >
> > Now, I am trying to use it. From what I've read in the
Internet,
> > including this mail list, I'd better use NistNet in a
linux box
> > configured as router. And also, have two more boxes
attached
> to it.
> > (Is this right?)
> > Well... I've talked to my boss to get this hardware
set up, but
> > until there, I got one question:
> >
> > I running nistnet in a machine with a single NIC. I've
tried
> to add
> > rules for delay like:
> >
> > cnistnet -a telemaque poseidon --delay 10
> > cnistnet -a poseidon telemaque --delay 10
> >
> > Where telemaque is my machine and poseidon is another
machine
> in the
> > LAN.
> > Nistnet is running and up, and the rules are implemented
> without errors.
> >
> > But, when I try to ping one machine from another,
nistnet has no
> > effect at all on then.
> > Should't nistnet delay the packets coming from
poseidon to my
> > machine (telemaque)? What am I missing?
> >
> > Thank you!!
> >
> > Gabriel
> >
> >
> >
> > --
> > This message has been scanned for viruses and is believed
to be
> clean.
> >
> >
> >
>
------------------------------------------------------------------------
> >
> > _______________________________________________
> > nistnet mailing list
> > nistnet@antd.nist.gov <mailto:nistnet@antd.nist.gov>
<mailto: nistnet@antd.nist.gov <mailto:nistnet@antd.nist.gov>>
> > http://www-x.antd.nist.gov/mailman/listinfo/nistnet
<http://www-x.antd.nist.gov/mailman/listinfo/nistnet>
>
>
> --
> This message has been scanned for viruses and is believed to
be clean
>
>
>
> --
> This message has been scanned for viruses and is believed to be
clean.
--
This message has been scanned for viruses and is believed to be clean
--
This message has been scanned for viruses and is believed to be clean.
------------------------------------------------------------------------
_______________________________________________
nistnet mailing list
nistnet@antd.nist.gov
http://www-x.antd.nist.gov/mailman/listinfo/nistnet
--
This message has been scanned for viruses and is believed to be clean
_______________________________________________
nistnet mailing list
nistnet@antd.nist.gov
http://www-x.antd.nist.gov/mailman/listinfo/nistnet
