add pipe 1 tcp from 147.28.2.129 to 147.28.2.133
add pipe 2 tcp from 147.28.2.133 to 147.28.2.129
pipe 1 config queue 50 delay 200ms
pipe 2 config queue 50 delay 200ms
is a tcp packet from 147.28.2.129 to 147.28.2.133 delayed by 200ms or
400ms, 200 for each interface?
randy
__
problem:
some devices are getting a v6 address and find the gateway, i.e. a
lionized macbook air. but a ripe atlas probe is getting an address but
not gateway.
environment and config:
the router is a soekris 5501 gateway running
FreeBSD soek0.psg.com 9.0-STABLE FreeBSD 9.0-STABLE #0: Fri Jan 2
> Well, you should look at your bandwidth-delay product and adjust the
> queue size appropriately
is there a url for that product? :) do they take paypal? :)
understand the math. want tool to do it for me. 'cause it ain't just
me, it's lab tech(s).
randy
_
> Try "ipfw pipe show" instead
thanks!
now to figure out what all that means. especially worried about the
queue length, as will be using varying delays in an experiment.
randy
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mail
>> dum0# ipfw 900 pipe 1 config queue 20 delay 10ms
> remove the '900'
> ipfw pipe 1 config queue 20 delay 10ms
thanks! but ...
sure, it's not really part of the programmitic sequence. but one can
not see it's there!
randy
dum0# ipfw show
00100 00 deny log ip from any to any ipopti
new to dummynet
FreeBSD dum0.sea.rg.net 9.0-STABLE FreeBSD 9.0-STABLE #0: Thu Apr 5 00:53:01
UTC 2012 root@dum0:/usr/obj/usr/src/sys/GENERIC amd64
dum0# ipfw show
00100 0 0 deny log ip from any to any ipoptions ssrr,lsrr,rr
00200 0 0 allow ip from any to any via lo0
00300 0
> What happens if you set hw.bge.allow_asf to 0 and use auto-negotiation
> on both sides?
it works! the switch was already auto-neg, and i forced auto-neg on the
server side.
thanks. this was not pleasant. did i remember to whine that i am in
tokyo and the server is on the beast coast of the s
>> Have you tried to set the loader-tunable hw.bge.allow_asf to 0?
>> The default for that option still is different between 8 and 9+.
> it no longer panics when booting, but the interface comes up not
> seeing carrier
an additional datum.
o with hw.bge.allow_asf untouched, i.e. default
o with
> Hrm, the problem apparently is that while when probing, the PHY
> still knows about the media it supports, it just has forgotten
> about it after the reset during attach. There was a change prior
> to 8.2 which would turn this from silently being ignored (which
> generally might or might not work
>> ok, i
>> o used device.hints to disable both bge interfaces
>> o booted successfully
>> o used serial console
>> o ifconfiged bge0 to the normal addresses
>> o and it is working
>>
>> i suspect that something sucks in bge initialization at startup.
>> insightful, i know. sorry.
>
>
ok, i
o used device.hints to disable both bge interfaces
o booted successfully
o used serial console
o ifconfiged bge0 to the normal addresses
o and it is working
i suspect that something sucks in bge initialization at startup.
insightful, i know. sorry.
randy
way cool. a /boot/device.hints entry of
hint.acpi.bge.1.disable=1
did disable bge1. but now it's bge0, and i need that interface. and
media are present!
so i tried /etc/rc.conf
ifconfig_bge0="198.180.150.1/25 media 1000baseTX"
ifconfig_bge0_ipv6="inet6 2001:418:8006::1/64"
ifco
day old i386 current
bge1: mem
0xd020-0xd020 irq 10 at device 0.0 on pci5
bge1: CHIP ID 0x4101; ASIC REV 0x04; CHIP REV 0x41; PCI-E
miibus1: on bge1
brgphy1: PHY 1 on miibus1
brgphy1: OUI 0x001018, model 0x0018, rev. 0
brgphy1: no media present
ifmedia_set: no match for 0x0/0x
>> ignore. i sorted it.
> Too late, sucked in .. diff from prior config might be bone enough?
i had forgotten to remove the nat enable from /etc/ppp/ppp.conf when i
moved to natd.
randy
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/
ignore. i sorted it.
randy
___
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"
FreeBSD gate0.psg.com 8.2-STABLE FreeBSD 8.2-STABLE #8: Sat Dec 24 13:39:45 GMT
2011 r...@gate0.psg.com:/usr/obj/usr/src/sys/GATE0 i386
i have a working natd setup and am trying to punch a hole in it for ssh
to an internal host.
.--.
netflix streaming is not allowed to japan where we live. i can tunnel
to a server in one of my racks in the states. the tokyo border is a
soekris running FreeBSD 8. it will kinda look like
.--.
| |
>> gets me no bridge. do i need a cloned interface for it?
> Yes, it should be in cloned_interfaces list.
works perfectly. thank you!!
randy
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe,
cloned_interfaces="tap0 tap1 tap2 tap3 tap4 tap5 tap6 tap7 tap8 tap9"
ifconfig_tap0=147.28.224.41/30
ifconfig_tap1=147.28.224.45/30
ifconfig_tap2=147.28.224.49/30
ifconfig_tap3=147.28.224.53/30
ifconfig_tap4=147.28.224.57/30
ifconfig_tap5=147.28.224.61/30
ifconfig_tap6=147.28.224.65/30
ifconfig_tap
> 1/ wow does that (dynamips ciscos) actually run on BSD?
yep
> 2/ "why?"
so we can have a routing research topology testbed of real cisco and
real juniper code.
> first you need to create them right?
> ifconfig tap0 create 192.168.3.1/28 up
>
> I think you do:
> in rc.conf:
> cloned_interface
i want to run a whole bunch of dynamips virtualized ciscos inside a fbsd
8.x server. i want the virtual routers to have some interfaces which
are externally visible.
so i think i do something like
ifconfig tap0 147.28.224.41/30
ifconfig tap1 147.28.224.45/30
ifconfig tap2 147.28.22
bjoern zeeb just received the itojun award. congratulations, bjoern.
and than you for all the hard work on the ipv6 stack.
randy
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail
a host sees these kinds of messages
Jun 7 00:20:41 r2 kernel: IPv4 address: "98.128.0.1" is not on the network
Jun 7 03:38:00 r2 kernel: IPv4 address: "98.128.0.2" is not on the network
Jun 7 04:32:08 r2 kernel: IPv4 address: "98.128.0.1" is not on the network
Jun 7 06:55:12 r2 kernel: IPv4 ad
> We should instead use names with exact sizes (16,32,64).
i think it should be pink
___
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"
thanks!
yep, i understood the stacks in from vr0 to the bridge. but yes,
short-cutting the diagram was a bad. thanks for the fix.
it's the bridge that worries me. took me a while to make it work
randy
___
freebsd-net@freebsd.org mailing list
http://
i have a year old 8 soekris system i am about to upgrade. it is pppoe
externally, and has a bridged natted wireless/ether internal net.
..
||
| b --wlan0|
| r| 192.168.0.0/24
ext ii
> However, I was simply reacting to the claim that it was *supported* by
> Cisco.
have you noticed a difference in the bug rate between things that are
'supported by cisco' and those that just happen to be there? :)
but you're right. i liked. our p2ps are /30s, not /31s. and we're
moving from
> No, Cisco does not *support* it. They make it available, which is a
> completely different story.
>
> We have asked Cisco repeatedly, through official channels, whether
> they *support* /31 on Ethernet links. The answer is always that it
> *may* work, use at your own peril.
i have managed O(10^
/31 on point to point ether is exceedingly common in inter-router
topologies.
you may be amused to also read draft-kohno-ipv6-prefixlen-p2p-00.txt
randy
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To un
> Using natd (or ipfw nat) has the ability to manipulate the IP address
> and ports of a packet. The fwd capability in ipfw does not modify the
> layer 3 headers, but instead short-circuits the next-hop logic. Take a
> look at the fwd description in ipfw(8).
>
> I would recommend using the ipfw bu
say i run routed and receive rip default from two routers, on the same
local ether. what is the forwarding? i presume it's not smart enough
to balance flows. i hope not alternating packets. clue, please?
>>> Unless you have RADIX_MPATH in your kernel (with a recent FreeBSD, ie:
>
>> say i run routed and receive rip default from two routers, on the same
>> local ether. what is the forwarding? i presume it's not smart enough
>> to balance flows. i hope not alternating packets. clue, please?
> Unless you have RADIX_MPATH in your kernel (with a recent FreeBSD, ie:
> 8.0) it
> What release are you running ?
>> say i run routed and receive rip default from two routers, on the same
>> local ether. what is the forwarding? i presume it's not smart enough
>> to balance flows. i hope not alternating packets. clue, please?
>>
>> fwiw, the routers each have full bgp exits
>> say i run routed and receive rip default from two routers, on the same
>> local ether. what is the forwarding? i presume it's not smart enough
>> to balance flows. i hope not alternating packets. clue, please?
> I can't speak for routed
routed is just the routing protocol used to garner the
say i run routed and receive rip default from two routers, on the same
local ether. what is the forwarding? i presume it's not smart enough
to balance flows. i hope not alternating packets. clue, please?
fwiw, the routers each have full bgp exits. vrrp would force all
traffic to one. so i am
>> From my perspective, putting it in a separate db outside the kernel
>> kind of defeats the purpose. I thought the first patches had the
>> right idea. though for me the current ability to rename an interface
>> is good enough. I mean is you can cal your interface "Sydney0" or
>> "Melbourne
>> i believe that you may relying on a behavior of a dns resolver which
>> is not specified
> While it might not be specified, it is being observed and therefore
> an issue when we want to restrict traffic specified by hostname.
i do not disagree.
randy
___
> I have "server 0.pool.ntp.org" in my NTP configuration, which still
> only gives me one NTP server in its internals ("dig 0.pool.ntp.org"
> gives me five answers, "ntpq -p" gives me one server). Having the
> "server 0.pool.ntp.org" in my configuration twice will give it two
> NTP servers in its i
On 08.12.17 03:11, Bruce Simpson wrote:
Randy Bush wrote:
...
freebsd does not allow metrics on static routes, which would be the
'normal' hack. i.e. you can not have two default routes with different
weights.
If you look in my 1 currently owned PRs:
http://www.freebsd.org/cgi/query
I have a nat'd box which obviously has an internal and external ip
address. The box has a third interface which is configured to a
DSL connection. My goal is for that interface to be activated if
the external side fails so that outbound traffic still flows. Any
of you know of a way to accomplish t
On 08.12.16 18:56, Gabe wrote:
I have a nat'd box which obviously has an internal and external ip
address. The box has a third interface which is configured to a DSL
connection. My goal is for that interface to be activated if the
external side fails so that outbound traffic still flows. Any of y
Brad wrote:
> On Friday 05 December 2008 03:43:41 Randy Bush wrote:
>> openbgp is said to be the best bsd implementation of bgp. but i see
>> that ports/openbgpd has not been updated in a while. it is at 4.0 while
>> 4.3 is the current public release.
> Actually 4
openbgp is said to be the best bsd implementation of bgp. but i see
that ports/openbgpd has not been updated in a while. it is at 4.0 while
4.3 is the current public release.
ports/quagga is at 0.99.10, while the public release is 0.99.11. so
that's a bit better. and, as i need is-is, i think
> I want to start a migration education to IPv6, setting up my internal
> network to be 100% ipv6-only. I dont want it to be dual stacked,
> because I intend to force my team to perform only IPv6 related tools
> on the internal network. However, when performing internet activity
> like, reading e-m
my fix to all this has been
/usr/ports/dns/unbound (cache only)
or
/usr/ports/dns/nsd (auth only)
and the developers/porters are constructive and friendly
randy
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listin
Ian Smith wrote:
> On Thu, 12 Jun 2008, Brooks Davis wrote:
> > On Thu, Jun 12, 2008 at 06:30:05PM -0700, Peter Losher wrote:
> > > Randy Bush wrote:
> > >> this has been a cause of great pain for a lng time.
> > >>
> > >
this has been a cause of great pain for a lng time.
http://www.psc.edu/networking/projects/hpn-ssh/
as openssh seems not to be fixing it (and i do not consider a 2mb fixed
buffer to be fixed, especially not from a 100mb link here in tokyo and
servers in the states, europe, and africa), per
> To address those privacy concerns RFC 3041 was written, and eventually
> obsoleted by RFC 4941. ftp://ftp.rfc-editor.org/in-notes/rfc4941.txt
> Our IPv6 implementation comes with the code to enable this feature,
> but by default it is turned off. My proposal is to enable it by
> default, and give
current of Apr 21 23:09 gmt. soekris 5501 with metrix minipci. this
worked in build of 31 march.
# ifconfig ath0 channel 11 ssid rgnet-aden wep wepkey thirteenletrs
weptxkey 1 mediaopt hostap up
ifconfig: unable to get channel information
# ifconfig ath0 channel 11 ssid rgnet-aden wep wepkey thi
i am putting in a newegg order for when i visit the states in two weeks.
among other goodies, i may need a pci 802.11 card to work with current
in a soekris 5501 (see minipci saga elsewhere). what is smack on
compatible and solid? thanks.
randy
___
how do i debug?
athstats
cool!
# athstats -i ath0
21 data frames received
54431data frames transmit
3tx frames with an alternate rate
104704 long on-chip tx retries
22469tx failed 'cuz too many retries
54M current transmit rate
35362tx management frames
3
just for giggles i un-hacked the mtus and ran for an hour with no
one using the wireless
soek0.psg.com:/root# netstat -i
NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll
vr01500 00:00:24:c8:b3:2819022 016015 0 0
vr11500 00:00:2
i seem to be loggin massive errors on an ath in hostap mode with
only two wireless clients.
mtu is set low as the tun0 ppoe over ntt B Flets on vr0 recommends
it. wireless on the two clients is set to mtu of 1454 too.
seeking pointers on how to debug.
randy
---
# netstat -i
NameMtu Networ
i have a dedicated ppp link that has to come up at boot. in
/etc/rc.conf, i have
# User ppp configuration.
ppp_enable=YES
ppp_mode=dedicated
ppp_nat=YES
ppp_profile=frob
during boot, i was getting
/libexec/ld-elf.so.1: Shared object "libintl.so.8" not found, required
by "su"
and ppp was not st
Ian Smith wrote:
>>> ifconfig_ath0="channel 4 ssid rgnet-aden wep wepkey 13-characters
>>> mediaopt hostap up"
>> ! thank you.
>> ^deftxkey 1
randy
___
freebsd-net@freebsd.org mailing list
htt
> ifconfig_ath0="channel 4 ssid rgnet-aden wep wepkey 13-characters
> mediaopt hostap up"
! thank you.
also needed to tell winxp that it was private security not enterprise.
randy
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.or
i know wep sucks caterpillar snot. but, for layer nine reasons, i
am trying to get it going on a soekris 5501 to a winxp machine and
am pretty confused.
first, if i run open, with wep off at both ends, no problem. if i
enable wep, i get what seems line a simplex, one-way, connection.
first, the p
>> How about routing domain or forwarding domain?
> which shortens too
fib
vfib
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sorry, neglected to include /etc/ipfw.rules
# egrep -v '^(#|$)' /etc/ipfw.rules
flush
add deny log all from any to any ipoptions ssrr,lsrr,rr
add pass tcp from me to 666.42.0.62 smtp
add deny log tcp from any to any smtp
add deny all from any to me auth
nat 42 config if vr0 log
add nat 42 ip4 from
ok, i have bridging working (kernel/userland version skew likely culprit,
thanks max),
except that ath0 does not seem to completely bridge. bms may have warned me in
saying
> although you won't get the 802.11 frames bridged.
---
the problem:
o hosts on vr1, vr2, and vr3 get dhcp addresses an
> 3) Most likely candidate: Your userland and kernel are out of sync. Try
> to rebuild ifconfig with the same headers installed as your kernel was
> built.
rebuilt all to current cvsup of current. can now bridge. on to trying
to make the ath happy with the bridge.
randy
___
> My last shot in the dark before They Who Know if_bridge get back from
> the nightclub .. Randy, just to rule ath in or out as prime suspect,
> does it come up right if you only specify the vr interfaces?
no
randy
___
freebsd-net@freebsd.org mailing li
> Ah. Well the only other thing i noticed (after posting) was that each
> of vr1 to vr3 showed as UP, but:
>> media: Ethernet autoselect (none)
>> status: no carrier
> but I don't know whether that should matter?
man page says not. and if i put ath0 first, which has
carrier/assoc
> did you start off with?
>
> # ifconfig bridge create
>
> when your ifconfig -a should then also show:
>
> bridge0: flags=8802 metric 0 mtu 1500
> (etc)
>
> though it looks like 'cloned_interfaces=bridge0' is supposed to do that.
>
> cheers, Ian
sorry, cut and paste error with screen.
the symptom
# ifconfig bridge0 192.168.0.1 addm vr1 addm vr2 addm vr3 addm ath0 up
ifconfig: BRDGADD vr1: Invalid argument
the conditions
# kldstat
Id Refs AddressSize Name
13 0xc040 39ad48 kernel
21 0xc27c8000 8000 if_bridge.ko
31 0xc27d 5000 bridgestp.
it is alleged that rh0 is processed in 6.2 (<
http://www.6journal.org/archive/0284/01/IPv6_RH_security-csw07.pdf>).
is this true. is rh0 processed in 7 and -current?
randy
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/l
> is your ruleset/config ok? can you post it?
appended, with one ip address obscured
> try to substitute the "nat 42 ip4 from any to any via vr0" rule with a
> divert rule, and config & start natd: does it config work as expected?
i hope to try this later today
randy
--
# ipfw list
00100 den
>>> # grep -n nat /etc/ipfw.rules
>>> 33:add nat 123 all from any to any
>>> 34:add nat 123 config if vr0
>> - add is not needed here.
thanks andrey
> ipfw nat crash course:
> echo "net.inet.ip.fw.one_pass=0" >> /etc/sysctl.conf
> and manually add:
> ipfw nat 123 config if $IF log
> ipfw
i386 current
kernel has
options IPFIREWALL
options IPFIREWALL_VERBOSE
options IPFIREWALL_VERBOSE_LIMIT=100
options IPDIVERT
options IPFIREWALL_NAT #thanks to paulo and andrey
options LIBALIAS
# ipfw -q /etc/ipfw.rules
Line 34: unrecognised
> options IPFIREWALL_NAT #ipfw kernel nat support
thank you. apologies for missing it.
randy
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROT
i386 current
# grep -n nat /etc/ipfw.rules
33:add nat 42 all from any to any
34:add nat 42 config if vr0 same_ports unreg_only
# ipfw -q /etc/ipfw.rules
Line 33: getsockopt(IP_FW_ADD): Invalid argument
kernel has
options IPFIREWALL
options IPFIREWALL_VERBOSE #enable logging
>> so it does not want to be an AP but it does want to bridge.
> At the bottom of if_bridge(4):
> "Only wireless interfaces in hostap mode can be bridged due to the
> 802.11 framing format, bridging a wireless client is not supported yet."
randy, rearchitecting
__
> I don't know what you're trying to do
no surprise. i rarely do. :)
> When you attach your wired nic to a bridge and and turn the bridge on
> the nic gets set in promiscuous mode. This is likely why you can
> ping the other wireless station through the wired nic. To ping the
> wireless statio
> You can only bridge a wireless card in hostap mode.
after your earlier comment, i tried that too :(
it's not that i think i have not done something stupid. i just can't
find it :)
randy
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.o
> Be sure apbridge is enabled
not running in hostap mode, not an access point
> you can use tcpdump to check traffic on each interface to isolate the issue.
the ath interface
00:28:26.699253 IP dhcp1.psg.com > hawi0.psg.com: ICMP echo request, id 56334,
seq 218, length 64
00:28:26.699295 IP ha
> device if_bridge
> or
> if_bridge_load="YES" in loader.conf is all that's needed.
if_bridge.ko is automagically loaded, no extra charge
> For testing purposes, you might want to disable the filtering
> configuration with:
> sysctl net.link.bridge.pfil_member=0
> sysctl net.link.bridge.pfil_brid
> Just to be sure...
good questions, thanks for asking
> net.inet.ip.forwarding=1
# sysctl net.inet.ip.forwarding
net.inet.ip.forwarding: 1
> net.link.ether.bridge.enable=1
> net.link.ether.bridge.config=em0,ath0
# sysctl net.link.ether.bridge.enable
sysctl: unknown oid 'net.link.ether.bridge.
Andrew Thompson wrote:
> On Wed, Sep 26, 2007 at 04:07:00PM -1000, Randy Bush wrote:
>> current i386 thinkpad t41
>>
>> ifconfig_lo0="inet 127.0.0.1/8"
>> cloned_interfaces="bridge0"
>> ifconfig_bridge0="inet 192.168.0.3/24 addm em0 addm
current i386 thinkpad t41
ifconfig_lo0="inet 127.0.0.1/8"
cloned_interfaces="bridge0"
ifconfig_bridge0="inet 192.168.0.3/24 addm em0 addm ath0 up"
ifconfig_em0="up"
ifconfig_ath0="ssid rgnet up"
defaultrouter="192.168.0.1"
with ether plugged in, i can ping it. unplug ether and no ping over
ath0.
> divert
> ipnat
> ipfw's integrated nat
>
> I believe the integrated version makes configuration simpler. I would
> choose the old classic divert with ipfw if it is for a important network
> that must work, but if I was running -current I would try the integrated
> variant beacuse it seems to be
> I believe the integrated version makes configuration simpler. I would
> choose the old classic divert with ipfw if it is for a important network
> that must work, but if I was running -current I would try the integrated
> variant beacuse it seems to be simpler to use.
and one less daemon. less
freebsd-current i386 / soekris
i used to use ipfw to divert to natd. so, when i went to configure a
new nat box nat box today, i was 82.3% there when i hit a bunch of nat
stuff in ipfw that i do not remember seeing before. it appears that
ipfw will nat all on its own without natd and divert.
wh
> I would like to see NOTHING running anything that looked too much like
> 5.x. And I can't really think the 6.x (while much better that 5) would
> be a good choice for a route processor.
juniper merely uses freebsd as a framework. all route processing, and
anything to do with routing, is extreme
>>> what size is the actual maximal sized jumbo packet we will ever see?
>> some transpac science community folk, who care more about speed trials
>> with big data sets than they do about over-stretching the ethernet crc,
>> use 9k jumbo frames.
> well that's the standard but the highest I've seen
> what size is the actual maximal sized jumbo packet we will ever see?
some transpac science community folk, who care more about speed trials
with big data sets than they do about over-stretching the ethernet crc,
use 9k jumbo frames.
randy
___
freebsd-
just did a cvsup build and portupgrade of a six month old -current
i386 system running quagga. quagga cranked to 0.99.8. i got
slammed by bgp tcpmd5 requirement.
bgpd[469]: can't set sockopt TCP_MD5SIG 0 to socket 17
bgpd[469]: can't set sockopt TCP_MD5SIG 0 to socket 18
bgpd[469]: can't set soc
any suggestions for how to tune freebsd tcp for very large bandwidth
delay product. doing daily rsync from oregon to australia over I2
and aarnet. getting mediocre transfers. hints appreciated.
___
freebsd-net@freebsd.org mailing list
http://lists.fre
> Mike Tancsa <[EMAIL PROTECTED]> suggested i try
> ifconfig fxp0 media 10baseT/UTP
> ifconfig fxp0 media autoselect
> this worked!
>
> i will next reboot with in_fxp.c reverted to pre 2006.10.06.
and this also worked. i.e. there is poison in the if_fxp.c update
of 2006.10.06
randy
___
Mike Tancsa <[EMAIL PROTECTED]> suggested i try
ifconfig fxp0 media 10baseT/UTP
ifconfig fxp0 media autoselect
this worked!
i will next reboot with in_fxp.c reverted to pre 2006.10.06.
but first i did the suggested analysis, which follows.
> (1) When it's "dead", do interrupts still fire
> FreeBSD rip.psg.com 7.0-CURRENT FreeBSD 7.0-CURRENT #3: Sat Nov 11 19:18:23
> GMT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/RIP i386
>
> and for the last four or five days, fxp0 goes dead. it shows up
> and active, but no packets move.
>
> down/up does not help. only way out has been
FreeBSD rip.psg.com 7.0-CURRENT FreeBSD 7.0-CURRENT #3: Sat Nov 11 19:18:23 GMT
2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/RIP i386
and for the last four or five days, fxp0 goes dead. it shows up
and active, but no packets move.
down/up does not help. only way out has been reboot.
sugge
i am in a hotel which gives me an address from 10/8 on the ether.
i have it plugged into em0 on a -current system.
i have another machine on wireless out the ath0 port which is
configured as 192.168.0.1
my natd.conf is
dynamic yes
unregistered_only yes
interface em0
my ipfw.rules se
>> As i also said before, i agree that when the number of interfaces
>> becomes large, managing ipfw lists can become difficult (though i
>> see no way your technique can help without the assistance of scripts
>> generating the actual lists for each interface making sure that the
>> 'common' checks
dunno if i am the randy you meant to invoke, but sctp is far
more usable and used than t/tcp. but it is not widely used
yet. it very well may be. i think it would be good to
support it, and i have zero qualms about dumping t/tcp.
randy
___
[EMAIL PRO
i was using my 6-current laptop to debug a bunch of networking
stuff. i manually switched interfaces between ath0 and em0.
i readdressed and remasked many many times. i used dhcclient.
i routed through the puppy.
and it all just worked.
this did not used to be the case; especially switching bet
> I do not insist that AS pathes in kernel are good idea. If you
> show me an other way to get AS information when constructing
> netflow exports in kernel, I'd be thankful.
do we need to rediscover why flow export places a large processor
burden on criscos, junipers, prockets, ...?
randy
__
>> You need GigE, T1/E1, E3/T3 and STM-1 these days. Everything
>> else is dead.
> From what I understand from Henning, he's going to be dumping
> E-1/T-1, E3-T3, and probably also STM-1, because you can't get
> those kinds of interfaces for regular PC-type boxes. I'm not
> sure I agree with hi
most APs have snmp
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> what is teredo?
a security-problematic hack that should not be necessary on an
opsys that has other means of running v6 in a v4 world, e.g.,
faith.
randy
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To uns
> It took about 3 years for the updates to get out there so IPv6
> was usable
i have yet to see a cisco ios image supporting ipv6 that was usable
in production environment. and i have tried hard.
but i will admit to not having seen apollo networking for over a
decade. but i probably have not be
1 - 100 of 111 matches
Mail list logo
