>Hi,
>This is regarding sending router advertisement on the receipt of
>router solicitation.
you keep asking (good) questions, but why? will you plan to send
some summary to somewhere, or put up onto web, to give feedback to
people? if you have no plan, i suggest you to
Hi,
This is regarding sending router advertisement on the receipt of router solicitation.
When an icmp message of type router solicitation is received in the icmp6_input(). the
function calls nd6_rs_input(). This function inturn calls nd6_cach_lladdr().
But no where in the above code rtadv rela
Radoslav Vasilev writes:
| Hello, I wonder is there a way to connect two phisical networks on ethernel level in
|a situation like this:
| I have two subnets(subnet1,2) connected through 2 aironet PCI4800 NICs(Cisco Aironet
|340 Series) working on gateway1 and 2.(FreeBSD 3.3 and 4.3 machines)
| -
Thanks for the suggestion - it does fit the bill, although I have to
getsockopt(SO_SNDBUF on a per-socket basis (I'm using the kqueue
NOTE_LOWAT, which doesn't trigger if I supply a very large number - the
exact SO_SNDBUF needs to be used). I'd honestly just prefer to have the
kernel close the so
Hello, I wonder is there a way to connect two
phisical networks on ethernel level in a situation like this:
I have two subnets(subnet1,2) connected through 2
aironet PCI4800 NICs(Cisco Aironet 340 Series) working on gateway1 and
2.(FreeBSD 3.3 and 4.3 machines)
---\
I was thinking of doing this..
but slightly differnt
renaming the node would change the interface name too.
but what you have would work as well.
"Vladimir B. Grebenschikov" wrote:
>
> Tring to use netgraph system for some pruposes
> (frame-relay/tunneling/sync) I found that it is too comp
Shaun Dwyer wrote:
>
> For configuring netgraph for bridging, i used the example script in
> /usr/share/examples/netgraph/ether.bridge .
>
> Is this to be expected when using netgraph for bridging? or is it
> because of some piece of hardware i was using, or something else?
> I dont think poces
sean-freebsd> I found the bug. The socket was IPv6, but the bind used an
sean-freebsd> IPv4 sockaddr struct. Patch attached.
sean-freebsd> - s = socket(addr.sa.sa_family, SOCK_STREAM, 0);
sean-freebsd> + s = socket(clt_addr.sa.sa_family, SOCK_STREAM, 0);
Thanks
Hi there,
Is there any serious reason to load ipfw rules after configuring network
interfaces? IMHO the right way is doing that in the reverse order.
Incidentally, IPFilter rules are loaded before starting the interfaces,
which leads to inconsistency as well.
--
Yar
To Unsubscribe: send mail t
>i have freebsd 4.2 stable release.
>i have set up a ipv6 network.
> i dun know y ping6 is not working ie ping6 with
>linklocaladdress.
> ping6 -I interfacename linklocaladdress
> works fine.
you MUST either:
1. specify the outgoing interface like "ping6 -I if0 linklocal"
Scenario: I accept a (TCP) connection, write some data, close the
connection.
Problem: close() does not perform an orderly shutdown, does not resend
unacknowledged data - responds with RST to data/acks sent to me
Non-solution: SO_LINGER, makes close into a blocking call in order to
get orderly s
i have freebsd 4.2 stable release.
i have set up a ipv6 network.
i dun know y ping6 is not working ie ping6 with
linklocaladdress.
ping6 -I interfacename linklocaladdress
works fine.
and telnet y is not working.ie
telnet linklocaladdress will it not work?
To Unsubscribe: send mail to [
12 matches
Mail list logo