Re: Removing IPv6 address causes all IPv6 traffic to stop working

2018-07-12 Thread Frank de Bot (lists)
The routes are not affected. the strangest thing I find that the host
and jails are accessible from outside, and it can reach outside hosts
via v6, but everything that's  staying on the server fails.

Alan Somers wrote:
> How did you assign the jails' IPv6 addresses in the first place?  The usual
> way is to assign them as /128 aliases, in which case the command to remove
> them would include a "/128", not "/48".  I think when you're deleting a
> "/48" you're also removing some routes that the jail host is using.
> -Alan
> 
> On Thu, Jul 12, 2018 at 4:30 PM, Frank de Bot (lists) 
> wrote:
> 
>> On a older server running FreeBSD 10.2 i have a number of jails. For
>> migration to FreeBSD I'm planning to shutdown the jail, move the data to
>> the new server and spin up the jail there. IP addresses are alse moved.
>>
>> When I remove an IPv6 address with the following command 'ifconfig em0
>> inet6 v6address/48 delete', all IPv6 traffic on the server stops
>> working. I can reach IPv6 from outside to the server and from the server
>> to outside, but everything on the server (jail to jail for example)
>> immediatly stops working. IPv4 works normally
>> Unfortunately it's not feasible to bing-bang migrate everything,
>> ignoring ipv6 is not possible because a lot of the jails interact with
>> each other with ipv6 (some even exclusivly)
>>
>> What can cause this?
>>
>>
>> Regards,
>>
>> Frank de Bot
>> ___
>> freebsd-stable@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>>
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
> 

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: Removing IPv6 address causes all IPv6 traffic to stop working

2018-07-12 Thread Alan Somers
How did you assign the jails' IPv6 addresses in the first place?  The usual
way is to assign them as /128 aliases, in which case the command to remove
them would include a "/128", not "/48".  I think when you're deleting a
"/48" you're also removing some routes that the jail host is using.
-Alan

On Thu, Jul 12, 2018 at 4:30 PM, Frank de Bot (lists) 
wrote:

> On a older server running FreeBSD 10.2 i have a number of jails. For
> migration to FreeBSD I'm planning to shutdown the jail, move the data to
> the new server and spin up the jail there. IP addresses are alse moved.
>
> When I remove an IPv6 address with the following command 'ifconfig em0
> inet6 v6address/48 delete', all IPv6 traffic on the server stops
> working. I can reach IPv6 from outside to the server and from the server
> to outside, but everything on the server (jail to jail for example)
> immediatly stops working. IPv4 works normally
> Unfortunately it's not feasible to bing-bang migrate everything,
> ignoring ipv6 is not possible because a lot of the jails interact with
> each other with ipv6 (some even exclusivly)
>
> What can cause this?
>
>
> Regards,
>
> Frank de Bot
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Removing IPv6 address causes all IPv6 traffic to stop working

2018-07-12 Thread Frank de Bot (lists)
On a older server running FreeBSD 10.2 i have a number of jails. For
migration to FreeBSD I'm planning to shutdown the jail, move the data to
the new server and spin up the jail there. IP addresses are alse moved.

When I remove an IPv6 address with the following command 'ifconfig em0
inet6 v6address/48 delete', all IPv6 traffic on the server stops
working. I can reach IPv6 from outside to the server and from the server
to outside, but everything on the server (jail to jail for example)
immediatly stops working. IPv4 works normally
Unfortunately it's not feasible to bing-bang migrate everything,
ignoring ipv6 is not possible because a lot of the jails interact with
each other with ipv6 (some even exclusivly)

What can cause this?


Regards,

Frank de Bot
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: syslogd not logging with . in program name

2018-07-12 Thread Matt Smith

On Jul 13 02:11, Eugene Grosbein wrote:

13.07.2018 1:14, Matt Smith wrote:


I run acme.sh with it configured to log to syslog. I use this syslog.conf 
structure to log to a specific log file:

!-acme.sh
... other syslog.conf entries ...
!acme.sh
*.*/var/log/acme.log
!*

This has worked for ages, but I've just noticed it's no longer working at all. 
It appears that syslogd is now not happy with a . character in a program name. 
I see that there have been a lot of commits to syslogd during June and July 
which may have changed the behavior?

