Authenticating WiFi hotspot users
Hi All, I use AuthPF a fair bit to limit acces to external ports that I dont want globally accessible. The users that utilise this I I can plan for so they have an ssh client installed on the device I am now trying to authenticate unknown users that likey will not have an SSH client. The users will just need to browse the web. They need to be initially directed to a web page of terms and conditions and once accepted given permission to browse. Is there a simple answer to this problem ? I was thinking maybe a web based ssh client that can be loaded with apache or maybe an option to do something with relayd. I have a manual workaround by just changing wpa pass phrase periodically but any ideas to automate this would be appreciated.
Re: media coverage [Was: Re: OPENBSD FUNDING SOLUTION -- COME AND PARTICIPATE]
Marcus MERIGHI [mcmer-open...@tor.at] wrote: > > "OpenBSD ist in finanziellen Noeten" => "OpenBSD is in financial > trouble": > http://www.heise.de/open/meldung/OpenBSD-ist-in-finanziellen-Noeten-2088205.html > > "OpenBSD ist gerettet" => "OpenBSD is saved" > http://www.heise.de/open/meldung/Unix-Derivat-OpenBSD-ist-gerettet-2090017.html > This doesn't mean that OpenBSD is no longer in need of monthly recurring funding, quite the opposite! Use the Paypal link on the foundation web page! I'm surprised that more businesses can't afford a relatively meager $100/mo recurring funding. Yearly funding from the likes of Google and MPEx are hardly guarantees!! They are saving graces that make up for the shortfall from everyone else!!! If people really want to see OpenBSD be successful, you need to put your money in the game. The ISP/NSP types who are generally bigger users should ALL be participating in some kind of monthly recurring funding. There is now a lot of development effort geared towards improving performance to fit YOUR needs, why can't YOU help to ensure that the development environment continues on? Chris
Re: Areca HW-Raid Support ARC-1224
Jan Lambertz [jd.arb...@googlemail.com] wrote: > Hi, > > i'm currently looking for a openbsd compatible hw-raid solution. i ended up > with areca. openbsd lists a number of supported devices. sadly nothing that > can be found on the areca website. relevant openbsd supported products seem > to be eol. > the ARC-1224-8I ist quite intresting for my purpose, but not listed as > supported by openbsd, but on the areca website there is sourcecode for a > driver... > http://www.areca.com.tw/support/s_openbsd/openbsd.htm > Anyone tried that yet ? > have things changed with license or something ? why do i need this external > driver ? > any other good (and supported) hw-raid pcie card out there ? This Areca driver is now part of the -current (5.5-beta) tree.
Re: Trouble with Huawei E5372 (was e3276)
Hello all, I am hijacking this thread because I also have a Huawei LTE device that produces errors when attaching as urndis(4) with OpenBSD5.4-stable. The device is a mobile hotspot Huawei E5372 (http://consumer.huawei.com/en/mobile-broadband/mobile-wifi/features/e5372-en.htm) * dmesg : umsm0 at uhub0 port 2 configuration 1 interface 0 "HUAWEI Technology HUAWEI Mobile" rev 2.00/1.02 addr 2 umsm1 at uhub0 port 2 configuration 1 interface 1 "HUAWEI Technologies HUAWEI Mobile E353 Initial" rev 2.00/1.02 addr 2 umsm0 detached umsm1 detached urndis0 at uhub0 port 2 configuration 1 interface 0 "HUAWEI Technology HUAWEI Mobile" rev 2.00/1.02 addr 2 urndis0: using Vendorurndis0: ctrl message error: wrong size 4026510011 > 1024 urndis0: unable to get init response urndis0: ctrl message error: wrong size 4026510011 > 1024 urndis0: unable to get query response : unable to get hardware address urndis1 at uhub0 port 2 configuration 1 interface 2 "HUAWEI Technology HUAWEI Mobile" rev 2.00/1.02 addr 2 urndis1: using Vendorurndis1: ctrl message error: wrong size 4026510011 > 1024 urndis1: unable to get init response urndis1: ctrl message error: wrong size 4026510011 > 1024 urndis1: unable to get query response : unable to get hardware address umass0 at uhub0 port 2 configuration 1 interface 4 "HUAWEI Technology HUAWEI Mobile" rev 2.00/1.02 addr 2 umass0: using SCSI over Bulk-Only scsibus3 at umass0: 2 targets, initiator 0 sd0 at scsibus3 targ 1 lun 0: SCSI2 0/direct removable urndis2 at uhub0 port 2 configuration 1 interface 5 "HUAWEI Technology HUAWEI Mobile" rev 2.00/1.02 addr 2 urndis2: no data interface * usbdev -v Controller /dev/usb0: addr 1: high speed, self powered, config 1, EHCI root hub(0x), Intel(0x8086), rev 1.00 port 1 powered port 2 addr 2: high speed, power 500 mA, config 1, HUAWEI Mobile(0x1c1e), HUAWEI Technology(0x12d1), rev 1.02 port 3 powered port 4 powered port 5 powered port 6 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x8086), rev 1.00 port 1 powered port 2 powered Controller /dev/usb2: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x8086), rev 1.00 port 1 powered port 2 powered Controller /dev/usb3: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x8086), rev 1.00 port 1 powered port 2 powered And after adding USB product ID (0x1c1e) to usbdevs, usbdevs.h, usbdevs_data.h and umsm.c (as DEV_UMASS5), here is what I get : * dmesg : umsm0 at uhub0 port 1 configuration 1 interface 0 "HUAWEI Technology HUAWEI Mobile" rev 2.00/1.02 addr 2 umsm1 at uhub0 port 1 configuration 1 interface 1 "HUAWEI Technologies HUAWEI Mobile E353 Initial" rev 2.00/1.02 addr 2 umsm0 detached umsm1 detached umsm0 at uhub0 port 1 configuration 1 interface 0 "HUAWEI Technology HUAWEI Mobile" rev 2.00/1.02 addr 2 ucom0 at umsm0 umsm1 at uhub0 port 1 configuration 1 interface 1 "HUAWEI Technology HUAWEI Mobile" rev 2.00/1.02 addr 2 umsm2 at uhub0 port 1 configuration 1 interface 2 "HUAWEI Technology HUAWEI Mobile" rev 2.00/1.02 addr 2 ucom1 at umsm2 umsm3 at uhub0 port 1 configuration 1 interface 3 "HUAWEI Technology HUAWEI Mobile" rev 2.00/1.02 addr 2 umsm3: missing endpoint umsm4 at uhub0 port 1 configuration 1 interface 4 "HUAWEI Technology HUAWEI Mobile" rev 2.00/1.02 addr 2 umsm5 at uhub0 port 1 configuration 1 interface 5 "HUAWEI Technology HUAWEI Mobile" rev 2.00/1.02 addr 2 ucom2 at umsm5 I can see that Linux have a product ID of 0x1506. So I change 0x1c1e with E5372_INIT and add 0x1506, still the same : * dmesg : umsm0 at uhub0 port 2 configuration 1 interface 0 "HUAWEI Technology HUAWEI Mobile" rev 2.00/1.02 addr 2 umsm1 at uhub0 port 2 configuration 1 interface 1 "HUAWEI Technologies HUAWEI Mobile E353 Initial" rev 2.00/1.02 addr 2 umsm0 detached umsm1 detached umsm0 at uhub0 port 2 configuration 1 interface 0 "HUAWEI Technology HUAWEI Mobile" rev 2.00/1.02 addr 2 ucom0 at umsm0 umsm1 at uhub0 port 2 configuration 1 interface 1 "HUAWEI Technology HUAWEI Mobile" rev 2.00/1.02 addr 2 umsm2 at uhub0 port 2 configuration 1 interface 2 "HUAWEI Technology HUAWEI Mobile" rev 2.00/1.02 addr 2 ucom1 at umsm2 umsm3 at uhub0 port 2 configuration 1 interface 3 "HUAWEI Technology HUAWEI Mobile" rev 2.00/1.02 addr 2 umsm3: missing endpoint umsm4 at uhub0 port 2 configuration 1 interface 4 "HUAWEI Technology HUAWEI Mobile" rev 2.00/1.02 addr 2 umsm5 at uhub0 port 2 configuration 1 interface 5 "HUAWEI Technology HUAWEI Mobile" rev 2.00/1.02 addr 2 ucom2 at umsm5 Does anyone have any idea ? Making the beast detect as urndis(4) would be a blast ! Thank you in advance, Denis
Re: Trouble with Huawei e3276
Sorry, I now check /dev/cuaU* with cu and got Input/Output error on all
On Fri, Jan 24, 2014 at 10:03 PM, patrick keshishian
wrote:
> On 1/24/14, ÐиÑилл Ðаплин wrote:
> > After update firmware on the modem I made some changes to the your patch
> > (change id), it writes in dmesg:
> > umsm0 at uhub2 port 5 configuration 1 interface 0 "HUAWEI Technology
> HUAWEI
> > Mobile" rev 2.00/1.02 addr 3
> > umsm0 detached
> > umsm0 at uhub2 port 5 configuration 1 interface 0 "HUAWEI Technology
> HUAWEI
> > Mobile" rev 2.00/1.02 addr 3
> > ucom0 at umsm0
> > umsm1 at uhub2 port 5 configuration 1 interface 1 "HUAWEI Technology
> HUAWEI
> > Mobile" rev 2.00/1.02 addr 3
> > umsm2 at uhub2 port 5 configuration 1 interface 2 "HUAWEI Technology
> HUAWEI
> > Mobile" rev 2.00/1.02 addr 3
> > ucom1 at umsm2
> > umsm3 at uhub2 port 5 configuration 1 interface 3 "HUAWEI Technology
> HUAWEI
> > Mobile" rev 2.00/1.02 addr 3
> > umsm3: missing endpoint
> > umsm4 at uhub2 port 5 configuration 1 interface 4 "HUAWEI Technologies
> > HUAWEI Mobile E3276" rev 2.00/1.02 addr 3
> > umsm5 at uhub2 port 5 configuration 1 interface 5 "HUAWEI Technologies
> > HUAWEI Mobile E3276" rev 2.00/1.02 addr 3
> > ucom2 at umsm5
> >
> > but that devices no appears in /dev
>
> which devices exactly were you expecting to "appear"
> in /dev?
>
> --patrick
>
>
> >
> >
> > On Fri, Jan 24, 2014 at 5:32 PM, ÐиÑилл Ðаплин
> > wrote:
> >
> >> but it succesfully connects to it with program "my huawei terminal"
> under
> >> windows.
> >> anyway, thanks!
> >>
> >>
> >> On Fri, Jan 24, 2014 at 5:03 PM, David Coppa wrote:
> >>
> >>> On Fri, Jan 24, 2014 at 1:52 PM, ÐиÑилл Ðаплин
> >
> >>> wrote:
> >>> > sorry for delay!
> >>> > after this patch, after attach in dmesg:
> >>> > umsm0 at uhub2 port 5 configuration 1 interface 0 "Technology Mobile"
> >>> rev
> >>> > 2.00/1.02 addr 3
> >>> > umsm0 detached
> >>> > urndis0 at uhub2 port 5 configuration 1 interface 0 "Technology
> >>> > Mobile"
> >>> rev
> >>> > 2.00/1.02 addr 3
> >>> > urndis0: using Vendorurndis0: ctrl message error: wrong size
> >>> > 3735928559
> >>> >
> >>> > 1024
> >>> > urndis0: unable to get query response
> >>> > : unable to get hardware address
> >>> > urndis1 at uhub2 port 5 configuration 1 interface 2 "Technology
> >>> > Mobile"
> >>> rev
> >>> > 2.00/1.02 addr 3
> >>> > urndis1: using Vendorurndis1: ctrl message error: wrong size
> >>> > 3736059565
> >>> >
> >>> > 1024
> >>> > urndis1: unable to get query response
> >>> > : unable to get hardware address
> >>> > umass0 at uhub2 port 5 configuration 1 interface 4 "Technology
> Mobile"
> >>> rev
> >>> > 2.00/1.02 addr 3
> >>> > umass0: using SCSI over Bulk-Only
> >>> > scsibus4 at umass0: 2 targets, initiator 0
> >>> > sd7 at scsibus4 targ 1 lun 0: <, TF CARD Storage, 2.31> SCSI2
> 0/direct
> >>> > removable
> >>> > urndis2 at uhub2 port 5 configuration 1 interface 5 "Technology
> >>> > Mobile"
> >>> rev
> >>> > 2.00/1.02 addr 3
> >>> > urndis2: no data interface
> >>>
> >>>
> >>> Oh, so this seems to be a LTE device!
> >>> This particular modem has no modem interface, only NDIS.
> >>> I know nothing about these devices, I'm sorry.
> >>>
> >>> Ciao,
> >>> David
> >>>
> >>> > On Thu, Jan 23, 2014 at 1:36 PM, David Coppa
> >>> wrote:
> >>> >
> >>> >>
> >>> >> > From: night...@gmail.com
> >>> >> > Date: Thu, Jan 23, 2014 at 10:01 AM
> >>> >> > Subject: Re: Trouble with Huawei e3276
> >>> >> > To: misc
> >>> >>
> >>> >> ...
> >>> >>
> >>> >> > port 6 addr 3: high speed, power 500 mA, config 1,
> Mobile(0x155b),
> >>> >> > Technology(0x12d1), rev 1.02
> >>> >> >umass1
> >>> >>
> >>> >> ...
> >>> >>
> >>> >> Please try the attached diff:
> >>> >>
> >>> >> $ cd /usr/src/sys/dev/usb && patch -NE -i /path/to/e3276.diff
> >>> >>
> >>> >> And rebuild your kernel.
> >>> >>
> >>> >> Ciao,
> >>> >> David
> >>> >>
> >>> >> Index: umsm.c
> >>> >> ===
> >>> >> RCS file: /cvs/src/sys/dev/usb/umsm.c,v
> >>> >> retrieving revision 1.96
> >>> >> diff -u -p -u -p -r1.96 umsm.c
> >>> >> --- umsm.c 13 Dec 2013 17:43:07 - 1.96
> >>> >> +++ umsm.c 23 Jan 2014 09:27:57 -
> >>> >> @@ -138,6 +138,7 @@ static const struct umsm_type umsm_devs[
> >>> >> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E1820 },
> >>> DEV_UMASS5},
> >>> >> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E220 },
> >>> >> DEV_HUAWEI},
> >>> >> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E303 },
> >>> >> DEV_UMASS5},
> >>> >> + {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E3276 },
> >>> DEV_UMASS5},
> >>> >> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E353_INIT },
> >>> >> DEV_UMASS5},
> >>> >> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E510 },
> >>> >> DEV_HUAWEI},
> >>> >> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E618 },
> >>> >> DEV_HUAWEI},
> >>> >> Index: usbdevs
> >>> >> ===
Re: Trouble with Huawei e3276
On 1/24/14, Кирилл Каплин wrote:
> After update firmware on the modem I made some changes to the your patch
> (change id), it writes in dmesg:
> umsm0 at uhub2 port 5 configuration 1 interface 0 "HUAWEI Technology HUAWEI
> Mobile" rev 2.00/1.02 addr 3
> umsm0 detached
> umsm0 at uhub2 port 5 configuration 1 interface 0 "HUAWEI Technology HUAWEI
> Mobile" rev 2.00/1.02 addr 3
> ucom0 at umsm0
> umsm1 at uhub2 port 5 configuration 1 interface 1 "HUAWEI Technology HUAWEI
> Mobile" rev 2.00/1.02 addr 3
> umsm2 at uhub2 port 5 configuration 1 interface 2 "HUAWEI Technology HUAWEI
> Mobile" rev 2.00/1.02 addr 3
> ucom1 at umsm2
> umsm3 at uhub2 port 5 configuration 1 interface 3 "HUAWEI Technology HUAWEI
> Mobile" rev 2.00/1.02 addr 3
> umsm3: missing endpoint
> umsm4 at uhub2 port 5 configuration 1 interface 4 "HUAWEI Technologies
> HUAWEI Mobile E3276" rev 2.00/1.02 addr 3
> umsm5 at uhub2 port 5 configuration 1 interface 5 "HUAWEI Technologies
> HUAWEI Mobile E3276" rev 2.00/1.02 addr 3
> ucom2 at umsm5
>
> but that devices no appears in /dev
which devices exactly were you expecting to "appear"
in /dev?
--patrick
>
>
> On Fri, Jan 24, 2014 at 5:32 PM, Кирилл Каплин
> wrote:
>
>> but it succesfully connects to it with program "my huawei terminal" under
>> windows.
>> anyway, thanks!
>>
>>
>> On Fri, Jan 24, 2014 at 5:03 PM, David Coppa wrote:
>>
>>> On Fri, Jan 24, 2014 at 1:52 PM, Кирилл Каплин
>
>>> wrote:
>>> > sorry for delay!
>>> > after this patch, after attach in dmesg:
>>> > umsm0 at uhub2 port 5 configuration 1 interface 0 "Technology Mobile"
>>> rev
>>> > 2.00/1.02 addr 3
>>> > umsm0 detached
>>> > urndis0 at uhub2 port 5 configuration 1 interface 0 "Technology
>>> > Mobile"
>>> rev
>>> > 2.00/1.02 addr 3
>>> > urndis0: using Vendorurndis0: ctrl message error: wrong size
>>> > 3735928559
>>> >
>>> > 1024
>>> > urndis0: unable to get query response
>>> > : unable to get hardware address
>>> > urndis1 at uhub2 port 5 configuration 1 interface 2 "Technology
>>> > Mobile"
>>> rev
>>> > 2.00/1.02 addr 3
>>> > urndis1: using Vendorurndis1: ctrl message error: wrong size
>>> > 3736059565
>>> >
>>> > 1024
>>> > urndis1: unable to get query response
>>> > : unable to get hardware address
>>> > umass0 at uhub2 port 5 configuration 1 interface 4 "Technology Mobile"
>>> rev
>>> > 2.00/1.02 addr 3
>>> > umass0: using SCSI over Bulk-Only
>>> > scsibus4 at umass0: 2 targets, initiator 0
>>> > sd7 at scsibus4 targ 1 lun 0: <, TF CARD Storage, 2.31> SCSI2 0/direct
>>> > removable
>>> > urndis2 at uhub2 port 5 configuration 1 interface 5 "Technology
>>> > Mobile"
>>> rev
>>> > 2.00/1.02 addr 3
>>> > urndis2: no data interface
>>>
>>>
>>> Oh, so this seems to be a LTE device!
>>> This particular modem has no modem interface, only NDIS.
>>> I know nothing about these devices, I'm sorry.
>>>
>>> Ciao,
>>> David
>>>
>>> > On Thu, Jan 23, 2014 at 1:36 PM, David Coppa
>>> wrote:
>>> >
>>> >>
>>> >> > From: night...@gmail.com
>>> >> > Date: Thu, Jan 23, 2014 at 10:01 AM
>>> >> > Subject: Re: Trouble with Huawei e3276
>>> >> > To: misc
>>> >>
>>> >> ...
>>> >>
>>> >> > port 6 addr 3: high speed, power 500 mA, config 1, Mobile(0x155b),
>>> >> > Technology(0x12d1), rev 1.02
>>> >> >umass1
>>> >>
>>> >> ...
>>> >>
>>> >> Please try the attached diff:
>>> >>
>>> >> $ cd /usr/src/sys/dev/usb && patch -NE -i /path/to/e3276.diff
>>> >>
>>> >> And rebuild your kernel.
>>> >>
>>> >> Ciao,
>>> >> David
>>> >>
>>> >> Index: umsm.c
>>> >> ===
>>> >> RCS file: /cvs/src/sys/dev/usb/umsm.c,v
>>> >> retrieving revision 1.96
>>> >> diff -u -p -u -p -r1.96 umsm.c
>>> >> --- umsm.c 13 Dec 2013 17:43:07 - 1.96
>>> >> +++ umsm.c 23 Jan 2014 09:27:57 -
>>> >> @@ -138,6 +138,7 @@ static const struct umsm_type umsm_devs[
>>> >> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E1820 },
>>> DEV_UMASS5},
>>> >> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E220 },
>>> >> DEV_HUAWEI},
>>> >> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E303 },
>>> >> DEV_UMASS5},
>>> >> + {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E3276 },
>>> DEV_UMASS5},
>>> >> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E353_INIT },
>>> >> DEV_UMASS5},
>>> >> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E510 },
>>> >> DEV_HUAWEI},
>>> >> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E618 },
>>> >> DEV_HUAWEI},
>>> >> Index: usbdevs
>>> >> ===
>>> >> RCS file: /cvs/src/sys/dev/usb/usbdevs,v
>>> >> retrieving revision 1.622
>>> >> diff -u -p -u -p -r1.622 usbdevs
>>> >> --- usbdevs 22 Jan 2014 01:25:41 - 1.622
>>> >> +++ usbdevs 23 Jan 2014 09:28:02 -
>>> >> @@ -2153,6 +2153,7 @@ product HUAWEI K4510 0x14c5
>>> >> HUAWEI
>>> Mob
>>> >> product HUAWEI E353_INIT 0x14fe HUAWEI Mobile E353 Initial
>>> >> product HUAWEI E392_INIT 0x1505 HUAWE
Re: Trouble with Huawei e3276
After update firmware on the modem I made some changes to the your patch
(change id), it writes in dmesg:
umsm0 at uhub2 port 5 configuration 1 interface 0 "HUAWEI Technology HUAWEI
Mobile" rev 2.00/1.02 addr 3
umsm0 detached
umsm0 at uhub2 port 5 configuration 1 interface 0 "HUAWEI Technology HUAWEI
Mobile" rev 2.00/1.02 addr 3
ucom0 at umsm0
umsm1 at uhub2 port 5 configuration 1 interface 1 "HUAWEI Technology HUAWEI
Mobile" rev 2.00/1.02 addr 3
umsm2 at uhub2 port 5 configuration 1 interface 2 "HUAWEI Technology HUAWEI
Mobile" rev 2.00/1.02 addr 3
ucom1 at umsm2
umsm3 at uhub2 port 5 configuration 1 interface 3 "HUAWEI Technology HUAWEI
Mobile" rev 2.00/1.02 addr 3
umsm3: missing endpoint
umsm4 at uhub2 port 5 configuration 1 interface 4 "HUAWEI Technologies
HUAWEI Mobile E3276" rev 2.00/1.02 addr 3
umsm5 at uhub2 port 5 configuration 1 interface 5 "HUAWEI Technologies
HUAWEI Mobile E3276" rev 2.00/1.02 addr 3
ucom2 at umsm5
but that devices no appears in /dev
On Fri, Jan 24, 2014 at 5:32 PM, ÐиÑилл Ðаплин
wrote:
> but it succesfully connects to it with program "my huawei terminal" under
> windows.
> anyway, thanks!
>
>
> On Fri, Jan 24, 2014 at 5:03 PM, David Coppa wrote:
>
>> On Fri, Jan 24, 2014 at 1:52 PM, ÐиÑилл Ðаплин
>> wrote:
>> > sorry for delay!
>> > after this patch, after attach in dmesg:
>> > umsm0 at uhub2 port 5 configuration 1 interface 0 "Technology Mobile"
>> rev
>> > 2.00/1.02 addr 3
>> > umsm0 detached
>> > urndis0 at uhub2 port 5 configuration 1 interface 0 "Technology Mobile"
>> rev
>> > 2.00/1.02 addr 3
>> > urndis0: using Vendorurndis0: ctrl message error: wrong size 3735928559
>> >
>> > 1024
>> > urndis0: unable to get query response
>> > : unable to get hardware address
>> > urndis1 at uhub2 port 5 configuration 1 interface 2 "Technology Mobile"
>> rev
>> > 2.00/1.02 addr 3
>> > urndis1: using Vendorurndis1: ctrl message error: wrong size 3736059565
>> >
>> > 1024
>> > urndis1: unable to get query response
>> > : unable to get hardware address
>> > umass0 at uhub2 port 5 configuration 1 interface 4 "Technology Mobile"
>> rev
>> > 2.00/1.02 addr 3
>> > umass0: using SCSI over Bulk-Only
>> > scsibus4 at umass0: 2 targets, initiator 0
>> > sd7 at scsibus4 targ 1 lun 0: <, TF CARD Storage, 2.31> SCSI2 0/direct
>> > removable
>> > urndis2 at uhub2 port 5 configuration 1 interface 5 "Technology Mobile"
>> rev
>> > 2.00/1.02 addr 3
>> > urndis2: no data interface
>>
>>
>> Oh, so this seems to be a LTE device!
>> This particular modem has no modem interface, only NDIS.
>> I know nothing about these devices, I'm sorry.
>>
>> Ciao,
>> David
>>
>> > On Thu, Jan 23, 2014 at 1:36 PM, David Coppa
>> wrote:
>> >
>> >>
>> >> > From: night...@gmail.com
>> >> > Date: Thu, Jan 23, 2014 at 10:01 AM
>> >> > Subject: Re: Trouble with Huawei e3276
>> >> > To: misc
>> >>
>> >> ...
>> >>
>> >> > port 6 addr 3: high speed, power 500 mA, config 1, Mobile(0x155b),
>> >> > Technology(0x12d1), rev 1.02
>> >> >umass1
>> >>
>> >> ...
>> >>
>> >> Please try the attached diff:
>> >>
>> >> $ cd /usr/src/sys/dev/usb && patch -NE -i /path/to/e3276.diff
>> >>
>> >> And rebuild your kernel.
>> >>
>> >> Ciao,
>> >> David
>> >>
>> >> Index: umsm.c
>> >> ===
>> >> RCS file: /cvs/src/sys/dev/usb/umsm.c,v
>> >> retrieving revision 1.96
>> >> diff -u -p -u -p -r1.96 umsm.c
>> >> --- umsm.c 13 Dec 2013 17:43:07 - 1.96
>> >> +++ umsm.c 23 Jan 2014 09:27:57 -
>> >> @@ -138,6 +138,7 @@ static const struct umsm_type umsm_devs[
>> >> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E1820 },
>> DEV_UMASS5},
>> >> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E220 }, DEV_HUAWEI},
>> >> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E303 }, DEV_UMASS5},
>> >> + {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E3276 },
>> DEV_UMASS5},
>> >> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E353_INIT },
>> >> DEV_UMASS5},
>> >> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E510 }, DEV_HUAWEI},
>> >> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E618 }, DEV_HUAWEI},
>> >> Index: usbdevs
>> >> ===
>> >> RCS file: /cvs/src/sys/dev/usb/usbdevs,v
>> >> retrieving revision 1.622
>> >> diff -u -p -u -p -r1.622 usbdevs
>> >> --- usbdevs 22 Jan 2014 01:25:41 - 1.622
>> >> +++ usbdevs 23 Jan 2014 09:28:02 -
>> >> @@ -2153,6 +2153,7 @@ product HUAWEI K4510 0x14c5 HUAWEI
>> Mob
>> >> product HUAWEI E353_INIT 0x14fe HUAWEI Mobile E353 Initial
>> >> product HUAWEI E392_INIT 0x1505 HUAWEI Mobile E392 Initial
>> >> product HUAWEI K3765_INIT 0x1520 HUAWEI Mobile K3765 Initial
>> >> +product HUAWEI E3276 0x155b HUAWEI Mobile E3276
>> >> product HUAWEI E173S 0x1c05 HUAWEI Mobile E173s
>> >> product HUAWEI E173S_INIT 0x1c0b HUAWEI Mobile E173s Initial
>> >> p
Re: Cannot SSH to OpenBSD from machines on network
Thing are working at the moment. It turned out to be some weirdness with my wireless router. All of my machines could see the router and could get to the internet… but some of the machines were not able to see one another. I restarted the router and all seems to be working. Not sure if it was due to my clients all running different 802.11 speeds of b/g/n. I am currently using a OLD USB wireless NIC for my OpenBSD machine. Can anyone recommend a good wireless, mini-PCI NIC that is compatible with OpenBSD? Has to be mini-PCI. I am running on a Shuttle XPC machine, and it only has a mini-PCI slot. Or, I could use another (albeit newer) USB NIC. Thanks, Dan. On Jan 24, 2014, at 10:18 AM, Peter N. M. Hansteen wrote: > Dan Daley writes: > >> I am new to OpenBSD and just installed 5.4 on an AMD 64 machine. >> Still running generic kernel. > > Unless you have very specific needs that are somehow not met by > GENERIC, the general advice is to not bother compiling your own. > >> sshd is running and I can ssh into the local machine using ssh >> 192.168.1.4 >> >> However, if I attempt to ssh into the box from another machine on >> the network, I get "Operation timed out" > > I'd try the obvious things first, like checking that the boxes on the > local net agree on the netmask, check that they can ping each other, > check ifconfig output to see that you actually have a link (you want > "status: active" in the output for the relevant interface) and so on. > >> I tried disabling pf by adding PF=NO to rc.conf.local, to make sure >> that that wasn't the culprit, but that didn't help. > > Editing the file was followed by "sudo pfctl -d" or a reboot to make > extra sure? The default pf.conf allows ssh in anyway, so unless you > changed it, that would normally not be the problem. > >> I also attempted to telnet to port 22 to see if I received the SSH >> header response but that timed out with no response. >> >> Also tried with a hosts.allow with ALL: 192. >> >> Any other suggestions to assist troubleshooting this? I haven't >> seen any messages output to any of the logs when attempting to ssh >> into the machine. > > ssh running but producing no messages anywhere means that it's not > seeing any traffic. to me this sounds like a basic connectivity issue > or a banal misconfiguration, but ICBW. > > - Peter > -- > Peter N. M. Hansteen, member of the first RFC 1149 implementation team > http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ > "Remember to set the evil bit on all malicious network traffic" > delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: Cannot SSH to OpenBSD from machines on network
Hi Dan, PF=NO won't disable pf unless you reboot, FYI. Run # pfctl -d to disable it immediately. If you want to keep pf running, you can run tcpdump while attempting to connect with a client to see if pf is blocking SSH: # tcpdump -nettti pflog0 port 22 That will show you all activity on port 22 and tell if you if it is passed or blocked by pf. Some other troubleshooting tips: Run # grep sshd /var/log/authlog and see what it says about connection attempts. Awhile back another user had a similar issue, and the result, I believe, was a bad MTU setting on the client. Do your clients have a custom ssh_config? Can you try another client? -- Jeff Goettsch Agricultural and Resource Economics http://agecon.ucdavis.edu/ On 1/24/14 7:50 AM, Dan Daley wrote: I am new to OpenBSD and just installed 5.4 on an AMD 64 machine. Still running generic kernel. sshd is running and I can ssh into the local machine using ssh 192.168.1.4 However, if I attempt to ssh into the box from another machine on the network, I get "Operation timed out" I tried disabling pf by adding PF=NO to rc.conf.local, to make sure that that wasn't the culprit, but that didn't help. I also attempted to telnet to port 22 to see if I received the SSH header response… but that timed out with no response. Also tried with a hosts.allow with ALL: 192. Any other suggestions to assist troubleshooting this? I haven't seen any messages output to any of the logs when attempting to ssh into the machine. Dan.
Re: Cannot SSH to OpenBSD from machines on network
Dan Daley writes: > I am new to OpenBSD and just installed 5.4 on an AMD 64 machine. > Still running generic kernel. Unless you have very specific needs that are somehow not met by GENERIC, the general advice is to not bother compiling your own. > sshd is running and I can ssh into the local machine using ssh > 192.168.1.4 > > However, if I attempt to ssh into the box from another machine on > the network, I get "Operation timed out" I'd try the obvious things first, like checking that the boxes on the local net agree on the netmask, check that they can ping each other, check ifconfig output to see that you actually have a link (you want "status: active" in the output for the relevant interface) and so on. > I tried disabling pf by adding PF=NO to rc.conf.local, to make sure > that that wasn't the culprit, but that didn't help. Editing the file was followed by "sudo pfctl -d" or a reboot to make extra sure? The default pf.conf allows ssh in anyway, so unless you changed it, that would normally not be the problem. > I also attempted to telnet to port 22 to see if I received the SSH > header response but that timed out with no response. > > Also tried with a hosts.allow with ALL: 192. > > Any other suggestions to assist troubleshooting this? I haven't > seen any messages output to any of the logs when attempting to ssh > into the machine. ssh running but producing no messages anywhere means that it's not seeing any traffic. to me this sounds like a basic connectivity issue or a banal misconfiguration, but ICBW. - Peter -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: Huawei E355 and OBSD as SMS gateway
Tito Mari Francis Escaño wrote: Hello everyone, I researched online for using Huawei E355 with OpenBSD as a means to create an SMS gateway, however I did not find any reliable resource on this. Can somebody also please point me to the proper direction how OBSD can be used as an SMS gateway? I have seen many references only for Linux-based systems. Hope you could help me. With gratitude, thank you very much. If the Huawei E355 attaches as a modem, you can probably just use standard AT commands to send SMSs. Otherwise a lot of modems do exist that work fine for this. The ones I have used, use a standard RS-232 interface. Best regards, Mikkel C. Simonsen
Re: Cannot SSH to OpenBSD from machines on network
On Fri 24 Jan 2014 15:50:18 GMT, Dan Daley wrote: I am new to OpenBSD and just installed 5.4 on an AMD 64 machine. Still running generic kernel. sshd is running and I can ssh into the local machine using ssh 192.168.1.4 However, if I attempt to ssh into the box from another machine on the network, I get "Operation timed out" I tried disabling pf by adding PF=NO to rc.conf.local, to make sure that that wasn't the culprit, but that didn't help. I also attempted to telnet to port 22 to see if I received the SSH header response… but that timed out with no response. Also tried with a hosts.allow with ALL: 192. Any other suggestions to assist troubleshooting this? I haven't seen any messages output to any of the logs when attempting to ssh into the machine. Dan. Check pf is really disabled with 'pfctl -d'
Cannot SSH to OpenBSD from machines on network
I am new to OpenBSD and just installed 5.4 on an AMD 64 machine. Still running generic kernel. sshd is running and I can ssh into the local machine using ssh 192.168.1.4 However, if I attempt to ssh into the box from another machine on the network, I get "Operation timed out" I tried disabling pf by adding PF=NO to rc.conf.local, to make sure that that wasn't the culprit, but that didn't help. I also attempted to telnet to port 22 to see if I received the SSH header response… but that timed out with no response. Also tried with a hosts.allow with ALL: 192. Any other suggestions to assist troubleshooting this? I haven't seen any messages output to any of the logs when attempting to ssh into the machine. Dan.
Re: Huawei E355 and OBSD as SMS gateway
On Fri, January 24, 2014 17:38, David Coppa wrote: > On Fri, Jan 24, 2014 at 2:29 PM, Tito Mari Francis Esca?o > wrote: >> Hello everyone, >> I researched online for using Huawei E355 with OpenBSD as a means to create >> an SMS gateway, however I did not find any reliable resource on this. >> Can somebody also please point me to the proper direction how OBSD can be >> used as an SMS gateway? I have seen many references only for Linux-based >> systems. >> Hope you could help me. With gratitude, thank you very much. > > Does this device attach as umsm? i.e. do you have an ucom* at umsm in > your dmesg? > If so, you can use SMS Server Tools, just "pkg_add smstools3". > See: http://smstools3.kekekasvi.com/index.php?p=configure > On OpenBSD the device is usually /dev/cuaUX, where X is 0, 1, or 2, > you need to find it, as it changes from device to device... You can probe it with 'cu -s 9600 -l /dev/cuaUX' and send 'AT'. The port you need should answer you 'OK' > > ciao, > David
Re: Trouble with Huawei e3276
On Fri, January 24, 2014 16:52, Кирилл Каплин wrote:
> sorry for delay!
> after this patch, after attach in dmesg:
> umsm0 at uhub2 port 5 configuration 1 interface 0 "Technology Mobile" rev
> 2.00/1.02 addr 3
> umsm0 detached
> urndis0 at uhub2 port 5 configuration 1 interface 0 "Technology Mobile" rev
> 2.00/1.02 addr 3
> urndis0: using Vendorurndis0: ctrl message error: wrong size 3735928559 >
> 1024
> urndis0: unable to get query response
> : unable to get hardware address
> urndis1 at uhub2 port 5 configuration 1 interface 2 "Technology Mobile" rev
> 2.00/1.02 addr 3
> urndis1: using Vendorurndis1: ctrl message error: wrong size 3736059565 >
> 1024
> urndis1: unable to get query response
> : unable to get hardware address
> umass0 at uhub2 port 5 configuration 1 interface 4 "Technology Mobile" rev
> 2.00/1.02 addr 3
> umass0: using SCSI over Bulk-Only
> scsibus4 at umass0: 2 targets, initiator 0
> sd7 at scsibus4 targ 1 lun 0: <, TF CARD Storage, 2.31> SCSI2 0/direct
> removable
> urndis2 at uhub2 port 5 configuration 1 interface 5 "Technology Mobile" rev
> 2.00/1.02 addr 3
> urndis2: no data interface
Hi. Take a look at this: http://www.hub.ru/wiki/Huawei_E3276 (in russian). I
suppose you can enable modem functions using AT commands under off-topic OS.
Basically such AT "tweaks" are possible with almost all modems.
>
>
>
> On Thu, Jan 23, 2014 at 1:36 PM, David Coppa wrote:
>
>>
>> > From: night...@gmail.com
>> > Date: Thu, Jan 23, 2014 at 10:01 AM
>> > Subject: Re: Trouble with Huawei e3276
>> > To: misc
>>
>> ...
>>
>> > port 6 addr 3: high speed, power 500 mA, config 1, Mobile(0x155b),
>> > Technology(0x12d1), rev 1.02
>> >umass1
>>
>> ...
>>
>> Please try the attached diff:
>>
>> $ cd /usr/src/sys/dev/usb && patch -NE -i /path/to/e3276.diff
>>
>> And rebuild your kernel.
>>
>> Ciao,
>> David
>>
>> Index: umsm.c
>> ===
>> RCS file: /cvs/src/sys/dev/usb/umsm.c,v
>> retrieving revision 1.96
>> diff -u -p -u -p -r1.96 umsm.c
>> --- umsm.c 13 Dec 2013 17:43:07 - 1.96
>> +++ umsm.c 23 Jan 2014 09:27:57 -
>> @@ -138,6 +138,7 @@ static const struct umsm_type umsm_devs[
>> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E1820 }, DEV_UMASS5},
>> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E220 }, DEV_HUAWEI},
>> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E303 }, DEV_UMASS5},
>> + {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E3276 }, DEV_UMASS5},
>> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E353_INIT },
>> DEV_UMASS5},
>> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E510 }, DEV_HUAWEI},
>> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E618 }, DEV_HUAWEI},
>> Index: usbdevs
>> ===
>> RCS file: /cvs/src/sys/dev/usb/usbdevs,v
>> retrieving revision 1.622
>> diff -u -p -u -p -r1.622 usbdevs
>> --- usbdevs 22 Jan 2014 01:25:41 - 1.622
>> +++ usbdevs 23 Jan 2014 09:28:02 -
>> @@ -2153,6 +2153,7 @@ product HUAWEI K4510 0x14c5 HUAWEI Mob
>> product HUAWEI E353_INIT 0x14fe HUAWEI Mobile E353 Initial
>> product HUAWEI E392_INIT 0x1505 HUAWEI Mobile E392 Initial
>> product HUAWEI K3765_INIT 0x1520 HUAWEI Mobile K3765 Initial
>> +product HUAWEI E3276 0x155b HUAWEI Mobile E3276
>> product HUAWEI E173S 0x1c05 HUAWEI Mobile E173s
>> product HUAWEI E173S_INIT 0x1c0b HUAWEI Mobile E173s Initial
>> product HUAWEI E3030x1f01 HUAWEI Mobile E303
>> Index: usbdevs.h
>> ===
>> RCS file: /cvs/src/sys/dev/usb/usbdevs.h,v
>> retrieving revision 1.634
>> diff -u -p -u -p -r1.634 usbdevs.h
>> --- usbdevs.h 22 Jan 2014 02:47:05 - 1.634
>> +++ usbdevs.h 23 Jan 2014 09:28:07 -
>> @@ -2160,6 +2160,7 @@
>> #defineUSB_PRODUCT_HUAWEI_E353_INIT0x14fe /* HUAWEI
>> Mobile E353 Initial */
>> #defineUSB_PRODUCT_HUAWEI_E392_INIT0x1505 /* HUAWEI
>> Mobile E392 Initial */
>> #defineUSB_PRODUCT_HUAWEI_K3765_INIT 0x1520 /* HUAWEI
>> Mobile K3765 Initial */
>> +#defineUSB_PRODUCT_HUAWEI_E32760x155b /* HUAWEI
>> Mobile E3276 */
>> #defineUSB_PRODUCT_HUAWEI_E173S0x1c05 /* HUAWEI
>> Mobile E173s */
>> #defineUSB_PRODUCT_HUAWEI_E173S_INIT 0x1c0b /* HUAWEI
>> Mobile E173s Initial */
>> #defineUSB_PRODUCT_HUAWEI_E303 0x1f01 /* HUAWEI Mobile
>> E303 */
>> Index: usbdevs_data.h
>> ===
>> RCS file: /cvs/src/sys/dev/usb/usbdevs_data.h,v
>> retrieving revision 1.628
>> diff -u -p -u -p -r1.628 usbdevs_data.h
>> --- usbdevs_data.h 22 Jan 2014 02:47:05 - 1.628
>> +++ usbdevs_data.h 23 Jan 2014 09:28:15 -
>> @@ -4562,6 +4562,10 @@ const struct usb_know
Re: Huawei E355 and OBSD as SMS gateway
On Fri, Jan 24, 2014 at 2:29 PM, Tito Mari Francis Escaño wrote: > Hello everyone, > I researched online for using Huawei E355 with OpenBSD as a means to create > an SMS gateway, however I did not find any reliable resource on this. > Can somebody also please point me to the proper direction how OBSD can be > used as an SMS gateway? I have seen many references only for Linux-based > systems. > Hope you could help me. With gratitude, thank you very much. Does this device attach as umsm? i.e. do you have an ucom* at umsm in your dmesg? If so, you can use SMS Server Tools, just "pkg_add smstools3". See: http://smstools3.kekekasvi.com/index.php?p=configure On OpenBSD the device is usually /dev/cuaUX, where X is 0, 1, or 2, you need to find it, as it changes from device to device... ciao, David
Re: Trouble with Huawei e3276
but it succesfully connects to it with program "my huawei terminal" under
windows.
anyway, thanks!
On Fri, Jan 24, 2014 at 5:03 PM, David Coppa wrote:
> On Fri, Jan 24, 2014 at 1:52 PM, ÐиÑилл Ðаплин
wrote:
> > sorry for delay!
> > after this patch, after attach in dmesg:
> > umsm0 at uhub2 port 5 configuration 1 interface 0 "Technology Mobile" rev
> > 2.00/1.02 addr 3
> > umsm0 detached
> > urndis0 at uhub2 port 5 configuration 1 interface 0 "Technology Mobile"
> rev
> > 2.00/1.02 addr 3
> > urndis0: using Vendorurndis0: ctrl message error: wrong size 3735928559 >
> > 1024
> > urndis0: unable to get query response
> > : unable to get hardware address
> > urndis1 at uhub2 port 5 configuration 1 interface 2 "Technology Mobile"
> rev
> > 2.00/1.02 addr 3
> > urndis1: using Vendorurndis1: ctrl message error: wrong size 3736059565 >
> > 1024
> > urndis1: unable to get query response
> > : unable to get hardware address
> > umass0 at uhub2 port 5 configuration 1 interface 4 "Technology Mobile"
> rev
> > 2.00/1.02 addr 3
> > umass0: using SCSI over Bulk-Only
> > scsibus4 at umass0: 2 targets, initiator 0
> > sd7 at scsibus4 targ 1 lun 0: <, TF CARD Storage, 2.31> SCSI2 0/direct
> > removable
> > urndis2 at uhub2 port 5 configuration 1 interface 5 "Technology Mobile"
> rev
> > 2.00/1.02 addr 3
> > urndis2: no data interface
>
>
> Oh, so this seems to be a LTE device!
> This particular modem has no modem interface, only NDIS.
> I know nothing about these devices, I'm sorry.
>
> Ciao,
> David
>
> > On Thu, Jan 23, 2014 at 1:36 PM, David Coppa wrote:
> >
> >>
> >> > From: night...@gmail.com
> >> > Date: Thu, Jan 23, 2014 at 10:01 AM
> >> > Subject: Re: Trouble with Huawei e3276
> >> > To: misc
> >>
> >> ...
> >>
> >> > port 6 addr 3: high speed, power 500 mA, config 1, Mobile(0x155b),
> >> > Technology(0x12d1), rev 1.02
> >> >umass1
> >>
> >> ...
> >>
> >> Please try the attached diff:
> >>
> >> $ cd /usr/src/sys/dev/usb && patch -NE -i /path/to/e3276.diff
> >>
> >> And rebuild your kernel.
> >>
> >> Ciao,
> >> David
> >>
> >> Index: umsm.c
> >> ===
> >> RCS file: /cvs/src/sys/dev/usb/umsm.c,v
> >> retrieving revision 1.96
> >> diff -u -p -u -p -r1.96 umsm.c
> >> --- umsm.c 13 Dec 2013 17:43:07 - 1.96
> >> +++ umsm.c 23 Jan 2014 09:27:57 -
> >> @@ -138,6 +138,7 @@ static const struct umsm_type umsm_devs[
> >> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E1820 }, DEV_UMASS5},
> >> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E220 }, DEV_HUAWEI},
> >> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E303 }, DEV_UMASS5},
> >> + {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E3276 }, DEV_UMASS5},
> >> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E353_INIT },
> >> DEV_UMASS5},
> >> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E510 }, DEV_HUAWEI},
> >> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E618 }, DEV_HUAWEI},
> >> Index: usbdevs
> >> ===
> >> RCS file: /cvs/src/sys/dev/usb/usbdevs,v
> >> retrieving revision 1.622
> >> diff -u -p -u -p -r1.622 usbdevs
> >> --- usbdevs 22 Jan 2014 01:25:41 - 1.622
> >> +++ usbdevs 23 Jan 2014 09:28:02 -
> >> @@ -2153,6 +2153,7 @@ product HUAWEI K4510 0x14c5 HUAWEI
> Mob
> >> product HUAWEI E353_INIT 0x14fe HUAWEI Mobile E353 Initial
> >> product HUAWEI E392_INIT 0x1505 HUAWEI Mobile E392 Initial
> >> product HUAWEI K3765_INIT 0x1520 HUAWEI Mobile K3765 Initial
> >> +product HUAWEI E3276 0x155b HUAWEI Mobile E3276
> >> product HUAWEI E173S 0x1c05 HUAWEI Mobile E173s
> >> product HUAWEI E173S_INIT 0x1c0b HUAWEI Mobile E173s Initial
> >> product HUAWEI E3030x1f01 HUAWEI Mobile E303
> >> Index: usbdevs.h
> >> ===
> >> RCS file: /cvs/src/sys/dev/usb/usbdevs.h,v
> >> retrieving revision 1.634
> >> diff -u -p -u -p -r1.634 usbdevs.h
> >> --- usbdevs.h 22 Jan 2014 02:47:05 - 1.634
> >> +++ usbdevs.h 23 Jan 2014 09:28:07 -
> >> @@ -2160,6 +2160,7 @@
> >> #defineUSB_PRODUCT_HUAWEI_E353_INIT0x14fe /*
> HUAWEI
> >> Mobile E353 Initial */
> >> #defineUSB_PRODUCT_HUAWEI_E392_INIT0x1505 /*
> HUAWEI
> >> Mobile E392 Initial */
> >> #defineUSB_PRODUCT_HUAWEI_K3765_INIT 0x1520 /*
> HUAWEI
> >> Mobile K3765 Initial */
> >> +#defineUSB_PRODUCT_HUAWEI_E32760x155b /*
> HUAWEI
> >> Mobile E3276 */
> >> #defineUSB_PRODUCT_HUAWEI_E173S0x1c05 /*
> HUAWEI
> >> Mobile E173s */
> >> #defineUSB_PRODUCT_HUAWEI_E173S_INIT 0x1c0b /*
> HUAWEI
> >> Mobile E173s Initial */
> >> #defineUSB_PRODUCT_HUAWEI_E303 0x1f01 /* HUAWEI Mobile
> >> E303 */
> >> Index: usbdevs_data.h
> >> ===
Huawei E355 and OBSD as SMS gateway
Hello everyone, I researched online for using Huawei E355 with OpenBSD as a means to create an SMS gateway, however I did not find any reliable resource on this. Can somebody also please point me to the proper direction how OBSD can be used as an SMS gateway? I have seen many references only for Linux-based systems. Hope you could help me. With gratitude, thank you very much.
Re: Trouble with Huawei e3276
On Fri, Jan 24, 2014 at 1:52 PM, Кирилл Каплин wrote:
> sorry for delay!
> after this patch, after attach in dmesg:
> umsm0 at uhub2 port 5 configuration 1 interface 0 "Technology Mobile" rev
> 2.00/1.02 addr 3
> umsm0 detached
> urndis0 at uhub2 port 5 configuration 1 interface 0 "Technology Mobile" rev
> 2.00/1.02 addr 3
> urndis0: using Vendorurndis0: ctrl message error: wrong size 3735928559 >
> 1024
> urndis0: unable to get query response
> : unable to get hardware address
> urndis1 at uhub2 port 5 configuration 1 interface 2 "Technology Mobile" rev
> 2.00/1.02 addr 3
> urndis1: using Vendorurndis1: ctrl message error: wrong size 3736059565 >
> 1024
> urndis1: unable to get query response
> : unable to get hardware address
> umass0 at uhub2 port 5 configuration 1 interface 4 "Technology Mobile" rev
> 2.00/1.02 addr 3
> umass0: using SCSI over Bulk-Only
> scsibus4 at umass0: 2 targets, initiator 0
> sd7 at scsibus4 targ 1 lun 0: <, TF CARD Storage, 2.31> SCSI2 0/direct
> removable
> urndis2 at uhub2 port 5 configuration 1 interface 5 "Technology Mobile" rev
> 2.00/1.02 addr 3
> urndis2: no data interface
Oh, so this seems to be a LTE device!
This particular modem has no modem interface, only NDIS.
I know nothing about these devices, I'm sorry.
Ciao,
David
> On Thu, Jan 23, 2014 at 1:36 PM, David Coppa wrote:
>
>>
>> > From: night...@gmail.com
>> > Date: Thu, Jan 23, 2014 at 10:01 AM
>> > Subject: Re: Trouble with Huawei e3276
>> > To: misc
>>
>> ...
>>
>> > port 6 addr 3: high speed, power 500 mA, config 1, Mobile(0x155b),
>> > Technology(0x12d1), rev 1.02
>> >umass1
>>
>> ...
>>
>> Please try the attached diff:
>>
>> $ cd /usr/src/sys/dev/usb && patch -NE -i /path/to/e3276.diff
>>
>> And rebuild your kernel.
>>
>> Ciao,
>> David
>>
>> Index: umsm.c
>> ===
>> RCS file: /cvs/src/sys/dev/usb/umsm.c,v
>> retrieving revision 1.96
>> diff -u -p -u -p -r1.96 umsm.c
>> --- umsm.c 13 Dec 2013 17:43:07 - 1.96
>> +++ umsm.c 23 Jan 2014 09:27:57 -
>> @@ -138,6 +138,7 @@ static const struct umsm_type umsm_devs[
>> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E1820 }, DEV_UMASS5},
>> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E220 }, DEV_HUAWEI},
>> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E303 }, DEV_UMASS5},
>> + {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E3276 }, DEV_UMASS5},
>> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E353_INIT },
>> DEV_UMASS5},
>> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E510 }, DEV_HUAWEI},
>> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E618 }, DEV_HUAWEI},
>> Index: usbdevs
>> ===
>> RCS file: /cvs/src/sys/dev/usb/usbdevs,v
>> retrieving revision 1.622
>> diff -u -p -u -p -r1.622 usbdevs
>> --- usbdevs 22 Jan 2014 01:25:41 - 1.622
>> +++ usbdevs 23 Jan 2014 09:28:02 -
>> @@ -2153,6 +2153,7 @@ product HUAWEI K4510 0x14c5 HUAWEI Mob
>> product HUAWEI E353_INIT 0x14fe HUAWEI Mobile E353 Initial
>> product HUAWEI E392_INIT 0x1505 HUAWEI Mobile E392 Initial
>> product HUAWEI K3765_INIT 0x1520 HUAWEI Mobile K3765 Initial
>> +product HUAWEI E3276 0x155b HUAWEI Mobile E3276
>> product HUAWEI E173S 0x1c05 HUAWEI Mobile E173s
>> product HUAWEI E173S_INIT 0x1c0b HUAWEI Mobile E173s Initial
>> product HUAWEI E3030x1f01 HUAWEI Mobile E303
>> Index: usbdevs.h
>> ===
>> RCS file: /cvs/src/sys/dev/usb/usbdevs.h,v
>> retrieving revision 1.634
>> diff -u -p -u -p -r1.634 usbdevs.h
>> --- usbdevs.h 22 Jan 2014 02:47:05 - 1.634
>> +++ usbdevs.h 23 Jan 2014 09:28:07 -
>> @@ -2160,6 +2160,7 @@
>> #defineUSB_PRODUCT_HUAWEI_E353_INIT0x14fe /* HUAWEI
>> Mobile E353 Initial */
>> #defineUSB_PRODUCT_HUAWEI_E392_INIT0x1505 /* HUAWEI
>> Mobile E392 Initial */
>> #defineUSB_PRODUCT_HUAWEI_K3765_INIT 0x1520 /* HUAWEI
>> Mobile K3765 Initial */
>> +#defineUSB_PRODUCT_HUAWEI_E32760x155b /* HUAWEI
>> Mobile E3276 */
>> #defineUSB_PRODUCT_HUAWEI_E173S0x1c05 /* HUAWEI
>> Mobile E173s */
>> #defineUSB_PRODUCT_HUAWEI_E173S_INIT 0x1c0b /* HUAWEI
>> Mobile E173s Initial */
>> #defineUSB_PRODUCT_HUAWEI_E303 0x1f01 /* HUAWEI Mobile
>> E303 */
>> Index: usbdevs_data.h
>> ===
>> RCS file: /cvs/src/sys/dev/usb/usbdevs_data.h,v
>> retrieving revision 1.628
>> diff -u -p -u -p -r1.628 usbdevs_data.h
>> --- usbdevs_data.h 22 Jan 2014 02:47:05 - 1.628
>> +++ usbdevs_data.h 23 Jan 2014 09:28:15 -
>> @@ -4562,6 +4562,10 @@ const struct usb_known_product usb_known
>> "HUAWEI Mobile K3765 Initial",
>
Re: Trouble with Huawei e3276
sorry for delay!
after this patch, after attach in dmesg:
umsm0 at uhub2 port 5 configuration 1 interface 0 "Technology Mobile" rev
2.00/1.02 addr 3
umsm0 detached
urndis0 at uhub2 port 5 configuration 1 interface 0 "Technology Mobile" rev
2.00/1.02 addr 3
urndis0: using Vendorurndis0: ctrl message error: wrong size 3735928559 >
1024
urndis0: unable to get query response
: unable to get hardware address
urndis1 at uhub2 port 5 configuration 1 interface 2 "Technology Mobile" rev
2.00/1.02 addr 3
urndis1: using Vendorurndis1: ctrl message error: wrong size 3736059565 >
1024
urndis1: unable to get query response
: unable to get hardware address
umass0 at uhub2 port 5 configuration 1 interface 4 "Technology Mobile" rev
2.00/1.02 addr 3
umass0: using SCSI over Bulk-Only
scsibus4 at umass0: 2 targets, initiator 0
sd7 at scsibus4 targ 1 lun 0: <, TF CARD Storage, 2.31> SCSI2 0/direct
removable
urndis2 at uhub2 port 5 configuration 1 interface 5 "Technology Mobile" rev
2.00/1.02 addr 3
urndis2: no data interface
On Thu, Jan 23, 2014 at 1:36 PM, David Coppa wrote:
>
> > From: night...@gmail.com
> > Date: Thu, Jan 23, 2014 at 10:01 AM
> > Subject: Re: Trouble with Huawei e3276
> > To: misc
>
> ...
>
> > port 6 addr 3: high speed, power 500 mA, config 1, Mobile(0x155b),
> > Technology(0x12d1), rev 1.02
> >umass1
>
> ...
>
> Please try the attached diff:
>
> $ cd /usr/src/sys/dev/usb && patch -NE -i /path/to/e3276.diff
>
> And rebuild your kernel.
>
> Ciao,
> David
>
> Index: umsm.c
> ===
> RCS file: /cvs/src/sys/dev/usb/umsm.c,v
> retrieving revision 1.96
> diff -u -p -u -p -r1.96 umsm.c
> --- umsm.c 13 Dec 2013 17:43:07 - 1.96
> +++ umsm.c 23 Jan 2014 09:27:57 -
> @@ -138,6 +138,7 @@ static const struct umsm_type umsm_devs[
> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E1820 }, DEV_UMASS5},
> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E220 }, DEV_HUAWEI},
> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E303 }, DEV_UMASS5},
> + {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E3276 }, DEV_UMASS5},
> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E353_INIT },
> DEV_UMASS5},
> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E510 }, DEV_HUAWEI},
> {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E618 }, DEV_HUAWEI},
> Index: usbdevs
> ===
> RCS file: /cvs/src/sys/dev/usb/usbdevs,v
> retrieving revision 1.622
> diff -u -p -u -p -r1.622 usbdevs
> --- usbdevs 22 Jan 2014 01:25:41 - 1.622
> +++ usbdevs 23 Jan 2014 09:28:02 -
> @@ -2153,6 +2153,7 @@ product HUAWEI K4510 0x14c5 HUAWEI Mob
> product HUAWEI E353_INIT 0x14fe HUAWEI Mobile E353 Initial
> product HUAWEI E392_INIT 0x1505 HUAWEI Mobile E392 Initial
> product HUAWEI K3765_INIT 0x1520 HUAWEI Mobile K3765 Initial
> +product HUAWEI E3276 0x155b HUAWEI Mobile E3276
> product HUAWEI E173S 0x1c05 HUAWEI Mobile E173s
> product HUAWEI E173S_INIT 0x1c0b HUAWEI Mobile E173s Initial
> product HUAWEI E3030x1f01 HUAWEI Mobile E303
> Index: usbdevs.h
> ===
> RCS file: /cvs/src/sys/dev/usb/usbdevs.h,v
> retrieving revision 1.634
> diff -u -p -u -p -r1.634 usbdevs.h
> --- usbdevs.h 22 Jan 2014 02:47:05 - 1.634
> +++ usbdevs.h 23 Jan 2014 09:28:07 -
> @@ -2160,6 +2160,7 @@
> #defineUSB_PRODUCT_HUAWEI_E353_INIT0x14fe /* HUAWEI
> Mobile E353 Initial */
> #defineUSB_PRODUCT_HUAWEI_E392_INIT0x1505 /* HUAWEI
> Mobile E392 Initial */
> #defineUSB_PRODUCT_HUAWEI_K3765_INIT 0x1520 /* HUAWEI
> Mobile K3765 Initial */
> +#defineUSB_PRODUCT_HUAWEI_E32760x155b /* HUAWEI
> Mobile E3276 */
> #defineUSB_PRODUCT_HUAWEI_E173S0x1c05 /* HUAWEI
> Mobile E173s */
> #defineUSB_PRODUCT_HUAWEI_E173S_INIT 0x1c0b /* HUAWEI
> Mobile E173s Initial */
> #defineUSB_PRODUCT_HUAWEI_E303 0x1f01 /* HUAWEI Mobile
> E303 */
> Index: usbdevs_data.h
> ===
> RCS file: /cvs/src/sys/dev/usb/usbdevs_data.h,v
> retrieving revision 1.628
> diff -u -p -u -p -r1.628 usbdevs_data.h
> --- usbdevs_data.h 22 Jan 2014 02:47:05 - 1.628
> +++ usbdevs_data.h 23 Jan 2014 09:28:15 -
> @@ -4562,6 +4562,10 @@ const struct usb_known_product usb_known
> "HUAWEI Mobile K3765 Initial",
> },
> {
> + USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E3276,
> + "HUAWEI Mobile E3276",
> + },
> + {
> USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E173S,
> "HUAWEI Mobile E173s",
> },
Re: 10G with Intel card - GBIC options
On Fri 24 Jan 2014 09:59:04 GMT, Henning Brauer wrote: * Andy [2013-12-02 10:05]: Henning, could you please confirm for us if the 32bit bandwidth limit was lifted in the new queuing subsystem, or if it is just still in place whilst dual-running the new and the old? otoh it is still there, but rather easy to lift. Cool ok. We'll wait until the next release when the old queuing system is removed allowing for a code clean up and this limit is lifted :) Thanks for your work, Andy.
Re: 10G with Intel card - GBIC options
* Andy [2013-12-02 10:05]: > Henning, could you please confirm for us if the 32bit bandwidth limit was > lifted in the new queuing subsystem, or if it is just still in place whilst > dual-running the new and the old? otoh it is still there, but rather easy to lift. -- Henning Brauer, h...@bsws.de, henn...@openbsd.org BS Web Services GmbH, http://bsws.de, Full-Service ISP Secure Hosting, Mail and DNS Services. Dedicated Servers, Root to Fully Managed Henning Brauer Consulting, http://henningbrauer.com/
Re: OpenBGPd match clause with multihop BGP session
Laurent CARON(lca...@unix-scripts.info) on 2014.01.24 09:24:26 +0100: > On 24/01/2014 00:38, Sebastian Benoit wrote: > >This is normal behaivor (and perhaps a misunderstanding on your side): > > > >bgpd will only put routes into the fib that are best and valid in the rib. > > > >A route comming from an EBGP-peer is only valid if the nexthop is directly > >connected. To make the route valid you can force the nexthop to a useable > >nexthop, for exampe your $NERIM_PEER_v4. you could also use $NERIM_MY_v4. > > > >/Benno > > I perfectly understand bgpd needs a 'valid' nexthop to put routes into > the fib. I however (mistakingly?) thought having set nexthop blackhole > in the peer's stanza would make it. well, currently it does not. with a diff comited today you can use 127.0.0.1. However, it might be useful to have the blackhole depend on the reachablility of some other ip (the way it currently is). Does anybody use that or knows a use case for that? Otherwise we might just remove that and make it work the way you thought it would.
Re: OpenBGPd match clause with multihop BGP session
On 24/01/2014 00:38, Sebastian Benoit wrote: This is normal behaivor (and perhaps a misunderstanding on your side): bgpd will only put routes into the fib that are best and valid in the rib. A route comming from an EBGP-peer is only valid if the nexthop is directly connected. To make the route valid you can force the nexthop to a useable nexthop, for exampe your $NERIM_PEER_v4. you could also use $NERIM_MY_v4. /Benno I perfectly understand bgpd needs a 'valid' nexthop to put routes into the fib. I however (mistakingly?) thought having set nexthop blackhole in the peer's stanza would make it.
