Re: bin/79228: [patch] extend arp(8) to be able to create blackhole records

2011-03-01 Thread Dan Lukes
The following reply was made to PR bin/79228; it has been noted by GNATS.

From: Dan Lukes 
To: bug-follo...@freebsd.org
Cc:  
Subject: Re: bin/79228: [patch] extend arp(8) to be able to create blackhole
 records
Date: Tue, 01 Mar 2011 21:05:22 +0100

 Not true, it doesn't work in 8.x nor in HEAD. It disappeared during 
 rewrite of network stack.
 
 But current problem is not related to this PR, so there is no reason to 
 unclose it.
 
 This PR has been submited in 2005, reviewed and committed in 2008, I 
 requested it's close in 2009. Not surprising when outdated a lot in 2011 ...
 
 Anyway, thank to anybody who spent time to solve the problem ...
 
 Dan
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: bin/79228: [patch] extend arp(8) to be able to create blackhole records

2009-12-10 Thread Dan Lukes
The following reply was made to PR bin/79228; it has been noted by GNATS.

From: Dan Lukes 
To: bug-follo...@freebsd.org
Cc:  
Subject: Re: bin/79228: [patch] extend arp(8) to be able to create blackhole
 records
Date: Thu, 10 Dec 2009 11:50:53 +0100

 Already commited and MFCed into 7-R
 
 It seems it will not be MFCed into 6-R anymore.
 
 This PR should be closed.
 