If I run logger -p user.err -t acme.sh test message then nothing is logged. If 
I run logger -p user.err -t acme test message (removing the .sh), with the same 
change in syslog.conf, then everything is logged as normal.

Obviously . is used to separate facility and priority. Is it now being parsed 
wrongly in the case of a program name? I've tried things like putting it in 
quotes or escaping it with \ and it doesn't make any difference.


You have not specified which version/revision you run.


Whoops. My bad! It's 11.2-STABLE r336013. I'm not sure when this stopped 
working as I've only just noticed today but I usually do a buildworld 
every week. I took a look at svn log /usr/src/usr.sbin/syslogd though 
and can see there are quite a few updates in the last couple of months.


--
Matt
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: syslogd not logging with . in program name

2018-07-12 Thread Eugene Grosbein
13.07.2018 1:14, Matt Smith wrote:

> I run acme.sh with it configured to log to syslog. I use this syslog.conf 
> structure to log to a specific log file:
> 
> !-acme.sh
> ... other syslog.conf entries ...
> !acme.sh
> *.*/var/log/acme.log
> !*
> 
> This has worked for ages, but I've just noticed it's no longer working at 
> all. It appears that syslogd is now not happy with a . character in a program 
> name. I see that there have been a lot of commits to syslogd during June and 
> July which may have changed the behavior?
> 
> If I run logger -p user.err -t acme.sh test message then nothing is logged. 
> If I run logger -p user.err -t acme test message (removing the .sh), with the 
> same change in syslog.conf, then everything is logged as normal.
> 
> Obviously . is used to separate facility and priority. Is it now being parsed 
> wrongly in the case of a program name? I've tried things like putting it in 
> quotes or escaping it with \ and it doesn't make any difference.

You have not specified which version/revision you run.


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


syslogd not logging with . in program name

2018-07-12 Thread Matt Smith

Hi,

I run acme.sh with it configured to log to syslog. I use this 
syslog.conf structure to log to a specific log file:


!-acme.sh
... other syslog.conf entries ...
!acme.sh
*.*/var/log/acme.log
!*

This has worked for ages, but I've just noticed it's no longer working 
at all. It appears that syslogd is now not happy with a . character in a 
program name. I see that there have been a lot of commits to syslogd 
during June and July which may have changed the behavior?


If I run logger -p user.err -t acme.sh test message then nothing is 
logged. If I run logger -p user.err -t acme test message (removing the 
.sh), with the same change in syslog.conf, then everything is logged as 
normal.


Obviously . is used to separate facility and priority. Is it now being 
parsed wrongly in the case of a program name? I've tried things like 
putting it in quotes or escaping it with \ and it doesn't make any 
difference.


Thanks,

--
Matt
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Pós-Graduação SENAI | FATEC - MBA em Gestão de Projetos

2018-07-12 Thread SENAI | FATEC - Faculdade SENAI


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: Unable to boot memstick on APU2

2018-07-12 Thread Stefan Bethke
It appears that I just got lucky the one time. The same USB stick continues to 
mount only about half the time; other USB devices also have problems. It 
appears to me that the APU2 USB3 controller is not working correctly.  I’ve 
started a new thread over on freebsd-usb@


Stefan

