Re: dhclient question
kwesterb...@gmail.com (Kenneth Westerback), 2014.06.23 (Mon) 18:53 (CEST): On 23 June 2014 06:24, Avi Cohen av...@rad.com wrote: In my application (it is a router in the access) I'm initially running dhclient daemon without any interface specified for dhcp. Then - on user request - we add interfaces to dhclient.conf on run-time I have 3 questions - that I'll appreciate if you can answer You can read dhclient(8) and dhclient.conf(5) man pages for details. But to summarize ... (You seem to ask 4 questions, so which one will you not appreciate an answer to? :-)) 1. Is it possible to append interfaces to an existing dhclient.conf ? or just to add a new (for example) dhclient.conf-eth1? [BTW - where to locate this file ?] You can append as many 'interface' statements as you like in the dhclient.conf file. If you want to run with a separate config file for a particular instance of dhclient you can use the '-c' option to specify the non-default file. 2.When the daemon will start the dhcp-request for this new interface ? When you start it. Every interface's dhclient must be started separately. If you start a dhclient without specifying the interface it attempts to find an interface in the 'egress' group. If there is one and only one such interface then dhclient will use it. For other interfaces you must start other instances of dhclient, usually by creating a /etc/hostname.if file for that interface. The /etc/hostname.if file will be used at system startup or you can 'sh /etc/netstart if' as root. 3. Our application need to be informed whenever a new IP-address (dhcp) is assigned for the interface. How to do it ? by polling the dhclient.leases ? is there a notification from dhclient to our application that we can use ? The best way to do that is with a program that monitors the routing socket, where you can see all address changes. hint: route(8) monitor Bye, Marcus Alternatively you can monitor the leases file or use the '-L' option to write out the offered and effective lease information if you want complete information on what is being received and used. Some people use the entr port (/usr/ports/sysutils/entr, http://entrproject.org/) to monitor the file(s). 4. 4 - if I start the dhclient daemon without interface specified - I see that it sends dhcp-request for all my exiting interfaces ? why ? how to disable this behavior and to send request for only Specified interfaces ? (but without specifying it in the command line- but via dhclient.conf ? Now you make me doubt you are running OpenBSD. Our dhclient does not send dhcp-request for all interfaces -- it sends dhcp-requests out one and only one interface. At least for the last 10 years or more. You must specify the interface via the command line, or have the /etc/netstart command build the command line for you from a hostname.if file. Ken Regards, Avi !DSPAM:53a85bed101242941456129!
Re: Pflow granularity
2014-06-04 16:37 GMT+02:00 Stuart Henderson s...@spacehopper.org: On 2014-06-02, Andy a...@brandwatch.com wrote: I think you might have to try softflowd instead of the built-in sflowd.. These guys had the same problem and moved to softflowd to allow them to analyse DDOS traffic with netflow.. https://ripe68.ripe.net/presentations/276-DDoS.pdf see also the video from UKNOF28, though my understanding was that a big part of the reason for softflowd was to capture stats from blocked packets. I noticed the same problems in my reports Why this diff was not imported ? http://marc.info/?l=openbsd-miscm=124661838923498w=2 After all, that was a great idea.
Re: Pflow granularity
Tristan PILAT(tristan.pi...@gmail.com) on 2014.06.24 11:04:35 +0200: 2014-06-04 16:37 GMT+02:00 Stuart Henderson s...@spacehopper.org: On 2014-06-02, Andy a...@brandwatch.com wrote: I think you might have to try softflowd instead of the built-in sflowd.. These guys had the same problem and moved to softflowd to allow them to analyse DDOS traffic with netflow.. https://ripe68.ripe.net/presentations/276-DDoS.pdf see also the video from UKNOF28, though my understanding was that a big part of the reason for softflowd was to capture stats from blocked packets. I noticed the same problems in my reports Why this diff was not imported ? you'll have to ask joerg. :) however right now some people are working on something similar.
Re: Pflow granularity
2014-06-24 13:50 GMT+02:00 Sebastian Benoit benoit-li...@fb12.de: Tristan PILAT(tristan.pi...@gmail.com) on 2014.06.24 11:04:35 +0200: I noticed the same problems in my reports Why this diff was not imported ? you'll have to ask joerg. :) however right now some people are working on something similar. Very happy to read that :) Looking forward to know more about that.
Re: LAN vs VLAN interface performance
On 23/06/14 21:33, Henning Brauer wrote: * Chris Cappuccio ch...@nmedia.net [2014-06-23 20:24]: I have a sandy bridge Xeon box with PF NAT that handles a daily 200 to 700Mbps. It has a single myx interface using OpenBSD 5.5 (not current). It does nothing but PF NAT and related routing. No barage of vlans or interfaces. No dynamic routing. Nothing else. 60,000 to 100,000 states. With an MP kernel, kern.netlivelocks increases by something like 150,000 per day!! I The packet loss was notable. With an SP kernel, the 'netlivelock' counter barely moves. Maybe 100 per day on average, but for the past week, maybe 5. as already said in private, I'm not seeing anything like that which makes me wonder what is different for you. Me neither # uname -a OpenBSD server 5.5 GENERIC.MP#156 i386 sysctl -a|grep netlive kern.netlivelocks=50 # pfctl -ss|wc -l 73203 # pfctl -sr|wc -l 294 routing/firewalling/some NAT at ~ 500Mbps G
Portafolios de Inversion, Riesgos Financieros.
**PRIVACIDAD DE ESTE MENSAJE** Este mensaje esta dirigido exclusivamente a las personas que tienen las direcciones de correo electronico especificadas en los destinatarios dentro de su encabezado. Si por error usted ha recibido este mensaje, por ningun motivo debe revelar su contenido, copiarlo, distribuirlo o utilizarlo. Le solicitamos por favor comunique del error a la direccion de correo electronico remitente y elimine dicho mensaje junto con cualquier documento adjunto que pudiera contener. Los derechos de privacidad y confidencialidad de la informacion en este mensaje no deben perderse por el hecho de haberse trasmitido erroneamente o por causas de interferencias en el funcionamiento de los sistemas de correo y canales de comunicacion. este mensaje no es considerado spam puesto que tiene la facilidad de dar de baja para dar de baja da click aqui
Suspend does not work
Hello, so on my desktop workstation the suspend (zzz) does not work. It goes into sleep but as soon as i resume (with the power button, keyboard or mouse doesn't do anything) the X server comes back up but i cant see the mouse or do any keyboard inputs. The numlock LED can be switched on/off though. The same happens in console mode without X being started. This also happens with the radeon card being physically removed from the system. any help appreciated. i would also provide more information if needed. Specs: i5 2400 Asrock z68 pro3 ati radeon hd7770 dmesg for my systems comes here: OpenBSD 5.5-current (GENERIC.MP) #223: Fri Jun 20 22:44:51 MDT 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8459096064 (8067MB) avail mem = 8225140736 (7844MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xef370 (26 entries) bios0: vendor American Megatrends Inc. version P2.10 date 05/07/2012 bios0: ASRock Z68 Pro3 acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP APIC ASF! MCFG AAFT HPET SSDT SSDT SSDT BGRT acpi0: wakeup devices CIR_(S3) PS2K(S4) PS2M(S4) UAR1(S4) P0P1(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) USB6(S3) USB7(S3) RP01(S4) RP02(S4) RP03(S4) RP04(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) Core(TM) i5-2400 CPU @ 3.10GHz, 3093.41 MHz cpu0: FPU,VME,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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.0, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz, 3092.97 MHz cpu1: FPU,VME,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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz, 3092.97 MHz cpu2: FPU,VME,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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz, 3092.97 MHz cpu3: FPU,VME,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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P1) acpiprt2 at acpi0: bus 2 (RP01) acpiprt3 at acpi0: bus -1 (RP02) acpiprt4 at acpi0: bus -1 (RP03) acpiprt5 at acpi0: bus -1 (RP04) acpiprt6 at acpi0: bus 3 (RP05) acpiprt7 at acpi0: bus 4 (PE2P) acpiprt8 at acpi0: bus 5 (RP06) acpiprt9 at acpi0: bus 6 (RP07) acpiprt10 at acpi0: bus -1 (RP08) acpiprt11 at acpi0: bus 1 (PEG0) acpiprt12 at acpi0: bus -1 (PEG1) acpiprt13 at acpi0: bus -1 (PEG2) acpiprt14 at acpi0: bus -1 (PEG3) acpiec0 at acpi0: Failed to read resource settings acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpicpu2 at acpi0: C3, C2, C1, PSS acpicpu3 at acpi0: C3, C2, C1, PSS acpibat0 at acpi0: BAT0 not present acpibat1 at acpi0: BAT1 not present acpibat2 at acpi0: BAT2 not present acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: LID0 acpivideo0 at acpi0: GFX0 acpivout0 at acpivideo0: DD02 cpu0: Enhanced SpeedStep 3093 MHz: speeds: 3101, 3100, 3000, 2900, 2800, 2700, 2600, 2500, 2300, 2200, 2100, 2000, 1900, 1800, 1700, 1600 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel Core 2G Host rev 0x09 ppb0 at pci0 dev 1 function 0 Intel Core 2G PCIE rev 0x09: msi pci1 at ppb0 bus 1 radeondrm0 at pci1 dev 0 function 0 ATI Radeon HD 7770 rev 0x00 drm0 at radeondrm0 radeondrm0: msi azalia0 at pci1 dev 0 function 1 vendor ATI, unknown product 0xaab0 rev 0x00: msi azalia0: no supported codecs Intel HD Graphics 2000 rev 0x09 at pci0 dev 2 function 0 not configured Intel 6 Series MEI rev
PXE auto_install
Hi, The new OpenBSD auto_install with PXE works like a charm and just have 2 questions regarding the install.conf file I did not manage to find out yet: 1) how can I install the bsd.mp instead of the standard bsd image? 2) how can I custom partition my disk (I would like 1 partition for root and one for swap) ? Regards ML
Re: PXE auto_install
On 24 June 2014 11:10, ML mail mlnos...@yahoo.com wrote: Hi, The new OpenBSD auto_install with PXE works like a charm and just have 2 questions regarding the install.conf file I did not manage to find out yet: 1) how can I install the bsd.mp instead of the standard bsd image? bsd.mp should be copied and used by default on systems with 1 CPU. There is no way I know of to force bsd.mp to be used on uniprocessor systems, although it can be copied to the target system. 2) how can I custom partition my disk (I would like 1 partition for root and one for swap) ? At the moment you can't. Ken Regards ML
Re: dhclient question
On 2014-06-23, Kenneth Westerback kwesterb...@gmail.com wrote:
Alternatively you can monitor the leases file or use the '-L' option
to write out the offered and effective lease information if you want
complete information on what is being received and used. Some people
use the entr port (/usr/ports/sysutils/entr, http://entrproject.org/)
to monitor the file(s).
FWIW, I'm doing this to monitor nameserver changes, here's an example.
Note that it relies on support that was added to dhclient post-5.5.
(entr is from packages; it's a nice simple kqueue watcher, so it
works by a trigger when the file is changed, rather than needing to
poll it periodically).
$ cat /etc/dhcp-watcher
#!/bin/sh
gw=$(route -n get -inet 0.0.0.0 | awk '/interface/ {print $2}')
dns=$(awk '/domain-name-servers/ {gsub([;,], , $3); print $3;}'
/etc/dhclient.lease.$gw)
unbound-control forward_add . $dns /dev/null
echo default now on $gw: $(unbound-control list_forwards) | logger -t
dhcp-watcher
$ cat /etc/dhcp-watcher.run
#!/bin/sh
/etc/dhcp-watcher
echo /etc/dhclient.lease.* | tr ' ' '\n' | entr /etc/dhcp-watcher
$ cat /etc/hostname.em0
up -autoconfprivacy
!dhclient -L /etc/dhclient.lease.em0 em0
rtsol
$ cat /etc/hostname.iwn0
nwid rarara wpakey ackackmacaque wpaprotos wpa2 wpaciphers ccmp
!dhclient -L /etc/dhclient.lease.iwn0 iwn0
rtsol
Re: PXE auto_install
On Tue, Jun 24, 2014 at 08:10:59AM -0700, ML mail wrote:
Hi,
The new OpenBSD auto_install with PXE works like a charm and just have 2
questions regarding the install.conf file I did not manage to find out yet:
1) how can I install the bsd.mp instead of the standard bsd image?
2) how can I custom partition my disk (I would like 1 partition for root and
one for swap) ?
Regards
ML
2 - ugly hack, not tested yet.
j.
This would allow to get customized install.md where one can define
md_prep_fdisk() and/or md_prep_disklabel() functions.
Index: install.sub
===
RCS file: /cvs/src/distrib/miniroot/install.sub,v
retrieving revision 1.775
diff -u -p -r1.775 install.sub
--- install.sub 9 Jun 2014 18:05:55 - 1.775
+++ install.sub 19 Jun 2014 22:07:39 -
@@ -2134,6 +2134,14 @@ get_responsefile() {
ftp -o /$_mode.conf http://$_server/$_f.conf;
action=$_mode return 0
done
+ if [[ $_mode = install ]]; then
+ for _f in {$_mac-,}install; do
+ ftp -o /install.md http://$_server/$_f.md; \
+action=$_mode \
+. install.md \
+return 0
+done
+fi
fi
# No response file found
Re: LAN vs VLAN interface performance
Kapetanakis Giannis [bil...@edu.physics.uoc.gr] wrote: On 23/06/14 21:33, Henning Brauer wrote: * Chris Cappuccio ch...@nmedia.net [2014-06-23 20:24]: I have a sandy bridge Xeon box with PF NAT that handles a daily 200 to 700Mbps. It has a single myx interface using OpenBSD 5.5 (not current). It does nothing but PF NAT and related routing. No barage of vlans or interfaces. No dynamic routing. Nothing else. 60,000 to 100,000 states. With an MP kernel, kern.netlivelocks increases by something like 150,000 per day!! I The packet loss was notable. With an SP kernel, the 'netlivelock' counter barely moves. Maybe 100 per day on average, but for the past week, maybe 5. as already said in private, I'm not seeing anything like that which makes me wonder what is different for you. Me neither # uname -a OpenBSD server 5.5 GENERIC.MP#156 i386 I'm using amd64... sysctl -a|grep netlive kern.netlivelocks=50 # pfctl -ss|wc -l 73203 # pfctl -sr|wc -l 294 routing/firewalling/some NAT at ~ 500Mbps I have some ideas. I'm going to do some troubleshooting when I have a chance to think clearly. I think the disk subsystem could be part of the issue. I see the most netlivelocks on a box with a USB key, mfi is in second place.
Re: LAN vs VLAN interface performance
On 24/06/14 3:08 PM, Chris Cappuccio wrote: Kapetanakis Giannis [bil...@edu.physics.uoc.gr] wrote: On 23/06/14 21:33, Henning Brauer wrote: * Chris Cappuccio ch...@nmedia.net [2014-06-23 20:24]: I have a sandy bridge Xeon box with PF NAT that handles a daily 200 to 700Mbps. It has a single myx interface using OpenBSD 5.5 (not current). It does nothing but PF NAT and related routing. No barage of vlans or interfaces. No dynamic routing. Nothing else. 60,000 to 100,000 states. With an MP kernel, kern.netlivelocks increases by something like 150,000 per day!! I The packet loss was notable. With an SP kernel, the 'netlivelock' counter barely moves. Maybe 100 per day on average, but for the past week, maybe 5. as already said in private, I'm not seeing anything like that which makes me wonder what is different for you. Me neither # uname -a OpenBSD server 5.5 GENERIC.MP#156 i386 I'm using amd64... sysctl -a|grep netlive kern.netlivelocks=50 # pfctl -ss|wc -l 73203 # pfctl -sr|wc -l 294 routing/firewalling/some NAT at ~ 500Mbps I have some ideas. I'm going to do some troubleshooting when I have a chance to think clearly. I think the disk subsystem could be part of the issue. I see the most netlivelocks on a box with a USB key, mfi is in second place. This reminds me of a system I had mentioned to you in the past. Checking that system again I noticed since switching it from spinning rust to SSDs that the number of livelocks seems to have gone down. # sysctl -a | grep livelocks kern.netlivelocks=4163 # uptime 3:23PM up 1 day, 45 mins, 1 user, load averages: 0.79, 0.91, 0.83 # sysctl -a | grep livelocks kern.netlivelocks=4190 # uptime 3:37PM up 1 day, 59 mins, 1 user, load averages: 0.67, 0.99, 0.87 Before the switch that would be up into the tens of thousands by now. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
fxp driver - bsd.rd vs bsd
Hi, My colleague is after trying to install Current onto an old Dell PC several times now. -She can go through the install without problem, she gets connected with dhcp and can download the filesets, so obviously she has network connection. -However, after rebooting into the freshly installed system (still set to dhcp), the machine will just not appear on the network. -While it was installing it could be pinged, but as soon as it restarts into the installed Current, it will not reply to ping anymore, it is not accessible over ssh and it is impossible to connect from it as well. -ifconfig fxp0 tells me that the state is active and it appears to have kept the same ip-address as it had when it was being installed. -Cables have been changed and it was connected to ports on other switches to no avail. -I was just wondering what would be the difference between being booted into bsd.rd vs bsd - in the latter fxp seems to have some kind of issue while it is working fine while in install-mode?-We will work around this issue by using a different machine, but I am still curious, how come it works fine while installing, but not when it is actually installed? Any clue-sticks to hit me with? Cheers
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
Stuart Henderson [s...@spacehopper.org] wrote: On 2014-06-20, Roger Wiklund roger.wikl...@gmail.com wrote: On a side note I'm a bit worried about the CPU temperate, almost 70 degrees C during normal load. Yes. Someone, make a better chassis for these, please...! A low rpm fan would be quite acceptable to me and I think would make a huge difference. You know thermal headroom is tight when the vendor goes as far as telling you to use a black chassis. Pascal Dornier says that consistent pressure between the CPU and heat spreader is critical. He also says the colored cases have better emissivity: http://pcengines.ch/apucool.htm Some emissivity tests: http://snap.fnal.gov/crshield/crs-mech/emissivity-eoi.html More cooling surface area here (but not colored): http://linitx.com/viewproduct.php?prodid=12745
Re: fxp driver - bsd.rd vs bsd
On Tue, Jun 24, 2014 at 03:47:27PM -0400, Stefan Olsson wrote: Hi, My colleague is after trying to install Current onto an old Dell PC several times now. -She can go through the install without problem, she gets connected with dhcp and can download the filesets, so obviously she has network connection. -However, after rebooting into the freshly installed system (still set to dhcp), the machine will just not appear on the network. -While it was installing it could be pinged, but as soon as it restarts into the installed Current, it will not reply to ping anymore, it is not accessible over ssh and it is impossible to connect from it as well. -ifconfig fxp0 tells me that the state is active and it appears to have kept the same ip-address as it had when it was being installed. -Cables have been changed and it was connected to ports on other switches to no avail. -I was just wondering what would be the difference between being booted into bsd.rd vs bsd - in the latter fxp seems to have some kind of issue while it is working fine while in install-mode?-We will work around this issue by using a different machine, but I am still curious, how come it works fine while installing, but not when it is actually installed? Any clue-sticks to hit me with? Cheers The GENERIC kernel loads firmware patches into some fxp models. Perhaps your fxp model doesn't like that? To test this theory, try removing the call to fxp_load_ucode() in ftp_init() in the file /usr/src/sys/dev/ic/fxp.c and recompile the GENERIC kernel. If that makes it work please supply the output of pcidump -v and dmesg so a proper fix can be devised. Index: fxp.c === RCS file: /cvs/src/sys/dev/ic/fxp.c,v retrieving revision 1.115 diff -u -p -r1.115 fxp.c --- fxp.c 28 Dec 2013 03:34:59 - 1.115 +++ fxp.c 24 Jun 2014 21:06:31 - @@ -1193,7 +1193,6 @@ fxp_init(void *xsc) fxp_scb_cmd(sc, FXP_SCB_COMMAND_RU_BASE); #ifndef SMALL_KERNEL - fxp_load_ucode(sc); #endif /* Once through to set flags */ fxp_mc_setup(sc, 0);
Re: fxp driver - bsd.rd vs bsd
previously on this list Stefan Olsson contributed: However, after rebooting into the freshly installed system (still set to dhcp), the machine will just not appear on the network. -While it was installing it could be pinged I don't really use DHCP but believe there are various types. On Android it bypasses the filter all together. You could make sure logging is enabled in pf.conf and see what the following shows tcpdump -n -e -ttt -i pflog0 -- ___ 'Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface' (Doug McIlroy) In Other Words - Don't design like polkit or systemd ___
Re: fxp driver - bsd.rd vs bsd
Subject: Re: fxp driver - bsd.rd vs bsdFrom: andres@msu.eduDate: Tue, 24 Jun 2014 17:43:57 -0400To: stur...@hotmail.com; misc@openbsd.org First guess is do you have /etc/mygate ? --STeve Andre' -It doesn't really matter if I have mygate or not as this is on the LAN, no routing involved. It works fine to ping from other hosts on the LAN while it is installing (after getting an address from dhcp), but it doesn't reply to ping after rebooting to the *fresh* install of current.
Re: fxp driver - bsd.rd vs bsd
First guess is do you have /etc/mygate ? --STeve Andre' On June 24, 2014 3:47:27 PM EDT, Stefan Olsson stur...@hotmail.com wrote: Hi, My colleague is after trying to install Current onto an old Dell PC several times now. -She can go through the install without problem, she gets connected with dhcp and can download the filesets, so obviously she has network connection. -However, after rebooting into the freshly installed system (still set to dhcp), the machine will just not appear on the network. -While it was installing it could be pinged, but as soon as it restarts into the installed Current, it will not reply to ping anymore, it is not accessible over ssh and it is impossible to connect from it as well. -ifconfig fxp0 tells me that the state is active and it appears to have kept the same ip-address as it had when it was being installed. -Cables have been changed and it was connected to ports on other switches to no avail. -I was just wondering what would be the difference between being booted into bsd.rd vs bsd - in the latter fxp seems to have some kind of issue while it is working fine while in install-mode?-We will work around this issue by using a different machine, but I am still curious, how come it works fine while installing, but not when it is actually installed? Any clue-sticks to hit me with? Cheers
Thanks for ACPI
Works brilliantly on my core i3 Dell inspiron laptop. It's funny to me that NO power saving features work in Windows 8, nor 2 finger scrolling on the trackpad. OpenBSD Just Works(tm). Surprise, surprise, surprise Anyway, thanks! -Noah
Re: Thanks for ACPI
It's funny to me that NO power saving features work in Windows 8, nor 2 finger scrolling on the trackpad. It's a funny world, here's how, let me explain the road map for you: In 1 year, Windows will work worse on that particular laptop. In 2 years, it will be expired. In 4 years, it will barely work. That is a result of chasing new sales. In 1 year, OpenBSD will work better on that laptop. In 2 years, it will be work even better. In about 4 years, it will work as well, but the decline will start because our developers will move on. That is an aspect of minimal refinement, not chasing the curve. In 1 year, Linux might work better. In 2 years, it will not work well. But hey, don't take my word for me. Ask the net. They'll set me straight, and they'll set you straight. I don't know what they are chasing. Maybe it is the same as the first. Really, honestly, I don't have a clue what they are chasing.
Re: Thanks for ACPI
Hello all, just to add that its true !!! In my notebook also ACPI and two finger its working perfectly. Theo the way you define windows, linux and openbsd is brilliant. I will pass these words to my work colleagues =) Thank you for doing what you do. Its simply working !!! And simpler that the other OSes Saludos.- Leonardo Santagostini http://ar.linkedin.com/in/santagostini 2014-06-24 22:14 GMT-03:00 Theo de Raadt dera...@cvs.openbsd.org: It's funny to me that NO power saving features work in Windows 8, nor 2 finger scrolling on the trackpad. It's a funny world, here's how, let me explain the road map for you: In 1 year, Windows will work worse on that particular laptop. In 2 years, it will be expired. In 4 years, it will barely work. That is a result of chasing new sales. In 1 year, OpenBSD will work better on that laptop. In 2 years, it will be work even better. In about 4 years, it will work as well, but the decline will start because our developers will move on. That is an aspect of minimal refinement, not chasing the curve. In 1 year, Linux might work better. In 2 years, it will not work well. But hey, don't take my word for me. Ask the net. They'll set me straight, and they'll set you straight. I don't know what they are chasing. Maybe it is the same as the first. Really, honestly, I don't have a clue what they are chasing.
