FreeBSD, happy ping, was miserable ipv6 ping latency through freebsd 4.7 as router

comp.unix.bsd.freebsd.misc - FreeBSD operating system.


FreeBSD >> happy ping, was miserable ipv6 ping latency through freebsd 4.7 as router

by Mr Happy » Sat, 05 Jul 2003 05:42:43 GMT

Kirk Strauser wrote:

>
>>I think the freenet6 gobbles gif0--their binary is non-hackable of course,
>>sigh. Otherwise I'd just swap the gifs around.
>
>
> That couldn't be farther from the truth. When the client runs, it calls
> OS-specific scripts to do the actual network setup. In our case, look at:
>
> /usr/local/bin/tspc-freebsd44.sh
>
> Hack it to your heart's content.

Hi Kirk--

Yah some parts can be hacked. Actually my script is in
/usr/local/tsp/template and I'm using the 0.9.8 client.

Well the ping is happy now anyways--must have been
a problem between the chair and the keyboard :)

Now its just the reverse dns wont work. This is a freenet6
issue tho. Thanks for the replies.

../Steven



Top
Similar Threads

1. miserable ipv6 ping latency through freebsd 4.7 as router - FreeBSD

2. ping dns problem on freebsd 4.7 

for some reason when i ping a host that is dead i get replies from my wan
interface. but when i ping a host alive i get replies from the host alive.
can anyone tell me what is happenning? i believe it is dns but i am not 
sure. how can i fix this. thanks

3. IPv6 Multicast Listener Discovery (MLD) with FreeBSD 4.7 - FreeBSD

4. Freebsd router can't ping wireless client 

Hi,

My freebsd router configured as wireless router (with manual encryption 
key).
When I login the router thru this Windows desktop, I tried to ping my 
windows desktop, but surprisingly it doesn't show icmp echo reply.
I have the PF firewall rule enbaled as "pass quick on ath0 keep state". 
So I supposed it can reach my windows machine. But if connectoin is not 
available, my windows desktop won't able to go to the internet thru this 
router.

Can anyone please help?
Any suggestion and hints are much appreciated.

Thanks
S

5. Linux host PC(ipv6) can't ping with embedded board(ipv6) with ping6

6. Shorewall and ping latency 

Hi

I'm setting up a firewall based on Shorewall 2.2 from Debian stable
(sarge). It seems to work just fine, but I have a weird thing
happening when using ping and other ICMP traffic.

The box is a 2.8 GHz with 1 GB of memory. It has 3 gigabit ethernet
adapters, and I'm not loading it with a lot of traffic at this point.

When shutting down Shorewall I have a ping latency at around 0.1 ms
from my local network to the firewall, but as soon as I enable
Shorewall the latency goes up to about 25-30 ms.

However, if I traceroute through the firewall to some other host on
the internet it replies quickly in less than 0.2 ms. To illustrate:

$ ping -c 10 -q 10.0.0.8
PING 10.0.0.8 (10.0.0.8): 56 data bytes

--- 10.0.0.8 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 26.5/34.7/100.0 ms

$ traceroute -I www.webpartner.dk
traceroute to www.webpartner.dk (195.184.96.72), 30 hops max, 40 byte packets
 1  10.0.0.8 (10.0.0.8)  0.221 ms  0.186 ms  0.238 ms
 2  213.173.237.225 (213.173.237.225)  16.764 ms  14.519 ms  14.098 ms
 3  213.173.240.90 (213.173.240.90)  20.972 ms  24.657 ms  19.967 ms
 4  213.173.240.89 (213.173.240.89)  22.925 ms  34.553 ms  22.194 ms
 5  195.184.96.72 (195.184.96.72)  24.843 ms  9.660 ms  10.103 ms

213.173.237.225 is my router to the internet, it's not the world's
fastest router, but still faster than what what the above traceroute
shows. If I ping it through another firewall I get:

$ ping -c 10 -q 213.173.237.225
PING 213.173.237.225 (213.173.237.225) 56(84) bytes of data.

--- 213.173.237.225 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
rtt min/avg/max/mdev = 1.300/1.832/4.290/0.903 ms

I see the same pattern even if I cut the rules down to only permitting
ping. Does anyone have a clue as to what's happening? I'm using a
newly compiled 2.6.14 kernel, but saw the same behavior with an older
2.6.8-2 kernel.

-- 
Jacob

7. Windows ping and Linux ping command?

8. Ping from cron not having same effect as ping from console 

I'm running a RedHat Enterprise 2.1 server as a group development
platform.  We're having some network problems which are being worked
on, but right now I need a workaround.  The problem is that this
server drops off of the network a couple of times a day.  I've found
that if I just ping another server from that server it comes back on
the network, everybody can see it and everything is fine.

To keep the server on the network I set up a cron job to ping another
server every two minutes.  I can see this ping running every two
minutes with "ps -e | grep ping".  However, the machine still drops
off of the network.  When the server drops off of the network I wait
until I see the cron ping as above and then verify that it is still
off of the network.  So the cron ping doesn't get the machine back on
the network.  Then I do a ping from a console and the server comes
back on the network.

For some reason the cron ping doesn't have the same effect that a ping
from the console does.  The crontab ping entry is by the same user
that I am logged in as when I do the ping from the console.

Anyone have any suggestions?  Why does a ping from the console have a
different effect than a ping from cron.