Re: VLAN interface management - unloading carrying driver hangs the machine

Jack Vogel wrote: On Wed, Jan 7, 2009 at 9:54 AM, Sam Leffler > wrote: Yony Yossef wrote: Yony Yossef wrote: /sbin/ifconfig vlan3653 create Problem is when I assign an IP to the vlan interface.

Re: VLAN interface management - unloading carrying driver hangs the machine

On Wed, Jan 7, 2009 at 9:54 AM, Sam Leffler wrote: > Yony Yossef wrote: > >> Yony Yossef wrote: >>> >>> /sbin/ifconfig vlan3653 create Problem is when I assign an IP to the vlan interface. In that case, unloading the driver results in hanging the host. Does it sound fami

RE: Having problems with limited broadcast

> You will need to go to the pcap layer to send limited broadcasts w/o any > IPv4 addresses configured in a BSD stack for now. If you have an IP on > the interface, you can just use IP_ONESBCAST. Yes, I can send broadcasts if my box has an IP. Since we are writing our own DHCP-like service thoug

Re: VLAN interface management - unloading carrying driver hangs the machine

Yony Yossef wrote: Yony Yossef wrote: /sbin/ifconfig vlan3653 create Problem is when I assign an IP to the vlan interface. In that case, unloading the driver results in hanging the host. Does it sound familiar to anybody? Well, surely I'd expect problems by doing so. The correct

Re: Having problems with limited broadcast

Peter Steele wrote: .. Based on the discussion in the link above, it doesn't seem like the problem was entirely resolved by the patches mentioned in this thread. Has anything been done since this discussion took place. Surely there must be a way to get limited broadcast to work under FreeBSD.

Re: Having problems with limited broadcast

Peter Steele wrote: When our boxes are initially deployed, they have no IP addresses assigned to them. Their ifconfig entry looks like this: ifconfig_lagg0="laggproto failover laggport nfe0 laggport nfe1" With this config, no IP is assigned to the lagg0 device, so the only way to access the box

Re: SCTP : problems in sending ASCONF chunks

Randall Stewart wrote: > Aman: > > You may also want to contact Vlad (copied above) who is responsible > for the lk-sctp implementation.. he may be able to direct you to > the one that will have all his latest fixes.. > > Regards To turn on support of ASCONF, you need to turn on at least 2 sysc

Re: VLAN interface management - unloading carrying driver hangs the machine

Yony Yossef wrote: /sbin/ifconfig vlan3653 create Problem is when I assign an IP to the vlan interface. In that case, unloading the driver results in hanging the host. Does it sound familiar to anybody? Well, surely I'd expect problems by doing so. The correct way is to /sbin/ifconf

RE: VLAN interface management - unloading carrying driver hangs the machine

> Yony Yossef wrote: > > /sbin/ifconfig vlan3653 create > > > > Problem is when I assign an IP to the vlan interface. > > In that case, unloading the driver results in hanging the host. > > > > Does it sound familiar to anybody? > > Well, surely I'd expect problems by doing so. > The correct wa

RE: Having problems with limited broadcast

>We ARE talking about "just a LAN" here, right? Also, these computers >are "not on the internet?" They have absolutely no connectivity? >(Unlikely). When our boxes are initially deployed, they have no IP addresses assigned to them. Their ifconfig entry looks like this: ifconfig_lagg0="laggproto

Re: +ipsec_common_input: no key association found for SA

> From: Gabe > Subject: Re: +ipsec_common_input: no key association found for SA > To: "Bjoern A. Zeeb" > Cc: freebsd-net@freebsd.org > Date: Sunday, January 4, 2009, 4:11 AM > > From: Bjoern A. Zeeb > > > Subject: Re: +ipsec_common_input: no key association > found for SA > > To: "Gabe" > > Cc

VLAN interface management - unloading carrying driver hangs the machine

Hi All, I'm having a problem on FreeBSD 6.3 and 7.0 with VLAN management. After loading my 10GigE driver I'm creating a vlan interface: /sbin/ifconfig vlan3653 create /sbin/ifconfig vlan3653 vlan 3653 vlandev mynic0 Then I'm unloading the driver and everything is fine, the driver interface re

Re: Having problems with limited broadcast

On Tue, Jan 6, 2009 at 8:45 AM, Peter Steele wrote: > We have a Python app that implements a DHCP-like protocol using limited > broadcast using address 255.255.255.255. Our code works fine on Linux > and FreeBSD but we cannot seem to get broadcast to work on FreeBSD. > We've tried both Python and

Re: kern/106438: [ipf] ipfilter: keep state does not seem to allow replies in on spar64 (and maybe others)

The following reply was made to PR kern/106438; it has been noted by GNATS. From: =?iso-8859-1?Q?=22Stefan_Kr=FCger=22?= To: bug-follo...@freebsd.org Cc: Subject: Re: kern/106438: [ipf] ipfilter: keep state does not seem to allow replies in on spar64 (and maybe others) Date: Wed, 07 Jan 2009 0