> Am 09.07.2018 um 13:12 schrieb Stefan Bethke :
> 
> Thanks for the suggestions!
> 
> I did manage to get a working stick; the first couple of tries I did from m 
> MacBook Pro; finally I moved the stick to a physical FreeBSD box. Maybe the 
> Mac somehow "repaired" the GPT/MBR on the stick, making it invisible to the 
> FreeBSD kernel? But then at least da0 should have shown up. Maybe I just got 
> lucky.
> 
> If anyone is interested, I can try re-creating the issues for a week or two 
> while I still have the APU in a lab setting.
> 
> Stefan
> 
>> Am 08.07.2018 um 18:02 schrieb Stefan Bethke :
>> 
>> I'm stumped by a weird error: loader loads the kernel, and the kernel probes 
>> the USB stick successfully, but da0 never shows up. I’ve tried with 
>> FreeBSD-11.1-RELEASE-amd64-memstick.img and 
>> FreeBSD-11.2-RELEASE-amd64-memstick.img.
>> 
>> While at the mount root prompt, unplugging and replugging the USB stick and 
>> entering . repeatedly will show the kernel messages, but "da0 at umass0" 
>> never shows up.
>> 
>> I’ve added a couple entries to /boot/loader.conf:
>> # cat /mnt/boot/loader.conf
>> vfs.mountroot.timeout="10"
>> beastie_disable="YES"
>> comconsole_speed="115200"
>> console="comconsole"
>> autoboot_delay="1"
>> 
>> 
>> Here’s the console output from 11.1:
>> Consoles: internal video/keyboard   ce+0x67
>> BIOS drive C: is disk0 t vpanic+0x177
>> BIOS drive D: is disk1 t panic+0x43
>> BIOS 638kB/3668660kB available memory +0x1d95
>> 4 0x80a93b68 at start_init+0x48
>> FreeBSD/x86 bootstrap loader, Revision 1.1
>> (Fri Jul 21 02:03:08 UTC 2017 r...@releng2.nyi.freebsd.org)
>> Loading /boot/defaults/loader.conf
>> //boot/kernel/kernel text=0x14972f8 data=0x1384c0+0x4c15e8 
>> syms=[0x8+0x15e8b0+0x8+0x178422]ild 20170228
>> /080 MB ECC DRAM
>> Hit [Enter] to boot immediately, or any other key for command prompt.
>> Booting [/boot/kernel/kernel]...
>> Copyright (c) 1992-2017 The FreeBSD Project.
>> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
>>  The Regents of the University of California. All rights reserved.
>> FreeBSD is a registered trademark of The FreeBSD Foundation.
>> FreeBSD 11.1-RELEASE #0 r321309: Fri Jul 21 02:08:28 UTC 2017
>>   r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
>> FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 
>> 4.0.0)
>> VT(vga): resolution 640x480
>> CPU: AMD GX-412TC SOC(998.15-MHz K8-class 
>> CPU)
>> Origin="AuthenticAMD"  Id=0x730f01  Family=0x16  Model=0x30  Stepping=1
>> Features=0x178bfbff
>> Features2=0x3ed8220b
>> AMD Features=0x2e500800
>> AMD 
>> Features2=0x1d4037ff
>> Structured Extended Features=0x8
>> XSAVE Features=0x1
>> SVM: NP,NRIP,AFlush,DAssist,NAsids=8
>> TSC: P-state invariant, performance statistics
>> real memory  = 4815060992 (4592 MB)
>> avail memory = 4087992320 (3898 MB)
>> Event timer "LAPIC" quality 100
>> ACPI APIC Table: 
>> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
>> FreeBSD/SMP: 1 package(s) x 4 core(s)
>> ioapic1: Changing APIC ID to 5
>> ioapic0  irqs 0-23 on motherboard
>> ioapic1  irqs 24-55 on motherboard
>> SMP: AP CPU #1 Launched!
>> SMP: AP CPU #2 Launched!
>> SMP: AP CPU #3 Launched!
>> Timecounter "TSC" frequency 998148849 Hz quality 1000
>> random: entropy device external interface
>> kbd0 at kbdmux0
>> netmap: loaded module
>> module_register_init: MOD_LOAD (vesa, 0x80f5b220, 0) error 19
>> nexus0
>> vtvga0:  on motherboard
>> cryptosoft0:  on motherboard
>> acpi0:  on motherboard
>> acpi0: Power Button (fixed)
>> cpu0:  on acpi0
>> cpu1:  on acpi0
>> cpu2:  on acpi0
>> cpu3:  on acpi0
>> atrtc0:  port 0x70-0x71 irq 8 on acpi0
>> Event timer "RTC" frequency 32768 Hz quality 0
>> attimer0:  port 0x40-0x43 irq 0 on acpi0
>> Timecounter "i8254" frequency 1193182 Hz quality 0
>> Event timer "i8254" frequency 1193182 Hz quality 100
>> Timecounter "ACPI-safe" frequency 3579545 Hz quality 850
>> acpi_timer0: <32-bit timer at 3.579545MHz> port 0x818-0x81b on acpi0
>> hpet0:  iomem 0xfed0-0xfed003ff on acpi0
>> Timecounter "HPET" frequency 14318180 Hz quality 950
>> acpi_button0:  on acpi0
>> pcib0:  port 0xcf8-0xcff on acpi0
>> pci0:  on pcib0
>> pcib1:  at device 2.2 on pci0
>> pcib1: failed to allocate initial I/O port window: 0x1000-0x1fff
>> pci1:  on pcib1
>> igb0:  mem 
>> 0xfe60-0xfe61,0xfe62-0xfe623fff at device 0.0 on pci1
>> igb0: Using MSIX interrupts with 5 vectors
>> igb0: Ethernet address: 00:0d:b9:4b:e2:cc
>> igb0: Bound queue 0 to cpu 0
>> igb0: Bound queue 1 to cpu 1
>> igb0: Bound queue 2 to cpu 2
>> igb0: Bound queue 3 to cpu 3
>> igb0: netmap queues/slots: TX 4/1024, RX 4/1

