Re: crash with ipfw nat on mips32

On Thu, Mar 22, 2018 at 03:52:39PM +0300, Andrey V. Elsukov wrote: > On 22.03.2018 10:31, Adrian Chadd wrote: > > Erk. I'll go see if I can figure out what's going on. > > > > Thanks! This is really quite grr-y. > >>> Trap cause = 2 (TLB miss (load or instr. fetch) - kernel mode) > >>> [ thread

Re: ether <-> wlan failover still is broken

22.03.2018 20:57, Zeus Panchenko wrote: > while having no any problem with separate (lagg less) mode, when I use > ether or wlan without aggregating, I am still experiencing severe problem > with ether <-> wlan failover > > after upgrade to 11.1 I decided to give another try to the handbook

Re: ether <-> wlan failover still is broken

On 22.03.2018 16:57, Zeus Panchenko wrote: > hi, > > while having no any problem with separate (lagg less) mode, when I use > ether or wlan without aggregating, I am still experiencing severe problem > with ether <-> wlan failover > > after upgrade to 11.1 I decided to give another try to the

ether <-> wlan failover still is broken (was: is lagg (re+wlan) working on 11.0-RELEASE?)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi, while having no any problem with separate (lagg less) mode, when I use ether or wlan without aggregating, I am still experiencing severe problem with ether <-> wlan failover after upgrade to 11.1 I decided to give another try to the handbook

Re: ether <-> wlan failover still is broken

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrey V. Elsukov wrote: > > It will work, if you will change ethernet's MAC address to one, what > wlan interface have. > in my previous attempts it was working this way *only* when interface was in promiscious mode but I'll

Re: crash with ipfw nat on mips32

On 22.03.2018 10:31, Adrian Chadd wrote: > Erk. I'll go see if I can figure out what's going on. > > Thanks! This is really quite grr-y. >>> Trap cause = 2 (TLB miss (load or instr. fetch) - kernel mode) >>> [ thread pid 11 tid 100010 ] >>> Stopped at 0 >>> db> bt >>> Tracing pid 11 tid

Re: crash with ipfw nat on mips32

I dunno yet; this is a very embedded mips74k box. :) -a On 22 March 2018 at 06:00, Olivier Houchard wrote: > On Thu, Mar 22, 2018 at 03:52:39PM +0300, Andrey V. Elsukov wrote: >> On 22.03.2018 10:31, Adrian Chadd wrote: >> > Erk. I'll go see if I can figure out what's going on.

Re: ether wlan lagg works only with hint.ath.0.macaddr set (was: ether <-> wlan failover still is broken)

Hi, I keep telling people that right now it's not something I at least have time to fix up. :) -a On 22 March 2018 at 08:37, Zeus Panchenko wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > Andrey V. Elsukov wrote: >> >> It will work, if you

Re: crash with ipfw nat on mips32

On Thu, Mar 22, 2018 at 09:09:37AM -0700, Adrian Chadd wrote: > oh and xcompiled with gcc-6.x . > > I'm not very knowledgable with mips. Is it possible gcc wrongly generated an instruction that is not supported by mips74k ? I suppose not, or it wouldn't lead to a TLB miss. Olivier > > On 22

Re: crash with ipfw nat on mips32

oh and xcompiled with gcc-6.x . -a On 22 March 2018 at 09:09, Adrian Chadd wrote: > I dunno yet; this is a very embedded mips74k box. :) > > > -a > > On 22 March 2018 at 06:00, Olivier Houchard wrote: >> On Thu, Mar 22, 2018 at 03:52:39PM +0300, Andrey V.

Re: Same host or different? How can you tell "over the wire"?

In message <4db72389-d167-4152-a15f-4710c54b2...@your.org>, Kevin Day wrote: >Does the ssh-keyscan tool do what you want? I never knew about that tool until now. But yes, indeed, that may be the exact kind of magic I was looking for. Thank you.

Re: Same host or different? How can you tell "over the wire"?

On 03/22/18 09:02, Alexandre Snarskii wrote: On Wed, Mar 21, 2018 at 02:19:43PM -0700, Ronald F. Guilmette wrote: [...] P.S. It is my assumption that the kind of thing I'm looking for, if it exists at all, will be found somewhere below the application layer. I do not rule out however that

Re: Same host or different? How can you tell "over the wire"?

On Wed, Mar 21, 2018 at 02:19:43PM -0700, Ronald F. Guilmette wrote: [...] > P.S. It is my assumption that the kind of thing I'm looking for, if > it exists at all, will be found somewhere below the application layer. > I do not rule out however that there may be some way of differentiating > the

