opensmtpd
Hi, I seen http://www.opensmtpd.org Does exist a stable version ? can we put it on production ? And what's about your handbook : https://www.poolp.org/OpenSMTPD/ Possible to have this hanbook in french ? Thank you very much for replies. All the best, Wesley M.
Re: opensmtpd
Check: 1) archives of misc@ 2) man smtpd 3) man smtpd.conf 4) as it's work in progress use current 5) some people use it in production On Thu, Nov 17, 2011 at 9:27 AM, Wesley M. open...@e-solutions.re wrote: Hi, I seen http://www.opensmtpd.org Does exist a stable version ? can we put it on production ? And what's about your handbook : https://www.poolp.org/OpenSMTPD/ Possible to have this hanbook in french ? Thank you very much for replies. All the best, Wesley M.
Re: opensmtpd
On Thu, Nov 17, 2011 at 12:27:47PM +0400, Wesley M. wrote: Hi, Hi, I seen http://www.opensmtpd.org Does exist a stable version ? can we put it on production ? The very first line on the website says: OpenSMTPD has not had a stable release yet ! I guess it is self explanatory ;-) When we have a stable release ready, we'll prepare an announcement, until then the choice to put it in production or not is yours, but not recommended as we still have 4 issues we consider showstoppers in the TODO. eric, chl and I are working actively on fixing these amongst other things And what's about your handbook : https://www.poolp.org/OpenSMTPD/ Possible to have this hanbook in french ? Very unlikely. Currently, it only contains a few pages and you will not learn anything from it that isn't already explained in the man pages. It is still work in progress, private and not very valuable. When I think it is a worthy complement to the official docs, I will let misc@ and tech@ know. For now you can assume it does not exist, I don't know when it'll be ready as I only work on it when I'm bored from code. Gilles -- Gilles Chehade http://www.poolp.org@poolpOrg
Re: opensmtpd
On Thu, Nov 17, 2011 at 10:24:39AM +0100, Gilles Chehade wrote: When I think it is a worthy complement to the official docs, I will let misc@ and tech@ know. For now you can assume it does not exist, I don't know when it'll be ready as I only work on it when I'm bored from code. Bored of code? I doubt this ever happens to you :) -- Antoine
Re: opensmtpd
On Thu, Nov 17, 2011 at 10:30:55AM +0100, Antoine Jacoutot wrote: On Thu, Nov 17, 2011 at 10:24:39AM +0100, Gilles Chehade wrote: When I think it is a worthy complement to the official docs, I will let misc@ and tech@ know. For now you can assume it does not exist, I don't know when it'll be ready as I only work on it when I'm bored from code. Bored of code? I doubt this ever happens to you :) s/bored from/too drunk to/ better ? ;-p -- Gilles Chehade http://www.poolp.org@poolpOrg
Re: opensmtpd
On Thu, Nov 17, 2011 at 10:35:20AM +0100, Gilles Chehade wrote: On Thu, Nov 17, 2011 at 10:30:55AM +0100, Antoine Jacoutot wrote: On Thu, Nov 17, 2011 at 10:24:39AM +0100, Gilles Chehade wrote: When I think it is a worthy complement to the official docs, I will let misc@ and tech@ know. For now you can assume it does not exist, I don't know when it'll be ready as I only work on it when I'm bored from code. Bored of code? I doubt this ever happens to you :) s/bored from/too drunk to/ better ? ;-p Yes, _that_ I can believe :) -- Antoine
Re : OpenBSD ipsec gateway behind a router
Hello, Joosep, thank you for pointing out this incompatibility. I have made tests with Fabio and that was the problem. Regarding the ipsec configuration behind nat routers it has been tested successfully between a 4.9 and a 4.4 openbsd with udp encapsulation and between a 4.9 openbsd and a fortigate (not behind nat). However I don't know about long term stability in those two cases. Regarding the configuration to adopt when the ipsec gateway is natted, I'm wondering if it's necessary to port forward udp 500 and 4500 pointing to the ipsec gateway on the LAN. I think yes if the two ipsec gateways are natted, and maybe if only one of them is natted. As for the configuration that I described below I have not tried to do a ping from LAN1 to LAN2 with the OpenBSD having only one interface. I will try to test it when I'll be able to. Something I'm still wondering is, how Openbsd knows that he's natted or not so that he should use udp 4500. I haven't seen anywhere in the configuration stating that I would use nat-t or not. Also, if two ipsec gateways are not natted but I want to force nat-t would that be possible ? Thanks - Mail original - De : Joosep joos...@gmail.com @ : misc@openbsd.org Cc : Envoyi le : Lundi 14 Novembre 2011 14h08 Objet : Re: OpenBSD ipsec gateway behind a router On Mon, Nov 14, 2011 at 2:00 PM, Mentesan mente...@gmail.com wrote: Hi :) I'm trying to do exactly this setup, between two OpenBSD boxes - 4.4 (central office) and 4.9 (branch office). With the following setup I can bring the tunnel up, but the networks can't talk to each other: Central ipsec.conf - ike passive esp tunnel from 10.20.0.0/16 to any \ srcid matriz.domain.com.br \ psk testefilial Branch ipsec.conf - matriz_net = 10.20.0.0/16 matriz_gw = 178.9.35.10 filial_net = 10.10.11.0/24 ike dynamic esp tunnel from $filial_net to $matriz_net peer $matriz_gw \ srcid filial.domain.com.br \ dstid matriz.domain.com.br \ psk testefilial --- # ipsecctl -sa FLOWS: flow esp in from 10.10.11.0/24 to 10.20.0.0/16 peer 185.53.27.23 srcid matriz.gruponp.com.br dstid filial.gruponp.com.br type use flow esp out from 10.20.0.0/16 to 10.10.11.0/24 peer 185.53.27.23 srcid matriz.gruponp.com.br dstid filial.gruponp.com.br type require SAD: esp tunnel from 178.9.35.10 to 185.53.27.23 spi 0x59f8b098 auth hmac-sha2-256 enc aes esp tunnel from 185.53.27.23 to 178.9.35.10 spi 0xda08a9c3 auth hmac-sha2-256 enc aes --- # route -n show -encap Routing tables Encap: Source Port Destination Port Proto SA(Address/Proto/Type/Direction) 10.10.11/240 10.20/16 0 0 185.53.27.23/esp/use/in 10.20/16 0 10.10.11/240 0 185.53.27.23/esp/require/out Fabio Almeida Em 13/11/2011, `s 12:06, Mik J escreveu: Hello, I would like to know if such configuration is possible. LAN1 (192.168.10.0/24) -- OpenBSD .99 -- .254 Router IPx -- Internet -- IPy IPSec_GW (Vendor) -- LAN2 (192.168.20.0/24) As you can see the OpenBSD 4.9 server sits on the LAN1 and has one physical interface. When it wants to access to the internet, its address 192.168.10.99 is natted in IPx and that's how the IPSec_GW(Vendor) sees the source packets. It's not really important now if other machines on LAN1 should ping machines on LAN2. I would like for now that the OpenBSD could ping machines on LAN2. I have search for examples on the internet for this particular case because the OpenBSD is behind a nat router. And I haven't found the proper way to do this. I don't even know if it's possible. I know some kind of nat-t should be used though. Does anyone have this configuration in place ? Thanks [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc] Hi! I think the problem in your case is HMAC-SHA2 incompatibility between releases before 4.7 and 4.7(and upwards) releases. Please check this link http://www.openbsd.org/faq/upgrade47.html#hmac-sha2 regards, Joosep
Multi Link PPP support in Kernel
Is it possible to enable multilink PPP using the kernel based: pppoe(4) ? Or does one have to resort to the userland pppoe/ppp(8) ? -- Russell Sutherand I+TS e: russell.sutherl...@utoronto.ca t: +1.416.978.0470 f: +1.416.978.6620 m: +1.416.803.0080
Re: Multi Link PPP support in Kernel
On 2011-11-17, Russell Sutherland russell.sutherl...@utoronto.ca wrote: Is it possible to enable multilink PPP using the kernel based: pppoe(4) ? no, not supported. Or does one have to resort to the userland pppoe/ppp(8) ? wow, people really still use multilink? i remember it being a fair hassle on the lns side back when we did it with dialup... over here (UK) the few people doing this sort of thing use per-packet IP load-balancing these days.
OpenBSD 5.0 upgrade: em interface status no carrier
Hi, After upgrading from OpenBSD 4.9 to OpenBSD 5.0, the Intel 82579LM and Intel PRO/1000 MT (82574L) devices on one of my servers no longer come up. The ifconfig output simply shows status: no carrier. Without network access I can't copy and paste an entire dmesg, so here's some cherry-picked info: # uname -mrsv OpenBSD 5.0 GENERIC.MP#63 amd64 # dmesg | head -2 OpenBSD 5.0 (GENERIC.MP) #63: Wed Aug 17 10:14:30 MDT 2011 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP # dmesg | grep em[01] em0 at pci0 dev 25 function 0 Intel 82579LM rev 0x05: msi, address 00:25:90:52:b2:c1 em1 at pci2 dev 0 function 0 Intel PRO/1000 MT (82574L) rev 0x00: msi, address 00:25:90:52:b2:c0 # ifconfig em0 em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:25:90:52:b2:c1 priority: 0 groups: egress media: Ethernet autoselect (none) status: no carrier inet 10.0.2.7 netmask 0xff00 broadcast 10.255.255.255 inet6 fe80::225:90ff:fe52:b2c1%em0 prefixlen 64 scopeid 0x1 Running ifconfig down/up, manually choosing media types from the supported list and rebooting all have no effect. I've tried em1 as well without success. The connected switch is a Netgear GS116E and I've tried different cables and also a Netgear GS105E. I don't think it's the cable or switch though because rebooting back into 4.9 immediately brings the interface back to life. This is the hardware I'm having the problem on: http://www.supermicro.com/products/motherboard/Xeon/C202_C204/X9SCL-F.cfm I'm wondering if it's related to OpenBSD 5.0's new MSI interrupt code? Below is the dmesg when it's all up and working on 4.9. Is there anything I can try to narrow the problem down a bit further? Regards, Sam OpenBSD 4.9 (GENERIC.MP) #819: Wed Mar 2 06:57:49 MST 2011 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 3210297344 (3061MB) avail mem = 3110817792 (2966MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeadc0 (105 entries) bios0: vendor American Megatrends Inc. version 4.6.4 date 06/30/2011 bios0: Supermicro X9SCL/X9SCM acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP APIC SSDT MCFG HPET SPMI SPCR DMAR EINJ ERST HEST BERT acpi0: wakeup devices PS2K(S1) PS2M(S1) UAR1(S4) UAR2(S4) BR20(S1) EUSB(S4) USBE(S4) PEX0(S4) PEX4(S4) PEX6(S4) GBE_(S4) P0P1(S4) P0P2(S4) P0P3(S4) P0P4(S4) SLPB(S0) PWRB(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) CPU E31220L @ 2.20GHz, 2195.48 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,ES T,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,XSAVE,AVX,NXE,LONG cpu0: 256KB 64b/line 8-way L2 cache cpu0: apic clock running at 99MHz cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Xeon(R) CPU E31220L @ 2.20GHz, 2195.01 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,ES T,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,XSAVE,AVX,NXE,LONG cpu1: 256KB 64b/line 8-way L2 cache cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Xeon(R) CPU E31220L @ 2.20GHz, 2195.02 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,ES T,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,XSAVE,AVX,NXE,LONG cpu2: 256KB 64b/line 8-way L2 cache cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Xeon(R) CPU E31220L @ 2.20GHz, 2195.01 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,ES T,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,XSAVE,AVX,NXE,LONG cpu3: 256KB 64b/line 8-way L2 cache ioapic0 at mainbus0: apid 0 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 3 (BR20) acpiprt2 at acpi0: bus 1 (PEX0) acpiprt3 at acpi0: bus 2 (PEX4) acpiprt4 at acpi0: bus -1 (PEX6) acpiprt5 at acpi0: bus -1 (P0P1) acpiprt6 at acpi0: bus -1 (P0P2) acpiprt7 at acpi0: bus -1 (P0P3) acpiprt8 at acpi0: bus -1 (P0P4) acpicpu0 at acpi0: C3, C1, PSS acpicpu1 at acpi0: C3, C1, PSS acpicpu2 at acpi0: C3, C1, PSS acpicpu3 at acpi0: C3, C1, PSS acpibtn0 at acpi0: SLPB acpibtn1 at acpi0: PWRB ipmi at mainbus0 not configured cpu0: unknown i686 model 0x2a, can't get bus clock cpu0: Enhanced SpeedStep 2195 MHz: speeds: 2201, 2200, 2100, 2000, 1900, 1800, 1700, 1600 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0
Dhcpd.conf
If the name after host starts with a number, I get an error in
/var/log/messages and dhcpd fails to load.
host 5tbgx280 {
hardware ethernet 00:11:43:2f:87:d5;
fixed-address 192.168.1.112;
}
Nov 17 10:53:57 pj dhcpd[8557]: /etc/dhcpd.conf line 115: expecting left
brace.
Nov 17 10:53:57 pj dhcpd[8557]: host 5tbgx280
Starting the name with a letter fixes the error.
I did not find any info on the acceptable format of the host statement
in the dhcpd.conf man entry.
Is this an oversight on my part, or something that might documented
elsewhere?
Thanks,
Bill
OpenBSD 5.0 GENERIC#71 i386
OpenBSD 5.0-current (GENERIC) #71: Fri Oct 7 12:57:13 MDT 2011
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz (GenuineIntel
686-class) 3 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1
real mem = 3487547392 (3325MB)
avail mem = 3420450816 (3261MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 12/19/08, BIOS32 rev. 0 @ 0xfdba0,
SMBIOS rev. 2.5 @ 0xcfedf000 (39 entries)
bios0: vendor Phoenix Technologies LTD version 1.2a date 12/19/2008
bios0: Supermicro X7SBL
acpi0 at bios0: rev 2
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP _MAR TCPA MCFG HPET APIC BOOT SPCR ERST HEST
BERT EINJ SLIC SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT
acpi0: wakeup devices PEG_(S5) PEX_(S5) LAN_(S5) USB4(S5) USB5(S5)
USB7(S5) ESB2(S5) EXP1(S5) EXP5(S5) EXP6(S5) USB1(S5) USB2(S5) USB3(S5)
USB6(S5) ESB1(S5) PCIB(S5) KBC0(S1) MSE0(S1) COM1(S5) COM2(S5) PWRB(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimcfg0 at acpi0 addr 0xe000, bus 0-16
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 332MHz
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG_)
acpiprt2 at acpi0: bus -1 (PEX_)
acpiprt3 at acpi0: bus 5 (EXP1)
acpiprt4 at acpi0: bus 13 (EXP5)
acpiprt5 at acpi0: bus 15 (EXP6)
acpiprt6 at acpi0: bus 17 (PCIB)
acpicpu0 at acpi0: C3, PSS
acpibtn0 at acpi0: PWRB
acpivideo0 at acpi0: IGD0
bios0: ROM list: 0xc/0x8000 0xc8000/0x2a00! 0xcaa00/0x1000
ipmi at mainbus0 not configured
cpu0: Enhanced SpeedStep 2993 MHz: speeds: 3000, 2667, 2333, 2000 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 Intel 3200/3210 Host rev 0x01
uhci0 at pci0 dev 26 function 0 Intel 82801I USB rev 0x02: apic 2 int 16
uhci1 at pci0 dev 26 function 1 Intel 82801I USB rev 0x02: apic 2 int 17
uhci2 at pci0 dev 26 function 2 Intel 82801I USB rev 0x02: apic 2 int 18
ehci0 at pci0 dev 26 function 7 Intel 82801I USB rev 0x02: apic 2 int 18
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1
ppb0 at pci0 dev 28 function 0 Intel 82801I PCIE rev 0x02: apic 2 int 16
pci1 at ppb0 bus 5
ppb1 at pci0 dev 28 function 4 Intel 82801I PCIE rev 0x02: apic 2 int 16
pci2 at ppb1 bus 13
em0 at pci2 dev 0 function 0 Intel PRO/1000MT (82573E) rev 0x03: msi,
address 00:25:90:25:44:d8
ppb2 at pci0 dev 28 function 5 Intel 82801I PCIE rev 0x02: apic 2 int 17
pci3 at ppb2 bus 15
em1 at pci3 dev 0 function 0 Intel PRO/1000MT (82573L) rev 0x00: msi,
address 00:25:90:25:44:d9
uhci3 at pci0 dev 29 function 0 Intel 82801I USB rev 0x02: apic 2 int 23
uhci4 at pci0 dev 29 function 1 Intel 82801I USB rev 0x02: apic 2 int 22
uhci5 at pci0 dev 29 function 2 Intel 82801I USB rev 0x02: apic 2 int 18
ehci1 at pci0 dev 29 function 7 Intel 82801I USB rev 0x02: apic 2 int 23
usb1 at ehci1: USB revision 2.0
uhub1 at usb1 Intel EHCI root hub rev 2.00/1.00 addr 1
ppb3 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0x92
pci4 at ppb3 bus 17
em2 at pci4 dev 2 function 0 Intel PRO/1000GT (82541GI) rev 0x05: apic
2 int 20, address 00:1b:21:2d:38:c2
vga1 at pci4 dev 4 function 0 XGI Technology Volari Z9s/Z9m rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
ichpcib0 at pci0 dev 31 function 0 Intel 82801IR LPC rev 0x02: PM disabled
ahci0 at pci0 dev 31 function 2 Intel 82801I AHCI rev 0x02: msi, AHCI 1.2
scsibus0 at ahci0: 32 targets
sd0 at scsibus0 targ 5 lun 0: ATA, ST9750420AS, 0001 SCSI3 0/direct
fixed naa.5000c50029e59137
sd0: 715404MB, 512 bytes/sector, 1465149168 sectors
ichiic0 at pci0 dev 31 function 3 Intel 82801I SMBus rev 0x02: apic 2
int 17
iic0 at ichiic0
lm1 at iic0 addr 0x2d: W83627HF
wbng0 at iic0 addr 0x2f: w83793g
spdmem0 at iic0 addr 0x50: 2GB DDR2 SDRAM ECC PC2-6400CL5
spdmem1 at iic0 addr 0x52: 2GB DDR2 SDRAM ECC PC2-6400CL5
Intel 82801I Thermal rev 0x02 at pci0 dev 31 function 6 not configured
usb2 at uhci0: USB revision 1.0
uhub2 at usb2 Intel UHCI root hub rev
Re: OpenBSD 5.0 upgrade: em interface status no carrier
On 18/11/2011, at 12:59 PM, Sam Vaughan wrote: Hi, After upgrading from OpenBSD 4.9 to OpenBSD 5.0, the Intel 82579LM and Intel PRO/1000 MT (82574L) devices on one of my servers no longer come up. facepalm If I'd bothered to compare those two dmesg outputs more closely I'd have noticed that OpenBSD 5.0 is simply enumerating the two interfaces in the opposite order. What was em0 in 4.9 is now em1 in 5.0 and vice versa. Simply swapping the cable to the other port and _not_ moving the settings in ifconfig to em1 fixes the problem. Sorry for the noise. By the way, is there any reason why I should prefer the 82579LM to the 82574L or vice versa? Thanks, Sam
Re: Huawei EM770W mobile modem
On Thu, Nov 17, 2011 at 12:16 PM, Jonathan Gray j...@goblin.cx wrote: On Thu, Nov 17, 2011 at 09:27:32AM +0600, Baurzhan Muftakhidinov wrote: Hi all! I own a Acer Aspire ao532H netbook, and it has a Huawei EM770W mobile wcdma modem built-in. I think its internally connected via USB. Checked with usbdevs command. This modem does not work in stock OpenBSD 5.0 since its product ID is not listed in /sys/dev/usb/usbdevs, but this modem is supported by umsm driver (see below). Vendor is Huawei (0x12d1), product ID is (0x1404). I've added this is to usbdevs file, run make all in /sys/dev/usb ant this ID added to usbdevs.h. B I also added product ID to umsm.c, recompiled and booted new kernel and this modem worked just fine. The modem do not work with DEV_HUAWEI as umsm_flag (see /sys/dev/usb/umsm.c) but work with DEV_UMASS5 or 0 as umsm_flag. So here are my questions: 1) Maybe someone else also have this modem and can test it; 2) How to test which value of umsm_flag is correct (DEV_UMASS5 or 0), and what it affects to; If it works it is correct, the flags exist to change the mode of devices that come up as storage devices initially. 3) Since modem is working, who to ask to add it to umsm driver, should I fill bugreport or something? I've added it to umsm, thanks for the report. Thank you!
Re: Multi Link PPP support in Kernel
On 11/17/11 19:43, Stuart Henderson wrote: wow, people really still use multilink? i remember it being a fair hassle on the lns side back when we did it with dialup... over here (UK) the few people doing this sort of thing use per-packet IP load-balancing these days. Over here (Canada; Ontario specifically), where Russell and I are both located, the copper is owned by Bell Canada, a private company. They resell their bandwidth to independent ISPs, but *everyone* is stuck with the throttling that Bell applies during certain hours of the day. You mentioned dialup. Bell's throttle drops P2P traffic to the speed of a 56k modem, and to 28.8k during the most restrictive hours. I can't speak to Russell's reasons for using MLPPP, but myself and many others that use independent ISPs use MLPPP to evade the throttle. I don't know the technical details behind how it works, but it's currently the only way to get around Bell's throttle. Most people use the Tomato firmware on their modems, but OpenBSD does it perfectly for me. :) - Scott
Personal Branding para Asistentes Tu sello personal en el trabajo en Guadalajara.
[IMAGE] Pms de Mixico prestigiada firma de Capacitacisn presenta: Congreso Nacional Secretarias Ejecutivas y Asistentes 8 de Diciembre Guadalajara, Jalisco. -Mas de 900 asistentes satisfechas nos respaldansupera con ixito los retos del 2012. -Obtenga las herramientas necesarias para alcanzar un sptimo desempeqo en su funcisn. Empresa Registrada ante la STPS Smguenos en Twitter@pmscapacitacion o bien en Facebook PMS de Mixico. !Solicite Mayores Informes! Por favor responda este e-mail con los datos siguientes. Empresa: Nombre: Telifono: Email: Nzmero de Interesados: En breve recibira la informacisn completa de este inigualable evento. Comunmquese a los telifonos y con gusto uno de nuestros ejecutivos le atendera. Telifonos: (0133) 8851-2365, (0133) 8851-2741. Copyright (C) 2011, PMS Capacitacisn Efectiva de Mixico S.C. Derechos Reservados. PMS de Mixico, El logo de PMS de Mixico son marcas registradas. ADVERTENCIA PMS de Mixico no cuenta con alianzas estratigicas de ningzn tipo dentro de la Republica Mexicana. NO SE DEJE ENGAQAR - DIGA NO A LA PIRATERIA. Todos los logotipos, marcas comerciales e imagenes son propiedad de sus respectivas corporaciones y se utilizan con fines informativos solamente. Este Mensaje ha sido enviado a misc@openbsd.org como usuario de Pms de Mixico o bien un usuario le refiris para recibir este boletmn. Como usuario de Pms de Mixico, en este acto autoriza de manera expresa que Pms de Mixico le puede contactar vma correo electrsnico u otros medios. Si usted ha recibido este mensaje por error, haga caso omiso de el y reporte su cuenta respondiendo este correo con el subject BAJAASISTENTES Unsubscribe to this mailing list, reply a blank message with the subject UNSUBSCRIBE BAJAASISTENTES Tenga en cuenta que la gestisn de nuestras bases de datos es de suma importancia y no es intencisn de la empresa la inconformidad del receptor. [demime 1.01d removed an attachment of type image/jpeg which had a name of image001.jpg]
