I have an X-Micro wireless USB Adapter that prints "ugen0: vendor 0x0ace USB
WLAN, rev 1.10/1.01, addr 2" when i plug it in.
Is there any way i can get this device to work under FreeBSD?
Gareth
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.or
netstat -s -p ip
.
.
.
3575124 datagrams with bad address in header
Could it be this that drops "bad" packets before they enter the IPFW ?
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe,
** Reply to note from Iasen Kostov <[EMAIL PROTECTED]> Wed, 25 Feb 2004 14:37:25 +0200
>netstat -s -p ip
>..
>..
>..
>3575124 datagrams with bad address in header
>
>Could it be this that drops "bad" packets before they enter the IPFW ?
Nice, it could be, but I'm not so expert as to
On Tue, Feb 24, 2004 at 12:47:34PM +, DrumFire wrote:
> Hi,
>
> this is my configuration:
>
> rl0: flags=8843 mtu 1500
> options=8
> inet 192.168.100.1 netmask 0xff00 broadcast 192.168.100.255
> ether 00:30:84:9e:9d:26
> media: Ethernet autoselect (100baseT
Привет Iasen,
Wednesday, February 25, 2004, 3:37:25 PM, you wrote:
IK> netstat -s -p ip
IK> .
IK> .
IK> .
IK> 3575124 datagrams with bad address in header
IK> Could it be this that drops "bad" packets before they enter the IPFW ?
To me it would be also interesting to know where this
Andrew Riabtsev wrote:
Привет Iasen,
Wednesday, February 25, 2004, 3:37:25 PM, you wrote:
IK> netstat -s -p ip
IK> .
IK> .
IK> .
IK> 3575124 datagrams with bad address in header
IK> Could it be this that drops "bad" packets before they enter the IPFW ?
To me it would be also interes
On Tue, Feb 24, 2004 at 04:04:08PM +0300, Gleb Smirnoff wrote:
T> A> Ah, sorry, forgot that in my last email. The only thing is to use RTFREE().
T> A> At first I thought your reassigning of rt is a problem, but you free the
T> A> correct ro.ro_rt later.
T>
T> Thank you! I'll try everything you su
On Wed, Feb 25, 2004 at 04:47:03PM +0300, Andrew Riabtsev wrote:
A> To me it would be also interesting to know where this traffic comes
A> from. I have same on my local net:
A>
A> # tcpdump -neifxp0 src or dst 127.0.0.1
A> tcpdump: listening on fxp0
A> 16:26:23.280737 0:50:fc:ed:d4:4 0:02:55:b0:90
Gleb Smirnoff wrote:
On Wed, Feb 25, 2004 at 04:47:03PM +0300, Andrew Riabtsev wrote:
A> To me it would be also interesting to know where this traffic comes
A> from. I have same on my local net:
A>
A> # tcpdump -neifxp0 src or dst 127.0.0.1
A> tcpdump: listening on fxp0
A> 16:26:23.280737 0:50:fc
On Wed, Feb 25, 2004 at 04:19:51PM +0200, Iasen Kostov wrote:
I> >>16:26:23.287642 0:1:2:9>c:cf:e2 0:02:55:b0:90:e4 0800 60: 127.0.0.1.80 >
I> >>192.168.118.205.1046: R 0:0(0) ack 1959723009 win 0
I> >
I> >This is some kind of Win32 virus. This floods can be easily
I> >stopped by ipfw rule:
I> >
I
I have a ADSL modem (domain name: modem.lan) also acting as DNS/dhcp server
(pretty smart toy). The Windows computers in the office, after boot up and
requested an ip addresss, also registere a DNS name in the modem
(netbiosname.lan), but FreeBSD and Linux computers don't register their DNS
nam
** Reply to note from Gleb Smirnoff <[EMAIL PROTECTED]> Wed, 25 Feb 2004 17:21:34 +0300
> P.S. This is really off-topic already. We should move to -isp@ may be.
I don't really think so, why would it be?
It's concerning ipfw, netstat, traffic and the IP stack in general, I believe.
N.B. I'm obvi
Andrea Venturoli wrote:
** Reply to note from Gleb Smirnoff <[EMAIL PROTECTED]> Wed, 25 Feb 2004 17:21:34 +0300
P.S. This is really off-topic already. We should move to -isp@ may be.
I don't really think so, why would it be?
It's concerning ipfw, netstat, traffic and the IP stack in gener
Zhang Weiwu wrote:
> I thought it won't be difficult to let FreeBSD register domain name.
> after read the specific part of dhclient.conf(5), I created a
> /etc/dhclient.conf file:
> --
> #my hostname is thinkpad.lan, 'lan' is our default search domain
> send fqdn.fqdn "thinkpad.lan";
> send f
Hi,
I'm having trouble attempting to set up a lan to lan VPN between FreeBSD 4.9
and a Draytek 'Vigor2900 router'. I'm trying to use IPSec tunnelling.
My aim is to connect 192.168.32.0/24 (FreeBSD) to 192.168.1.0/24 (Draytek)
On the FreeBSD box I've gone ahead and created a tunnel (gif)
AAA.AAA.
Hi,
I've just merged version 2.27 of rhyolite.com's routed into the tree.
If you track -CURRENT and use the MD5 authentication feature, note that
it is no longer compatible with previous versions of FreeBSD; however it
is now compatible with the Sun Solaris and Cisco implementations.
I have adde
Hi,
we started importing OpenBSD's packet filter (pf) from it's port
(security/pf). The kernel parts are done, though not linked to any
automatic build. If you want to build it already, you can build from the
corresponding module directories:
sys/modules/{pf, pflog, pfsync}
Make sure
Steve Greenshaw:
>
>spdadd 192.168.32.0/24 192.168.1.0/24 ipencap -P out ipsec
>esp/tunnel/AAA.AAA.AAA.AAA-BBB.BBB.BBB.BBB/require;
>spdadd 192.168.1.0/24 192.168.32.0/24 ipencap -P in ipsec
>esp/tunnel/BBB.BBB.BBB.BBB-AAA.AAA.AAA.AAA/require;
>
Try using "any" inst
All,
maybe someone can comment on the status of this alert? There have been
some comments about fixing it on freebsd-net@ but I haven't seen a CVS
log - or I just missed it.
Thanks.
Helge
Jacques A. Vidrine:
>Does anyone have time to investigate? I will try to get more
>information from iDEFE
Hello. I think this problem really go out of my English language ability,
I'm trying my best to explain it:
Now I just built a bluetooth based LAN access server, that is to run
several serial connection over bluetooth, so you can think they are many
simple serial connection, and ppp runs over t
Greetings everyone:
I'm using a FreeBSD based notebook (P4-M2.6Ghz, 2GB RAM) on the built in 3COM 920c
(905c compatible) using the xl0 driver with the firewall enabled and set to open and
rc.conf basically has:
xl0 configured as 208.204.x.224 netmask 255.255.255.0 with the alias 192.168.0.1
On Wed, 25 Feb 2004, Aloha Guy wrote:
> Any ideas what is causing this? Is it the xl0 driver because I've
> used FreeBSD machines as ethernet routers before with a similar
> setup except there was no NAT involved and used the fxp drivers and
> it never had this problem. Thanks for your help in adv
Chris Dillon <[EMAIL PROTECTED]> wrote:
On Wed, 25 Feb 2004, Aloha Guy wrote:
> Any ideas what is causing this? Is it the xl0 driver because I've
> used FreeBSD machines as ethernet routers before with a similar
> setup except there was no NAT involved and used the fxp drivers and
> it never had
23 matches
Mail list logo