ether wlan lagg works only with hint.ath.0.macaddr set (was: ether <-> wlan failover still is broken)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrey V. Elsukov wrote: > > It will work, if you will change ethernet's MAC address to one, what > wlan interface have. > yes, for me it works *only* if the interface is in promiscious mode, just have checked BUT! what

Re: Raw Sockets: Two Questions

On 2018-Mar-21 13:50:26 -0700, "Ronald F. Guilmette" wrote: > >In message <5ab2c0b1.3020...@grosbein.net>, >Eugene Grosbein wrote: > >>It does not mean you need to stick with raw sockets API. >>libpcap can be used too, as I've shown in previous

Re: Same host or different? How can you tell "over the wire"?

> > In message <201803220250.w2m2owmf024...@pdx.rh.cn85.dnsmgr.net>, > "Rodney W. Grimes" wrote: > > >You are not going to prove the "control of the exact same Bad Actor" > >without a warrant to search and seize. > > Well, as someone else noted, if two IP

Re: Same host or different? How can you tell "over the wire"?

In message <201803220250.w2m2owmf024...@pdx.rh.cn85.dnsmgr.net>, "Rodney W. Grimes" wrote: >You are not going to prove the "control of the exact same Bad Actor" >without a warrant to search and seize. Well, as someone else noted, if two IP addresses yield

Re: Same host or different? How can you tell "over the wire"?

In message <4ce048ad-873e-795e-aae0-8d795d9bb...@kicp.uchicago.edu>, Valeri Galtsev wrote: >If A and A' do resolve beyond their SOA for clients outside of their >domain. That was vulnerable for abuse, and hardly anybody does that >these days. Am I missing

Re: Same host or different? How can you tell "over the wire"?

In message <20180322140233.ga79...@staff.retn.net>, Alexandre Snarskii wrote: >DNS: if both A and A' running open recursive DNS servers (bad idea in >modern internet, but..) it's possible to use TTL field to differentiate. >Scenario: create some DNS record with good enough

Re: ether <-> wlan failover still is broken

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eugene Grosbein wrote: > > You should try forcing lagg to use MAC of wireless card instead of fabricated > one: > ifconfig lagg0 ether $(ifconfig wlan0 | awk '/hwaddr/ {print $2}') > as I wrote in previous message, it works

Re: Same host or different? How can you tell "over the wire"?

In message <201803221856.w2miurjh027...@pdx.rh.cn85.dnsmgr.net>, "Rodney W. Grimes" wrote: >> Well, as someone else noted, if two IP addresses yield the exact same >> SSH key, that is fairly definitive. > >Wrong, as someone else pointed out that is simply a

Re: Need Netgraph Help [fixed]

Hi John, did you ever try out my version? Julian On 7/1/18 4:06 am, Julian Elischer wrote: On 7/1/18 4:02 am, John Lyon wrote: Thanks for the clarification and all the help. After Marko clarified that that edges/hooks are bidirectional, I was able to get it working WAN to LAN and LAN to WAN

crash with ipfw nat on mips32

hi, I'm updating my freebsd wifi bits in preparation for more work and ... well: ath1: using multicast key search random: harvesting attach, 8 bytes (4 bits) from ath1 .. ipfw ipfw2 initialized, divert loadable, nat loadable, default to accept, logging disabled .. ipfw_nat *** Setting

Re: crash with ipfw nat on mips32

On 22.03.2018 09:23, Adrian Chadd wrote: > Trap cause = 2 (TLB miss (load or instr. fetch) - kernel mode) > [ thread pid 11 tid 100010 ] > Stopped at 0 > db> bt > Tracing pid 11 tid 100010 td 0x80673b40 > dyn_expire_states+0x13c (?,?,?,?) ra c1d08f44 sp c1247c40 sz 144 > dyn_tick+0x238

Re: crash with ipfw nat on mips32

Erk. I'll go see if I can figure out what's going on. Thanks! This is really quite grr-y. -a On 21 March 2018 at 23:35, Andrey V. Elsukov wrote: > On 22.03.2018 09:23, Adrian Chadd wrote: >> Trap cause = 2 (TLB miss (load or instr. fetch) - kernel mode) >> [ thread pid

Re: Multicast/SSDP not working (on VLAN interface)

@sunp...@freebsd.org: as you are the (brand new?) maintainer of the miniDLNA port for FreeBSD, my hopes are with you :D tl;dr "setsockopt" should be replaced by "sourcefilter" (at least in minissdp.c's "AddMulticastMembership) On 22.03.18 01:15, Rodney W. Grimes wrote: ... Try as a very