.132.120.2 (200.132.120.2): 56 data bytes
ping: sendto: No route to host
ping: wrote 200.132.120.2 64 chars, ret=-1
64 bytes from 200.132.120.2: icmp_seq=1 ttl=64 time=0.231 ms
64 bytes from 200.132.120.2: icmp_seq=2 ttl=64 time=0.238 ms
--- 200.132.120.2 ping statistics ---
3 packets transmitted,
e network.
You might examine RIP logs. Just a thought.
Now, every once in while I get errors like:
PING 200.132.120.2 (200.132.120.2): 56 data bytes
ping: sendto: No route to host
ping: wrote 200.132.120.2 64 chars, ret=-1
64 bytes from 200.132.120.2: icmp_seq=1 ttl=64 time=0.231 ms
64 byte
Hi,
It would help if someone with more experience with PF
could help me to interpret some of those statistics
shown with pfctl -si:
Packets In
Passed 468375730
Blocked 3024000 98
Packets Out
Passed
Hi,
Thanks very much for your help.
> (You mean routed.)
Exaclty. Thanks for the correction.
> I'm always suspicious of RIP. It's so easy for
> a rouge device to mess up the whole network.
> You might examine RIP logs. Just a thought.
I also suspect of routed. The output of "route monitor"
sh
Look at sysctl net.inet.ip.ifq, bump maxlen until drops stops
increasing. I'd try 250 for starters.
On 2007/07/07 08:47, Jeff Santos wrote:
> Hi,
>
> It would help if someone with more experience with PF
> could help me to interpret some of those statistics
> shown with pfctl -si:
>
> Packets
Hi,
Thanks a lot for your message.
> Look at sysctl net.inet.ip.ifq, bump maxlen until drops stops
> increasing. I'd try 250 for starters.
I followed your suggestion. It did help to reduce the frequency
of this kind of event. The drops seem to have stopped at 300.
net.inet.ip.ifq.len=0
net.ine
On 2007/07/19 12:15, Jeff Santos wrote:
>
> net.inet.ip.ifq.len=0
> net.inet.ip.ifq.maxlen=300
> net.inet.ip.ifq.drops=0
>
> However, the problem did not go away altogether. I would like to
> know if it has anything to do with the "memory" or "state
> mismatch" statistics below:
"state-mismatch"
Hi,
> "memory" is PFRES_MEMORY, this could well be it. the description
> is "Dropped due to lacking mem", it's triggered in quite a few
> places (grep for PFRES_MEMORY in /sys/dev/net/pf*).
I could not find any /sys/dev/net directory. Could that be a problem?
How could I allocate more memory for
Hi,
> "memory" is PFRES_MEMORY, this could well be it. the description
> is "Dropped due to lacking mem", it's triggered in quite a few
> places (grep for PFRES_MEMORY in /sys/dev/net/pf*).
I could not find any /sys/dev/net directory. Could that be a problem?
How could I allocate more memory for
On 2007/07/21 07:45, Jeff Santos wrote:
> > "memory" is PFRES_MEMORY, this could well be it. the description
> > is "Dropped due to lacking mem", it's triggered in quite a few
> > places (grep for PFRES_MEMORY in /sys/dev/net/pf*).
>
> I could not find any /sys/dev/net directory. Could that be a p
t;route -s" because there is a need
> to publish RIPv1 routes for these networks.
>
> Now, every once in while I get errors like:
>
> PING 200.132.120.2 (200.132.120.2): 56 data bytes
> ping: sendto: No route to host
> ping: wrote 200.132.120.2 64 chars, ret=-1
> 64 by
11 matches
Mail list logo