Re: E3372: LCP: timeout sending Config-Requests
Hello, yes please provide /etc/ppp/connect-errors as mentioned and also a complete dmesg(8). Regards, Stefan > -Ursprüngliche Nachricht- > Von: Whistle > Gesendet: Donnerstag, 25. Juni 2020 13:31 > An: Kapfhammer, Stefan > Cc: Misc > Betreff: Re: E3372: LCP: timeout sending Config-Requests > > Hi Stefan, > no it's not Deutsche Telekom, it giffgaff in uk. > Do you still want the logs ? > Also tried to reboot on a linux image and it switchmode with > usb_switchmode then I rebooted (without detach it and without poweroff > the laptop) in openbsd and I found a ethernet interface (cdce0). I run > dhclient cdce0, it gave me the ip and I connected to the web page of the usb > stick and there I configured the profile with login,password,apm and then I > was online. Of course I cannot boot every time in linux to switch mode. > > > > Hey, > > > > do you want to connect to the german 'Deutsche Telekom' ? > > > > Please delete /etc/ppp/connect-errors and make ONE more run with 'pppd > > call telekom'. Then post this file here. > > > > Regards, > > Stefan > >
Re: AMD Ryzen
I have several Ryzen 3 and Ryzen 7 systems running OpenBSD 6.6 and 6.7, and they work great. 6.6 had some minor issues with Ryzen 3 graphics but these appear to be resolved in 6.7. Dave Raymond On 6/23/20, Joe Barnett wrote: > On 2020-06-23 08:56, Gregory Edigarov wrote: >> Hello, >> >> Can somebody tell me overall impressions/success stories of those >> systems? >> I am thinking of buying this system as my next desktop for OpenBSD of >> course, so please share. >> Most interesting would be dmesgs of some working configurations. >> Thanks a lot in advance >> -- >> With best regards, >> Gregory Edigarov > > I have a Ryzen 3 3200G sitting on an ASRock B450M-HDV R4.0 with 16GB > RAM, and it seems to run OpenBSD (6.7) very well. I added Window Maker > via packages, along with a few others such as firefox-esr, pidgin, qgis, > postgresql (both server and client), and a few others, again all from > packages. Bear in mind I usually use OpenBSD for network devices rather > than on the desktop, but my experiment so far with the above system and > config has been very positive -- very stable and responsive when booted > into the graphical environment. This machine has no wifi capability, so > I cannot comment on that, and I do not have speakers attached, so cannot > comment on sound support. > > This CPU is a somewhat new-ish model with built-in Radeon Vega graphics > which gave fits to several Linux distros*, but which seems to work right > out of the box with OpenBSD 6.7. > > *latest Debian, and latest Xubuntu experienced trouble on this machine > when in graphical mode, though the latest regular Ubuntu does work > nicely with this machine. > > Good luck, > > Joe > > dmesg: > OpenBSD 6.7 (GENERIC.MP) #2: Thu Jun 4 09:55:08 MDT 2020 > > r...@syspatch-67-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 14941401088 (14249MB) > avail mem = 14475939840 (13805MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 3.2 @ 0xe6cc0 (24 entries) > bios0: vendor American Megatrends Inc. version "P3.70" date 11/14/2019 > bios0: ASRock B450M-HDV R4.0 > acpi0 at bios0: ACPI 6.0 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP APIC FPDT FIDT SSDT SSDT SSDT MCFG AAFT HPET > UEFI SSDT CRAT CDIT SSDT SSDT WSMT > acpi0: wakeup devices GPP0(S4) GPP2(S4) GPP3(S4) GPP4(S4) GPP5(S4) > GPP6(S4) GP17(S4) XHC0(S4) XHC1(S4) GP18(S4) GPP1(S4) PTXH(S4) > acpitimer0 at acpi0: 3579545 Hz, 32 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: AMD Ryzen 3 3200G with Radeon Vega Graphics, 3593.83 MHz, 17-18-01 > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB,XSAVEOPT,XSAVEC,XGETBV1,XSAVES > cpu0: 64KB 64b/line 4-way I-cache, 32KB 64b/line 8-way D-cache, 512KB > 64b/line 8-way L2 cache, 4MB 64b/line 16-way L3 cache > cpu0: ITLB 64 4KB entries fully associative, 64 4MB entries fully > associative > cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully > associative > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > cpu0: apic clock running at 24MHz > cpu0: mwait min=64, max=64, C-substates=1.1, IBE > cpu1 at mainbus0: apid 2 (application processor) > cpu1: AMD Ryzen 3 3200G with Radeon Vega Graphics, 3593.21 MHz, 17-18-01 > cpu1: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB,XSAVEOPT,XSAVEC,XGETBV1,XSAVES > cpu1: 64KB 64b/line 4-way I-cache, 32KB 64b/line 8-way D-cache, 512KB > 64b/line 8-way L2 cache, 4MB 64b/line 16-way L3 cache > cpu1: ITLB 64 4KB entries fully associative, 64 4MB entries fully > associative > cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully > associative > cpu1: smt 0, core 2, package 0 > cpu2 at mainbus0: apid 1 (application processor) > cpu2: AMD Ryzen 3 3200G with Radeon Vega Graphics, 3593.21 MHz, 17-18-01 > cpu2: >
[Thunderbird] How to correctly set Mail-Followup-To header?
Greetings, Disclaimer: the topic isn't strictly OpenBSD related, but I'd love hearing comments from this community. I'm trying to get used (after a very long long time) to Thunderbird (mutt user for last 10 years or so...) and I'm struggling with mailing lists setting. In partucular, in mutt I declare the subscribed ones and the 'Mail-Followup-To' header is automatically added: [...] subscribe ^b...@openbsd.org$ ^misc@openbsd.org$ ^po...@openbsd.org$ ^t...@openbsd.org$ set followup_to = yes # Prevent receiving duplicate copies of replies to messages sent to mailing lists # Get a reply separately for any messages sent to known but not subscribed lists set honor_followup_to = yes # Honor Mail-Followup-To header when group-replying to a message [...] For Thunderbird (68.9.0), I found this very well written wiki article [1], but 'mail.identity.default.subscribed_mailing_lists' preference seems not to be there anymore. Of course, I could always set the header by hand, adding it to 'mail.compose.other.header', but I hope there is a smarter way... Any hints? All the best [1] https://wiki.mozilla.org/Thunderbird:Help_Documentation:Mail-Followup-To_and_Mail-Reply-To -- Alessandro De Laurenzis [mailto:jus...@atlantide.mooo.com] Web: http://www.atlantide.mooo.com LinkedIn: http://it.linkedin.com/in/delaurenzis
Re: Suggestions re error: "USB read failed" accessing Infinite Noise TRNG?
On 2020-06-25, Why 42? The lists account. wrote: > > On Wed, Jun 24, 2020 at 09:55:05AM -, Stuart Henderson wrote: >> > >> > Disable uftdi in your kernel config (boot -c, disable uftdi, quit) and >> > see if that works. The device is attaching as a serial port, but libftdi >> > probably wants it attaching to ugen. If that helps maybe we can add a >> > quirk to knock out just this device. Send usbdevs -v output. > > Hi Stuart, > > That's most helpful, thanks for the support. > > Unfortunately ... I fell at the first fence :(. After I enter 'boot -c' I > get several lines of output followed by a prompt. But the cursor is > flickering wildly and I can't enter any further input. > > At this point the first line, at the top of the screen, is an error: > 'kbc: cmd word write error' > > (This is with boot version: BOOTX64 3.52) > > A quick search on the net didn't show much, apart from a suggestion that > a USB keyboard won't work at this point because the USB subsystem hasn't > yet been discovered (that was back in 2015 though). I'm using both a USB > keyboard and mouse. > > Something is definitely faffing about with the USB bus though, every time > I press a key at the flickering cursor, the LEDs in my mouse light up ... > > I'll try the ktrace approach instead. > > Thanks again. > > Cheers, > Robb. > > # config -ef /bsd disable uftdi quit
Re: Stuck in Needbuf state, trying to understand (6.7)
On Thu, Jun 25, 2020 at 09:51:41PM -0400, sven falempin wrote: > Hello, > > I have a script that mostly untar stuff on a vnd device. > And i have the same problem with syspatch > > The program state gets into needbuf forever, ( the top state ). > > I'm trying to figure out what is happening, > I have a feeling it may be an entropy exhaustion > but it's just a guess. You can't always trust feelings. > > vmstat -m goes near 100% usage quickly > and swap/memory is like empty according to top. > > Is it possible to get out of `vmstat -m` logged memory, > could it be a limit in login.conf that I reach without knowing ? > > Once the problem is present, I cannot do anything but reboot > which does not help to understand what is going on. > > Please hAlp. You fail to report almost all relevent information. So we cannot help. -Otto
chromium-bsu(6) cheat
Hi misc, chormium-bsu(6) is a fun and hard top down shooter game. Try it out from the ports. By default the controls are arrow keys and space. At least try out the first level for 5 miinutes. Spoiler ahead. You have been warned. Cheat ahead. It's hard, right? If you use a laptop touchpad for movement, you will be able to accelerate and stop almost instantly. This isn't even the best part. Try shooting while moving. Your machine gun fire rate will be crazy fast. The ammo for additional machine guns (yellow skull) will be used up as fast as if not faster than plasma guns (purple skull). If this is a bug, please don't fix it. OpenBSD User
Re: IKEDv2 and alias addresses
On Sun, Jun 21, 2020 at 04:33:14PM -0400, Sonic wrote: > On Sun, Jun 21, 2020 at 12:11 PM Patrick Wildt wrote: > > If you want to use a specific address for a policy, you can use the > > "local" keyword to specify it. This is part of the policy, not a global > > option. > > > > Then iked(8) continues to losten on 0.0.0.0:500, but the policy will > > only match if the IP address match to the one specified as "local". > > My config is basically: > Remote: > === > local_gw="a.b.c.164" > local_net="172.20.28.0/23" > server_gw="x.y.z.45" > server_net="172.26.62.0/23" > state="active" > > ikev2 'remote_rsa' $state esp \ > from $local_net to $server_net \ > local $local_gw peer $server_gw \ > dstid server.example.com > === > Server: > === > local_gw="x.y.z.45" > local_net="172.26.62.0/23" > remote_gw="a.b.c.164" > remote_net="172.20.28.0/23" > state="passive" > > ikev2 'server_rsa' $state esp \ > from $local_net to $remote_net \ > local $local_gw peer $remote_gw \ > srcid server.example.com > === > > Both outside nets are /29's and the .164 and .45 are aliases, with > .161 and .41 being the main address. However in trouble shooting I > kept seeing information moving on the main addresses and my pf.conf > rules were configured for the alias addresses. > > Being new to ikev2 setup I may have this all wrong. > > Thanks! > I tried to reproduce your bug (on current) but it seems to work as intended for me. It would certainly help to have a bit more info such as an iked log and a tcpdump of your failed handshake as well as the used openbsd version.
Stuck in Needbuf state, trying to understand (6.7)
Hello, I have a script that mostly untar stuff on a vnd device. And i have the same problem with syspatch The program state gets into needbuf forever, ( the top state ). I'm trying to figure out what is happening, I have a feeling it may be an entropy exhaustion but it's just a guess. vmstat -m goes near 100% usage quickly and swap/memory is like empty according to top. Is it possible to get out of `vmstat -m` logged memory, could it be a limit in login.conf that I reach without knowing ? Once the problem is present, I cannot do anything but reboot which does not help to understand what is going on. Please hAlp.
Re: Suggestions re error: "USB read failed" accessing Infinite Noise TRNG?
On Wed, Jun 24, 2020 at 09:55:05AM -, Stuart Henderson wrote: > > > > Disable uftdi in your kernel config (boot -c, disable uftdi, quit) and > > see if that works. The device is attaching as a serial port, but libftdi > > probably wants it attaching to ugen. If that helps maybe we can add a > > quirk to knock out just this device. Send usbdevs -v output. Hi Stuart, That's most helpful, thanks for the support. Unfortunately ... I fell at the first fence :(. After I enter 'boot -c' I get several lines of output followed by a prompt. But the cursor is flickering wildly and I can't enter any further input. At this point the first line, at the top of the screen, is an error: 'kbc: cmd word write error' (This is with boot version: BOOTX64 3.52) A quick search on the net didn't show much, apart from a suggestion that a USB keyboard won't work at this point because the USB subsystem hasn't yet been discovered (that was back in 2015 though). I'm using both a USB keyboard and mouse. Something is definitely faffing about with the USB bus though, every time I press a key at the flickering cursor, the LEDs in my mouse light up ... I'll try the ktrace approach instead. Thanks again. Cheers, Robb.
Re: E3372: LCP: timeout sending Config-Requests
===> connect-errors abort on (BUSY) abort on (NO CARRIER) abort on (VOICE) report (CONNECT) timeout set to 20 seconds expect (OK) ^RSSI:23^M ^HCSQ:"LTE",54,53,116,26^M ^RSSI:25^M ^HCSQ:"LTE",58,53,121,24^M alarm send (AT^M) expect (OK) OK -- got it send (ATZ^M) expect (OK) OK -- got it send (AT+CMEE=2^M) expect (OK) OK -- got it send (AT^M) expect (OKd) OK^M ^RSSI:23^M ^HCSQ:"LTE",55,53,121,26^M ^RSSI:25^M ^HCSQ:"LTE",59,55,126,26^M alarm send (AT^M) expect (OK) OK -- got it send (ATI^M) expect (OK) Manufacturer: huawei^M Model: E3372^M Revision: 22.328.62.00.1217^M IMEI: x^M +GCAP: +CGSM,+DS,+ES^M OK -- got it send (ATZ^M) expect (OK) OK -- got it send (AT^M) expect (OK) OK -- got it send (AT+CGDCONT=1,"IP","giffgaff.com","0.0.0.0",0,0^M) expect (OK) OK -- got it send (ATD*99#^M) expect (CONNECT) CONNECT -- got it /bsd: umsm0 at uhub0 port 1 configuration 1 interface 0 "HUAWEI_MOBILE HUAWEI_MOBILE" rev 2.10/1.02 addr 2 /bsd: umsm0 detached /bsd: umsm0 at uhub0 port 1 configuration 1 interface 0 "HUAWEI_MOBILE HUAWEI_MOBILE" rev 2.10/1.02 addr 2 /bsd: ucom0 at umsm0 /bsd: umsm1 at uhub0 port 1 configuration 1 interface 1 "HUAWEI_MOBILE HUAWEI_MOBILE" rev 2.10/1.02 addr 2 pppd[2097]: pppd 2.3.5 started by lws, uid 0 pppd[2097]: Connect: ppp0 <--> /dev/cuaU0 pppd[2097]: LCP: timeout sending Config-Requests pppd[2097]: Connection terminated. pppd: Exit. /bsd: ucom0 detached /bsd: umsm0 detached /bsd: umsm1 detached > Hello, > > yes please provide /etc/ppp/connect-errors as mentioned and also a > complete dmesg(8). > > Regards, > Stefan >
Re: E3372: LCP: timeout sending Config-Requests
Hello, the chat script seems working, it got all commands recognized. For the peer parameters I can provide the following, which works: /dev/cuaU1 < or /dev/cuaU0 921600 modem crtscts lock defaultroute noipdefault :0.0.0.2 noauth user telekom <--- change to your setting connect '/usr/sbin/chat -v -s -f /etc/ppp/peers/chat/umts.telekom1' <--- change to your chat script path Please give feedback, if it works! Regards, Stefan > -Ursprüngliche Nachricht- > Von: Whistle > Gesendet: Donnerstag, 25. Juni 2020 22:29 > An: Kapfhammer, Stefan > Cc: Misc > Betreff: Re: E3372: LCP: timeout sending Config-Requests > > ===> connect-errors > abort on (BUSY) > abort on (NO CARRIER) > abort on (VOICE) > report (CONNECT) > timeout set to 20 seconds > expect (OK) > ^RSSI:23^M > ^HCSQ:"LTE",54,53,116,26^M > ^RSSI:25^M > ^HCSQ:"LTE",58,53,121,24^M > alarm > send (AT^M) > expect (OK) > OK > -- got it > > send (ATZ^M) > expect (OK) > OK > -- got it > > send (AT+CMEE=2^M) > expect (OK) > OK > -- got it > > send (AT^M) > expect (OKd) > OK^M > ^RSSI:23^M > ^HCSQ:"LTE",55,53,121,26^M > ^RSSI:25^M > ^HCSQ:"LTE",59,55,126,26^M > alarm > send (AT^M) > expect (OK) > OK > -- got it > > send (ATI^M) > expect (OK) > Manufacturer: huawei^M > Model: E3372^M > Revision: 22.328.62.00.1217^M > IMEI: x^M > +GCAP: +CGSM,+DS,+ES^M > OK > -- got it > > send (ATZ^M) > expect (OK) > OK > -- got it > > send (AT^M) > expect (OK) > OK > -- got it > > send (AT+CGDCONT=1,"IP","giffgaff.com","0.0.0.0",0,0^M) > expect (OK) > OK > -- got it > > send (ATD*99#^M) > expect (CONNECT) > CONNECT > -- got it > > /bsd: umsm0 at uhub0 port 1 configuration 1 interface 0 "HUAWEI_MOBILE > HUAWEI_MOBILE" rev 2.10/1.02 addr 2 > /bsd: umsm0 detached > /bsd: umsm0 at uhub0 port 1 configuration 1 interface 0 "HUAWEI_MOBILE > HUAWEI_MOBILE" rev 2.10/1.02 addr 2 > /bsd: ucom0 at umsm0 > /bsd: umsm1 at uhub0 port 1 configuration 1 interface 1 "HUAWEI_MOBILE > HUAWEI_MOBILE" rev 2.10/1.02 addr 2 > pppd[2097]: pppd 2.3.5 started by lws, uid 0 > pppd[2097]: Connect: ppp0 <--> /dev/cuaU0 > pppd[2097]: LCP: timeout sending Config-Requests > pppd[2097]: Connection terminated. > pppd: Exit. > /bsd: ucom0 detached > /bsd: umsm0 detached > /bsd: umsm1 detached > > > > Hello, > > > > yes please provide /etc/ppp/connect-errors as mentioned and also a > > complete dmesg(8). > > > > Regards, > > Stefan > >
Re: OpenBSD Readonly File System
On Wednesday, June 24, 2020 10:58 PM, Aaron Mason wrote: > Auto filesystem repair is bad juju. Indeed, but an unbootable network appliance thousands of miles away, is much much worse. Regards, Mogens Jensen
Re: OpenBSD Readonly File System
> On Mon, Jun 22, 2020 at 4:24 PM Mogens Jensen > wrote: >> +# NOTE: The do_fsck() function has been patched to run 'fsck -y' if an >> +# automatic file system check fails with exit code 8. I have quite a few machines patched like this. On 2020-06-24, Aaron Mason wrote: > Auto filesystem repair is bad juju. Nonsense. For many, the possible downsides of automatically running fsck -y are much less a problem than the downsides of *not* running it. Even if there is corruption, there's still a fair chance the machine will come up far enough to fix things. What else is someone going to do other than OOB/drive/fly/whatever to the machine, press enter and type "fsck -y"? They're not going to suddenly try to backup a dirty fs where they wouldn't already have backups. Someone who cares about the data will already have a way to rebuild or restore from backups.
Re: Sun Fire X2100 stops booting
On 2020-06-24, Jan Stary wrote: > This is current/amd64 on a Sun Fire X2100. > The boot sequence stops at the "root on wd0a ..." line > and nothing else happens. > > No, it's not redirecting the console. > Am I missing something obvious? > Is anyoney seeing the same? > > Below is the last working dmesg I have from the machine > - sorry it's so late. Try some other releases and see if you can figure out where it starts breaking. Compare dmesg between the last working one and a failing one.
Re: obsd 6.7 - TOR relay (non-exit) & /var folder
On 2020-06-24, Salvatore Cuzzilla wrote: > After few attempts, I can't still don't understand what's going on > it seems that the only way to free up the /var folder is to restart the > tor's daemon. > > "pkill -HUP -u _tor -U _tor -x tor" didn't help ... > > Other ideas? Did you figure out what files are involved? If it's logs, use syslog instead.
Re: obsd 6.7 - TOR relay (non-exit) & /var folder
Unfortunately the only think i know for sure is that the /var folder is constantly loosing free space & When i restart tor it gets back to normal. I can't (I don't know how to) figure out the involved files ... "du" is not really helping nor "fstat" ... Is there anything else i could test? On 25.06.2020 09:29, Stuart Henderson wrote: On 2020-06-24, Salvatore Cuzzilla wrote: After few attempts, I can't still don't understand what's going on it seems that the only way to free up the /var folder is to restart the tor's daemon. "pkill -HUP -u _tor -U _tor -x tor" didn't help ... Other ideas? Did you figure out what files are involved? If it's logs, use syslog instead. --- :wq, Salvatore.
Jonathan Gray committed backdoor named HDCP
OpenBSD + Digital Rights Management = <3 Good luck to you community of hypocrites, enjoy pseudo security! https://marc.info/?l=openbsd-cvs=159158830307568=2 https://marc.info/?l=openbsd-cvs=159158885907743=2 https://marc.info/?l=openbsd-cvs=159159173208497=2
Re: E3372: LCP: timeout sending Config-Requests
Hey, do you want to connect to the german 'Deutsche Telekom' ? Please delete /etc/ppp/connect-errors and make ONE more run with 'pppd call telekom'. Then post this file here. Regards, Stefan > -Ursprüngliche Nachricht- > Von: owner-m...@openbsd.org Im Auftrag > von Whistle > Gesendet: Mittwoch, 24. Juni 2020 22:10 > An: Misc > Betreff: E3372: LCP: timeout sending Config-Requests > > Hi, > I have the exactly same problem of the following guy: > https://marc.info/?l=openbsd-misc=151950994024553=2 > I have a e3372 mobile too but wiht openbsd 6.7. > But the guy forgotten to say how he solved the problem. > Anyone can help me ? > Anyway the following are my connections files: > > ===> /etc/ppp/peers/telekom > cuaU0 > user myuser888 > nocrtscts > defaultroute > noipdefault > ipcp-accept-local > ipcp-accept-remote > connect "/usr/sbin/chat -vs -f /etc/ppp/connect.telekom" > > > > /etc/ppp/connect.telekom > ABORT 'BUSY' > ABORT 'NO CARRIER' > ABORT 'VOICE' > REPORT CONNECT > TIMEOUT 20 > 'OK-AT-OK' 'ATZ' > 'OK' 'AT+CMEE=2' > 'OK' 'AT' > 'OK\d-AT-OK' 'ATI' > 'OK' 'ATZ' > 'OK' 'AT' > 'OK' AT+CGDCONT=1,"IP","giffgaff.com","0.0.0.0",0,0 > 'OK' 'ATD*99#' CONNECT > > and the Errors: > pppd[13820]: pppd 2.3.5 started by myuser, uid 0 > pppd[13820]: Connect: ppp0 <--> /dev/cuaU0 > pppd[13820]: LCP: timeout sending Config-Requests > pppd[13820]: Connection terminated. > pppd: Exit. > > > Thank you very much for your help.
Re: E3372: LCP: timeout sending Config-Requests
Hi Stefan, no it's not Deutsche Telekom, it giffgaff in uk. Do you still want the logs ? Also tried to reboot on a linux image and it switchmode with usb_switchmode then I rebooted (without detach it and without poweroff the laptop) in openbsd and I found a ethernet interface (cdce0). I run dhclient cdce0, it gave me the ip and I connected to the web page of the usb stick and there I configured the profile with login,password,apm and then I was online. Of course I cannot boot every time in linux to switch mode. > Hey, > > do you want to connect to the german 'Deutsche Telekom' ? > > Please delete /etc/ppp/connect-errors and make ONE more run with > 'pppd call telekom'. Then post this file here. > > Regards, > Stefan >
Re: obsd 6.7 - TOR relay (non-exit) & /var folder
On 2020/06/25 14:59, Salvatore Cuzzilla wrote: > > Unfortunately the only think i know for sure is that the /var folder is > constantly loosing free space & When i restart tor it gets back to > normal. I can't (I don't know how to) figure out the involved files ... > > "du" is not really helping nor "fstat" ... Is there anything else > i could test? du won't show size of an unlinked file. fstat won't show filenames but will show inode numbes. If it is from a file that existed at startup and was then moved away, you could capture inode numbers of all files on the filesystem when starting (find /var -ls, the first number is the inode number), then compare with the INUM column in fstat. Or, if you change logs to syslog, and that fixes the problem, you have your answer... > On 25.06.2020 09:29, Stuart Henderson wrote: > > On 2020-06-24, Salvatore Cuzzilla wrote: > > > After few attempts, I can't still don't understand what's going on > > > it seems that the only way to free up the /var folder is to restart the > > > tor's daemon. > > > > > > "pkill -HUP -u _tor -U _tor -x tor" didn't help ... > > > > > > Other ideas? > > > > Did you figure out what files are involved? > > > > If it's logs, use syslog instead. > > > > --- > :wq, > Salvatore.
