Re: dual pppoe problem
On 2019/06/16 22:17, Sacha wrote: > > > *De :* Stuart Henderson > *Objet :* dual pppoe problem > *Date :* dimanche 16 juin 2019 à 21:30 > *Pour :* Sacha > *Cc :* bugs@openbsd.org > > > On 2019/06/16 10:33, Sacha wrote: > >> Hi, > >> > >> when I'm starting the system (OpenBSD 6.5 amd64) with dual pppoe > >> connections > >> only the first is going up. > >> > >> Here are my pppoe confs (changed $user and $psw): > > Your config is not included in the email. > > Sorry: > > > cerbere# cat > /etc/hostname.pppoe0 > > > inet 0.0.0.0 255.255.255.255 NONE \ > pppoedev em0 authproto pap \ > authname '$user1' authkey '$psw1' up > dest 0.0.0.1 > !/sbin/route add default -ifp pppoe0 0.0.0.1 > > cerbere# cat > /etc/hostname.pppoe1 > > > > > inet 0.0.0.0 255.255.255.255 NONE \ > pppoedev em1 authproto pap \ > authname '$use2' authkey '$psw2' up > dest 0.0.0.1 > > > >> I tried to change 0.0.0.0 to 0.0.0.2 in /etc/hostname.pppoe1, > > Why? > > > > From the manual pppoe(4) : > > > > " If the local address is set to wildcard address 0.0.0.0, it will be > > changed > > " to an address suggested by the peer. > > > > You want 0.0.0.0 on both interfaces. It is the "remote address" (0.0.0.1 on > > the > > first interface) that you need to change for the second. > > > It was a try as previous conf didn't worked. > > Sacha. > You need to change the "remote address" (0.0.0.1 on the first interface) to 0.0.0.2 on the second. If that doesn't work, please show "ifconfig pppoe" output.
Re: dual pppoe problem
*De :* Stuart Henderson *Objet :* dual pppoe problem *Date :* dimanche 16 juin 2019 à 21:30 *Pour :* Sacha *Cc :* bugs@openbsd.org > On 2019/06/16 10:33, Sacha wrote: >> Hi, >> >> when I'm starting the system (OpenBSD 6.5 amd64) with dual pppoe connections >> only the first is going up. >> >> Here are my pppoe confs (changed $user and $psw): > Your config is not included in the email. Sorry: cerbere# cat /etc/hostname.pppoe0 inet 0.0.0.0 255.255.255.255 NONE \ pppoedev em0 authproto pap \ authname '$user1' authkey '$psw1' up dest 0.0.0.1 !/sbin/route add default -ifp pppoe0 0.0.0.1 cerbere# cat /etc/hostname.pppoe1 inet 0.0.0.0 255.255.255.255 NONE \ pppoedev em1 authproto pap \ authname '$use2' authkey '$psw2' up dest 0.0.0.1 > >> I tried to change 0.0.0.0 to 0.0.0.2 in /etc/hostname.pppoe1, > Why? > > From the manual pppoe(4) : > > " If the local address is set to wildcard address 0.0.0.0, it will be > changed > " to an address suggested by the peer. > > You want 0.0.0.0 on both interfaces. It is the "remote address" (0.0.0.1 on > the > first interface) that you need to change for the second. > It was a try as previous conf didn't worked. Sacha.
Re: dual pppoe problem
On 2019/06/16 10:33, Sacha wrote: > Hi, > > when I'm starting the system (OpenBSD 6.5 amd64) with dual pppoe connections > only the first is going up. > > Here are my pppoe confs (changed $user and $psw): > > > Your config is not included in the email. > I tried to change 0.0.0.0 to 0.0.0.2 in /etc/hostname.pppoe1, Why? >From the manual pppoe(4) : " If the local address is set to wildcard address 0.0.0.0, it will be changed " to an address suggested by the peer. You want 0.0.0.0 on both interfaces. It is the "remote address" (0.0.0.1 on the first interface) that you need to change for the second.
dual pppoe problem
Hi, when I'm starting the system (OpenBSD 6.5 amd64) with dual pppoe connections only the first is going up. Here are my pppoe confs (changed $user and $psw): I tried to change 0.0.0.0 to 0.0.0.2 in /etc/hostname.pppoe1, it doesn't work. Why dual pppoe are not working ? Note on pppoe links are from same operators on dual adsl link with same gateway IP. Finaly to make it work, I have done a dirty dirty hack to make all work: mv /etc/hostname.pppoe1 /etc/hostname.pppoe1-sav and put the /root/pppoe1 in /etc/rc.local -- Sent from: http://openbsd-archive.7691.n7.nabble.com/openbsd-dev-bugs-f183916.html
Re: man page possible correction for ports, bsd.port.mk
On Wed, Jun 12, 2019 at 09:08:29AM -0500, myportslist20190...@nym.hush.com
wrote:
> 2. man bsd.port.mk: in the PORTS_PRIVSEP section, where one adds
> these commands to doas.conf: /usr/bin/touch, /usr/sbin/pkg_add, and
> /usr/sbin/pkg_delete, I think an additional line is needed:
>
> permit nopass setenv { TERM } solene cmd /usr/bin/env
Nope, you don't want that line.
If you allow /usr/bin/env without passwd, you may as well allow any command.
The tree was fixed post-6.5 so that normal usage would no longer need env.
Re: man ports says set PLIST_DB but PLIST_DB is deprecated
On Sun, Jun 16, 2019 at 07:17:35AM -0500, myportslist20190...@nym.hush.com wrote: > >Synopsis:man ports says set PLIST_DB but PLIST_DB is deprecated > >Category:man pages > >Environment: > System : OpenBSD 6.5 > Details : OpenBSD 6.5-current (GENERIC.MP) #22: Wed Jun 12 20:26:15 > MDT 2019 > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > Architecture: OpenBSD.amd64 > Machine : amd64 > >Description: > In USING A READ_ONLY PORTS tree section of man ports, it says set > PLIST_DB but (I believe it) should say set PLIST_REPOSITORY > Please note that man bsd.port.mk says PLIST_DB is deprecated. Also, > setting PLIST_DB in /etc/mk.conf > doesn't change permissions when one runs make fix-permissions, but make > fix-permissions does work if > one sets PLIST_REPOSITORY in /etc/mk.conf. This occurs because > /usr/ports/infrastructure/mk/bsd.port.mk in the > fix-permissions sections affects PLIST_REPOSITORY but not PLIST_DB. > >How-To-Repeat: > set PLIST_DB in /etc/mk.conf and then run make fix-permissions in > /usr/ports. The directory permissions for PLIST_DB are > not changed. But if PLIST_REPOSITORY is set in /etc/mk.conf and make > fix-permissions in /usr/ports is run, the permissions > are changed appropriately. > >Fix: > Index: share/man/man7/ports.7 > === > RCS file: /cvs/src/share/man/man7/ports.7,v > retrieving revision 1.126 > diff -u -p -u -r1.126 ports.7 > --- share/man/man7/ports.730 May 2019 09:24:08 - 1.126 > +++ share/man/man7/ports.716 Jun 2019 12:12:42 - > @@ -641,7 +641,7 @@ Set > .Ev UPDATE_COOKIES_DIR , > .Ev DISTDIR , > and > -.Ev PLIST_DB > +.Ev PLIST_REPOSITORY > in > .Pa /etc/mk.conf > accordingly. Ack... I should finish killing PLIST_DB actually. It's been deprecated for 3 years by now :)
man ports says set PLIST_DB but PLIST_DB is deprecated
>Synopsis: man ports says set PLIST_DB but PLIST_DB is deprecated >Category: man pages >Environment: System : OpenBSD 6.5 Details : OpenBSD 6.5-current (GENERIC.MP) #22: Wed Jun 12 20:26:15 MDT 2019 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP Architecture: OpenBSD.amd64 Machine : amd64 >Description: In USING A READ_ONLY PORTS tree section of man ports, it says set PLIST_DB but (I believe it) should say set PLIST_REPOSITORY Please note that man bsd.port.mk says PLIST_DB is deprecated. Also, setting PLIST_DB in /etc/mk.conf doesn't change permissions when one runs make fix-permissions, but make fix-permissions does work if one sets PLIST_REPOSITORY in /etc/mk.conf. This occurs because /usr/ports/infrastructure/mk/bsd.port.mk in the fix-permissions sections affects PLIST_REPOSITORY but not PLIST_DB. >How-To-Repeat: set PLIST_DB in /etc/mk.conf and then run make fix-permissions in /usr/ports. The directory permissions for PLIST_DB are not changed. But if PLIST_REPOSITORY is set in /etc/mk.conf and make fix-permissions in /usr/ports is run, the permissions are changed appropriately. >Fix: Index: share/man/man7/ports.7 === RCS file: /cvs/src/share/man/man7/ports.7,v retrieving revision 1.126 diff -u -p -u -r1.126 ports.7 --- share/man/man7/ports.7 30 May 2019 09:24:08 - 1.126 +++ share/man/man7/ports.7 16 Jun 2019 12:12:42 - @@ -641,7 +641,7 @@ Set .Ev UPDATE_COOKIES_DIR , .Ev DISTDIR , and -.Ev PLIST_DB +.Ev PLIST_REPOSITORY in .Pa /etc/mk.conf accordingly.
No networking on AR8172 with alc driver on OpenBSD 6.5 (and -current)
Hi, the AR8172 10/100/Gigabit Ethernet device isn't working despite being supported by the alc driver. dmesg : OpenBSD 6.5 (GENERIC.MP) #3: dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP alc0 at pci2 dev 0 function 0 "Attansic Technology AR8172" rev 0x10: msi, address xx:xx:xx:xx:xx:xx atphy0 at alc0 phy 0: AR8035 10/100/1000 PHY, rev. 9 alc0: watchdog timeout alc0: watchdog timeout alc0: watchdog timeout alc0: watchdog timeout alc0: watchdog timeout alc0: watchdog timeout alc0: watchdog timeout alc0: watchdog timeout alc0: watchdog timeout alc0: watchdog timeout alc0: watchdog timeout pcidump : 2:0:0: Attansic Technology AR8172 0x: Vendor ID: 1969, Product ID: 10a0 0x0004: Command: 0007, Status: 0010 0x0008: Class: 02 Network, Subclass: 00 Ethernet, Interface: 00, Revision: 10 0x000c: BIST: 00, Header Type: 00, Latency Timer: 00, Cache Line Size: 10 0x0010: BAR mem 64bit addr: 0xf010/0x0004 0x0018: BAR io addr: 0x2000/0x0080 0x001c: BAR empty () 0x0020: BAR empty () 0x0024: BAR empty () 0x0028: Cardbus CIS: 0x002c: Subsystem Vendor ID: 17aa Product ID: 3806 0x0030: Expansion ROM Base Address: 0x0038: 0x003c: Interrupt Pin: 01 Line: 00 Min Gnt: 00 Max Lat: 00 0x0040: Capability 0x01: Power Management State: D0 PME# enabled 0x0058: Capability 0x10: PCI Express Link Speed: 2.5 / 2.5 GT/s, Link Width: x1 / x1 0x0100: Enhanced Capability 0x01: Advanced Error Reporting 0x0180: Enhanced Capability 0x03: Device Serial Number 0x00c0: Capability 0x05: Message Signalled Interrupts (MSI) Enabled: yes 0x00d8: Capability 0x11: Extended Message Signalled Interrupts (MSI-X) Enabled: no; table size 16 (BAR 0:8192) ifconfig with media autoselect : alc0: flags=8843 mtu 1500 lladdr xx:xx:xx:xx:xx:xx index 1 priority 0 llprio 3 media: Ethernet autoselect (none) status: no carrier ifconfig with media manually set to 100baseTX mediaop full-duplex : alc0: flags=8843 mtu 1500 lladdr xx:xx:xx:xx:xx:xx index 1 priority 0 llprio 3 media: Ethernet autoselect (100baseTX full-duplex,rxpause,txpause) status: active dhclient alc0 : alc0: no lease. sleeping Setting a static IP does not change anything, and the ethernet device is working properly on FreeBSD 12.0.