Dan
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: kern/116747: [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile 1400 wireless card

2009-11-10 Thread Dan Lukes
The following reply was made to PR kern/116747; it has been noted by GNATS.

From: Dan Lukes 
To: bug-follo...@freebsd.org, roar.petter...@freebsd.org
Cc:  
Subject: Re: kern/116747: [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile
 1400 wireless card
Date: Tue, 10 Nov 2009 13:48:33 +0100

 Just for evidence ...
 
 Same problem (unknown NDIS error C000138D then panic) but immediatelly 
 on kernel module load.
 
 OS FreeBSD 7.2-RELEASE-p3
 card:
 Atheros AR8131
 vendor:device:
chip: 1969:1063
card: 1025:0229
NDIS 5.1
windows driver version 1.0.0.26
 
Dan
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: inconsistent downloading rate

2003-06-04 Thread Dan Lukes
[EMAIL PROTECTED] napsal/wrote, On 06/02/03 21:26:
this is my first post in this ML. i'm using d-link
538TX NIC and my freebsd recognize it as a rl0. when
i'm downloading from my ftp server (other computer)
with basic configuration maximum rate 200KBps, my
freebsd box able to get only 80KBps max. the strange
thing is when i using MS XP (don't hate it ^_^), i'm
able to get 190-200KBPS, so i try to figure out why
this thing happen.
	Inconsistent full-duplex/half-duplex setting on rl0. Don't trust 'auto' 
- set it manually.

	Dan

--
Dan Lukes tel: +420 2 21914205, fax: +420 2 21914206
root of  FIONet, KolejNET,  webmaster  of www.freebsd.cz
AKA: [EMAIL PROTECTED], [EMAIL PROTECTED],[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: xe pcmcia interface broken, more debug

2002-12-29 Thread Dan Lukes
[EMAIL PROTECTED] wrote, On 12/28/02 01:11:


# ping -c 1 -s 2000 darkstar
PING darkstar.sajd.net (192.168.1.11): 56 data bytes
xe0: discard oversize frame (ether type 800 flags 3 len 1518 > max 1514)
xe0: discard oversize frame (ether type 800 flags 3 len 1518 > max 1514)

# ifconfig xe0 | grep mtu
xe0: flags=3D8843 mtu 1500



	Hm, real frame size (1518) exceeds 4 bytes above largest standard 
Ethernet packet. Are you using vlans with 'vlandev xe0', isn't it ?

				Dan



--
Dan Lukes tel: +420 2 21914205, fax: +420 2 21914206
root of  FIONet, KolejNET,  webmaster  of www.freebsd.cz
AKA: [EMAIL PROTECTED], [EMAIL PROTECTED],[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message


Re: pseudo-device ef

2002-12-29 Thread Dan Lukes
[EMAIL PROTECTED] wrote, On 12/26/02 19:11:

> I have FreeBSD 4.7-RELEASE here and pseudo-device ef doesn't seem to do
> the right thing. When compile kernel wth this option I see all the ef
> symbols in kernel:

...

> but no XXNfM interfaces come into existance after boot.
> On the other hand, if I load the corresponding module if_ef via
> loader.conf, everything works like charm.
> Am I missing something or is there a problem with the code ?


	The ef code creates preudointerfaces on init only. It doesn't catch the
interface creation after initialisation. You should load 'ef' module
after all other network-interface related module are loaded already.

Dan


--
Dan Lukes tel: +420 2 21914205, fax: +420 2 21914206
root of  FIONet, KolejNET,  webmaster  of www.freebsd.cz
AKA: [EMAIL PROTECTED], [EMAIL PROTECTED],[EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message



Re: broadcast over loopback

2002-12-05 Thread Dan Lukes
[EMAIL PROTECTED] wrote, On 12/05/02 20:41:


Is there a reason that the broadcast flag is not set on the loopback
interface? It seems like it might be useful to allow applications that
use broadcast to continue to work even when loopback is the only
interface.


	Your application shouldn't use broadcast unless it knows it run in 
broadcast capable environment or it shouldn't refuse to run when it 
cannot send a packet - as it doesn't care where it's packets are sent to.


	BTW, the broadcast are handled in mad way in TCP/IP stack already - the 
destination of 255.255.255.255 is silently rewritten to network 
broadcast and sent over first interface (if it is broadcast capable) or 
it is routed (often to default route). You can't send the non-network 
broadcast to interface of your choice (unless you use bpf).



	Dan

--
Dan Lukes tel: +420 2 21914205, fax: +420 2 21914206
root of  FIONet, KolejNET,  webmaster  of www.freebsd.cz
AKA: [EMAIL PROTECTED], [EMAIL PROTECTED],[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message


Re: if_ef doesn't work with if_fxp?

2002-11-17 Thread Dan Lukes
[EMAIL PROTECTED] wrote, On 11/14/02 15:26:


I checked with our network/netware guy, and he's told me that we're
running "0 interface with an Ethernet_II frame", so I've got fxp0f0
configured with our network number, which he's given me as 0x83a2c800 

Yust for fun - 0x83a2c800=131.162.200.0, so your try to hide real IP by 
"xx"ing it has failed.

Our network is a B-Class, with from x.x.128.x up being divided into
subnets of 8 C-classes each ... so subnet 128, 136, 144, etc ...

our netware server is on subnet 200, which is the 83a2c800 that he's given



Well - we must diferentiate what we are speaking about.

If you are trying to set up IPX network, then the informations about IP 
network topology is irelevant. You need to know the IPX network 
topology, IPX network numbers and so on. I don't know what the 
0x83A2C800 number is - it seems to be IP not IPX network number, but I'm 
not sure. You should ask your Netware server administrator.

me ... the computer I'm working on is a laptop, so will be on several
different subnets, but never on subnet 200 ... is 83a2c800 the netnum 

	The correct IPX network number must be set to the same number as the 
IPX network number assigned to network avaiable on cable you are 
connected in. Under Windows seems to be possible set the IPX network to 
0x00 requesting autodetection of the correct value.

	As you know, there must be a properly configured IPX router between you 
and server unless your IPX adress is from the same IPX NET as server's 
(it is similar law as for IP)

	Dan


--
Dan Lukes tel: +420 2 21914205, fax: +420 2 21914206
root of  FIONet, KolejNET,  webmaster  of www.freebsd.cz
AKA: [EMAIL PROTECTED], [EMAIL PROTECTED],[EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message