SAP Products Users List

2018-07-12 Thread camila . zarate





class="gmail-m_6350034823628897800gmail-m_-1605034654586745565gmail-m_-1881138833800936466gmail-MsoNoSpacing"  
style="margin:0in 0in  
0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Hi, 




class="gmail-m_6350034823628897800gmail-m_-1605034654586745565gmail-m_-1881138833800936466gmail-MsoNoSpacing"  
style="margin:0in 0in  
0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Would you be  
interested in SAP Products Users List? We endow  
the Database

across North America, EMEA, APAC and Latin America.

We also have other Technology

Users like: SAP HANA, SAP Business One, SAP HCM, SAP Crystal Reports,
 SAP ERP, SAP NetWeaver, ERP, CRM, Siebel Systems, SAP, IBM Cognos,
Salesforce, Business
Objects, Infor, NetSuite, Workday, Epicor, JDA Software and many  
more.


class="gmail-m_6350034823628897800gmail-m_-1605034654586745565gmail-m_-1881138833800936466gmail-MsoNoSpacing"  
style="margin:0in 0in  
0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"> 


class="gmail-m_6350034823628897800gmail-m_-1605034654586745565gmail-m_-1881138833800936466gmail-MsoNoSpacing"  
style="margin:0in 0in  
0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">We provide

complete Information Fields like: - Name, Title, Email address, Phone
Numbers, Company Name, and Company Details like, Physical Address, Web  
Address,

Revenue Size, Employee Size and industry.

class="gmail-m_6350034823628897800gmail-m_-1605034654586745565gmail-m_-1881138833800936466gmail-MsoNoSpacing"  
style="margin:0in 0in  
0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
Please let me know your target criteria and I’ll get back to you with the  
more

information.

class="gmail-m_6350034823628897800gmail-m_-1605034654586745565gmail-m_-1881138833800936466gmail-MsoNoSpacing"  
style="margin:0in 0in 0.0001pt">style="font-size:11pt">

Looking forward to hear from you

Thanks and  
Regards, style="font-size:14.6667px">Camila Zaratestyle="font-family:Calibri,sans-serif;font-size:11pt">


class="gmail-m_6350034823628897800gmail-m_-1605034654586745565gmail-m_-1881138833800936466gmail-MsoNoSpacing"  
style="margin:0in 0in  
0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Cloud  
Consultant


class="gmail-m_6350034823628897800gmail-m_-1605034654586745565gmail-m_-1881138833800936466gmail-MsoNoSpacing"  
style="margin:0in 0in  
0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"> 


class="gmail-m_6350034823628897800gmail-m_-1605034654586745565gmail-m_-1881138833800936466gmail-MsoNoSpacing"  
style="margin:0in 0in  
0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"> 


class="gmail-m_6350034823628897800gmail-m_-1605034654586745565gmail-m_-1881138833800936466gmail-MsoNoSpacing"  
style="margin:0in 0in  
0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"> 


class="gmail-m_6350034823628897800gmail-m_-1605034654586745565gmail-m_-1881138833800936466gmail-MsoNoSpacing"  
style="text-align:center;margin:0in 0in  
0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"  
align="center">To Evacuate,  
please react

"Quit" in the Headline.








 href='chrome.google.com/webstore/detail/gsm-mailmerge/fjimadonilpeknihlnnkbgmlmjneodgk'>powered  
by GSM. Free mail merge and email marketing software for Gmail.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: Passing through USB serial to bhyve VM

2018-07-12 Thread Stefan Bethke
FWIW, I’ve opened a bug: 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229712

