Hi to all,
i've this scenario:
one machine in a private network
one machine with a public machine
i need to control with vnc the machine with private ip by the machine
with public ip.
This is possibile installing ultravnc on the private machine (with
freebsd) so i can start the communication
I want to diskuss the tap(4) behaviour before I create a PR:
The tap(4) interface does not go automatically in UP state (IFF_UP) when opened
by a
process. Therefore an additional command "ifconfig tapx up" is necessary, which
can
execute root only. On the other site the interface goes down aut
On Friday 09 March 2007 01:50, Jack Vogel wrote:
> On 3/8/07, Sven Petai <[EMAIL PROTECTED]> wrote:
>
> I am not sure why the 32/64 bit architecture is making a difference,
> however, you have the 573 NIC, so before doing anything else run this DOS
> app, it will patch your eeprom if needed, the pr
Frank Behrens wrote:
How does tun(4) handle this? tun(4) is also set to down, when closed. It is not set to up, when
ist is opened, but when an address is assigned by the user process. This is fine, because it
needs always an ip address. tap(4) as layer 2 tunnel device does not need an ip addres
Bruce, thanks for your answer!
Bruce M. Simpson <[EMAIL PROTECTED]> wrote on 9 Mar 2007 12:30:
> Frank Behrens wrote:
> > How does tun(4) handle this? tun(4) is also set to down, when closed. It is
> > not set to up, when
> > ist is opened, but when an address is assigned by the user process. Th
I see some problems with if_bridge(4) and want to investigate this further. But
before I make
further tests I want to be sure to have the right setup. I could not find any
hints in the
documentation including FreeBSD handbook.
I have an ethernet device xl0 and want to create a if_bridge(4) to
(previously posted on freebsd-questions, but with no resolution)
I get this error quite frequently on my pf firewall running 6.2 and
it leads to loss of internet access.
kernel: vr0: discard oversize frame (ether type 710a flags 3 len 1532
max 1514)
vr0 is connected to my ISPs cable modem, i
On Fri, 9 Mar 2007 14:10:45 +1100, Sam Wun wrote
> Hi,
>
> About half year ago, I tested a mini wireless server card with
> FreeBSD 6. The connection runs very fast if only myself using it,
> but when there are more than 1 user connected to it, the second
> user will suffer extremely slow wirel
Hi,
Last October we published a book on the KAME implementation
and on IPv6 in general. The book is titled "IPv6 Core Protocols
Implementation".
We recently published Volume-II of this two-book series.
Volume-II is titled "IPv6 Advanced Protocols Implementation".
It i
On Friday 09 March 2007 13:42, Sven Petai wrote:
> On Friday 09 March 2007 01:50, Jack Vogel wrote:
> > On 3/8/07, Sven Petai <[EMAIL PROTECTED]> wrote:
> >
> > I am not sure why the 32/64 bit architecture is making a difference,
> > however, you have the 573 NIC, so before doing anything else run
On Thu, 8 Mar 2007, Dave Baukus wrote:
What's the word on netisr_direct ?
Do people typically enable this feature ?
I always enable it, but have never measured it doing anything useful.
Under light loads, it should reduce network latency and overheads by
a microsecond or two (whatever it takes
On 3/8/07, Dave Baukus <[EMAIL PROTECTED]> wrote:
What's the word on netisr_direct ?
Do people typically enable this feature ?
It really varies with workload. For a small number of streams I get
much better throughput with it enabled for a 10GigE link.
-Kip
___
University of Cambridge
On Thu, 8 Mar 2007, Dave Baukus wrote:
What's the word on netisr_direct ? Do people typically enable this feature ?
Direct dispatch is the default configuration for the network stack in FreeBSD
7.x. Many users have reported performance improvements, especially in hig
Jason Arnaute wrote:
> --- "Bruce A. Mah" <[EMAIL PROTECTED]> wrote:
>
>> If memory serves me right, Jason Arnaute wrote:
>>> (FreeBSD 6.2-RELEASE)
>>>
>>> I have two ipv6 related lines in my /etc/rc.conf:
>>>
>>> ifconfig_em0_alias0="inet6 XXX::2/48"
>>> ipv6_defaultrouter="XXX::1"
>>>
>>> When I
14 matches
Mail list logo
