Further to that, ifindexes of tunnels and PPP sessions can change
dynamically as the bearer connection goes up and down, even if the
interface has the same name and authenticated identity. That raises the
interesting question of whether even the interface name is stable, as on
many systems it is
Heh.
NZDT is UTC+13...
Having just moved to Australia from New Zealand... NZ has better airline
connections, especially for flying eastward across the Pacific.
As for being far away... well, you get used to that. My personal
definition of 'long flight' starts at 9 hours... 'short flight' would
On 29/03/2006, at 5:10 AM, Scott Leibrand wrote:
On 03/28/06 at 7:00am +0200, Anthony G. Atkielski
[EMAIL PROTECTED] wrote:
Agreed, but they reduce the amount of money you must pay to your ISP
each month by a factor of ten or more.
Your ISP charges you 9 times as much for IPv4 addresses
On 24/03/2006, at 9:52 AM, Yu-Shun Wang wrote:
Just another me-too data point about the Mac. It'll be
good to know why that happened. Mine is a 15 Powerbook.
I also brought a Cisco 11a NIC, and used it about 3-4
times w/out any problems.
yushun
The problem also occurs with Broadcom radios
On 20/10/2005, at 11:25 PM, Brian E Carpenter wrote:
It's very hard to get those data. We've tried looking
at how many local first-time attendees from (say) Korea
later became regular attendees but the data are hard to
state in any meaningful way and the time constants are
long (years). There
-BEGIN PGP SIGNED MESSAGE-
- --On Thursday, August 28, 2003 07:05:19 PM +0200 Iljitsch van Beijnum
[EMAIL PROTECTED] wrote:
On woensdag, aug 27, 2003, at 19:51 Europe/Amsterdam, Fred Templin wrote:
The hard part is coming up with a way to do the host/location mapping
in a way that
Or, get a NAT which *does* connection-track H.323. They do exist,
open-source and not, and work just fine.
Better, get a proper H.323 gateway (which will work behind an H.323 aware
NAT if done properly) so people can call in as well as out.
However, NAT is still brokenness. (and so is H.323)
to be hard to secure, but I guess that's what makes it
interesting.
Regards, peter
-Original Message-
From: Andrew McGregor [mailto:[EMAIL PROTECTED]]
Sent: Sunday, March 17, 2002 5:34 PM
To: Joe Touch; Vivek Gupta
Cc: [EMAIL PROTECTED]
Subject: Re: Netmeeting - NAT issue
That top-layer-calls-next-layer etc ad-nauseam model seems to have been one
of the original ideas for how to implement a stack.
Actual current implementations do all kinds of wierd stuff, but mostly pass
around accumulating collections of buffers; so the payload buffer doesn't
get copied to