> Am 11.07.2018 um 23:41 schrieb Stefan Bethke :
> 
> It’s been a while since I last dealt with serial devices. Apparently, when 
> passing through a serial device on the host to a COM port in the VM, CTS/RTS 
> are not (correctly) passed through. With
>set ctsrts off
> in ppp.conf I could get ppp to dial successfully.
> 
> 
> Stefan
> 
>> Am 11.07.2018 um 19:22 schrieb Stefan Bethke :
>> 
>> I’m trying to access a Huawei USB LTE stick from a Bhyve VM like so:
>> # cat /var/vm/mgmt/mgmt.conf 
>> loader="bhyveload"
>> cpu=1
>> memory=256M
>> network0_type="virtio-net"
>> network0_switch="lan"
>> disk0_type="virtio-blk"
>> disk0_name="disk0"
>> disk0_dev="sparse-zvol"
>> uuid="53854567-8358-11e8-9638-000db94be2cc"
>> network0_mac="58:9c:fc:04:1d:52"
>> bhyve_options="-lcom2,/dev/cuaU0“
>> 
>> On the host, I can connect ppp(8), but inside the VM, ppp(8) appears not to 
>> be able to talk to the USB device. Using cu(1), I can talk to it just fine 
>> though. I’m not sure how to debug this further. Is this supposed to just 
>> work, or am I missing some obvious configuration bit?
>> 
>> [root@mgmt ~]# cu -l cuau1 -s 115200
>> Connected
>> ATZ
>> OK
>> ATI
>> Manufacturer: huawei
>> Model: E3272
>> Revision: 22.436.07.02.1202
>> IMEI: 867503015nn
>> +GCAP: +CGSM,+DS,+ES
>> 
>> OK
>> ~
>> [EOT]
>> [root@mgmt ~]# ppp
>> Working in interactive mode
>> Using interface: tun0
>> Phase: PPP Started (interactive mode).
>> ppp ON mgmt> dial
>> Phase: bundle: Establish
>> Phase: deflink: closed -> opening
>> Phase: deflink: Connected!
>> Phase: deflink: opening -> dial
>> Chat: deflink: Dial attempt 1 of 1
>> ppp ON mgmt> Chat: Send: ATZ
>> Chat: Expect(5): OK
>> Chat: Expect timeout
>> Chat: Send: ATZ
>> Chat: Expect(5): OK
>> Chat: Expect timeout
>> Warning: Chat script failed
>> Phase: deflink: dial -> hangup
>> Phase: deflink: Disconnected!
>> Phase: deflink: Connect time: 11 secs: 0 octets in, 0 octets out
>> Phase: deflink: 0 packets in, 0 packets out
>> Phase:  total 0 bytes/sec, peak 0 bytes/sec on Wed Jul 11 21:14:43 2018
>> Phase: deflink: hangup -> closed
>> Phase: bundle: Dead
>> ppp ON mgmt> quit
>> [root@mgmt ~]# cat /etc/ppp/ppp.conf
>> default:
>>   enable dns
>>   set log local LCP IPCP Phase Chat
>>  set log all
>>   set timeout 0
>>   ident UMTS
>>   set authname eplus
>>   set authkey internet
>>   set cd off
>>   set device /dev/cuau1
>>   set speed 115200
>>   set dial "ABORT BUSY ABORT NO\\sCARRIER \
>>   ABORT VOICE ABORT NO\\sDIALTONE ABORT NO\\sDIAL\\sTONE ABORT ERROR \
>>   ABORT NO\\sANSWER ABORT DELAYED TIMEOUT 5 \
>>   \"\" ATZ OK-ATZ-OK \
>>   AT+CFUN=1 OK \
>>   AT+CREG? OK \
>>   AT+COPS? OK \
>>   AT+CSQ OK \
>>  AT^HCSQ? OK \
>>   AT+cgdcont=1,\\\"IP\\\",\\\"internet.eplus.de\\\" OK \
>>   ATDT*99***1# CONNECT"
>>   set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0
>>   add default HISADDR
>> 
>> 
>> Stefan
>> 
>> -- 
>> Stefan BethkeFon +49 151 14070811
>> 
>> 
>> ___
>> freebsd-stable@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
> 
> -- 
> Stefan BethkeFon +49 151 14070811
> 
> 
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

-- 
Stefan BethkeFon +49 151 14070811


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"