openbsd 63-eta and dhcpclient problem

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

openbsd 63-eta and dhcpclient problem

Holger Glaess
hi


i have here an fresh installed openbsd 6.3-beta on an samsung ultrabook
series 5

problem is the he don't get an ip address on his ethernet interface.


i see on my dhcp server the request coming and he send an offer but the
samsung diden't get it.

if i boot an simple stupid ubuntu 16.04.02 install cd , the interface
works and got an ip.

dmesg below.

there is no config for the dhclient .

bug ?


holger



OpenBSD 6.3-beta (GENERIC.MP) #44: Thu Mar  8 09:56:19 MST 2018
[hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8344485888 (7957MB)
avail mem = 8084537344 (7710MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe0840 (64 entries)
bios0: vendor Phoenix Technologies Ltd. version "P15AAJ" date 07/23/2015
bios0: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
acpi0 at bios0: rev 2
acpi0: sleep states S0 S1 S3 S4 S5
acpi0: tables DSDT FACP SLIC SSDT ASF! HPET APIC MCFG FPDT SSDT SSDT
UEFI UEFI POAT UEFI
acpi0: wakeup devices P0P1(S4) GLAN(S4) XHC_(S4) HDEF(S4) PXSX(S4)
RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4)
RP05(S4) PXSX(S4) RP06(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz, 1596.64 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
acpihpet0: recalibrated TSC frequency 1696151660 Hz
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.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz, 1596.38 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz, 1596.38 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT,MELTDOWN
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz, 1596.38 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT,MELTDOWN
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec00000, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xf8000000, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (P0P1)
acpiprt2 at acpi0: bus 1 (RP01)
acpiprt3 at acpi0: bus -1 (RP02)
acpiprt4 at acpi0: bus -1 (RP03)
acpiprt5 at acpi0: bus 2 (RP04)
acpiprt6 at acpi0: bus -1 (RP05)
acpiprt7 at acpi0: bus -1 (RP06)
acpiprt8 at acpi0: bus -1 (RP07)
acpiprt9 at acpi0: bus -1 (RP08)
acpiprt10 at acpi0: bus -1 (PEG0)
acpiprt11 at acpi0: bus -1 (PEG1)
acpiprt12 at acpi0: bus -1 (PEG2)
acpiprt13 at acpi0: bus -1 (PEG3)
acpiec0 at acpi0
acpicpu0 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10),
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10),
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10),
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10),
C1(1000@1 mwait.1), PSS
acpipwrres0 at acpi0: FN00, resource for FAN0
acpipwrres1 at acpi0: FN01, resource for FAN1
acpipwrres2 at acpi0: FN02, resource for FAN2
acpipwrres3 at acpi0: FN03, resource for FAN3
acpipwrres4 at acpi0: FN04, resource for FAN4
acpitz0 at acpi0: critical temperature is 106 degC
acpitz1 at acpi0: critical temperature is 106 degC
acpibat0 at acpi0: BAT1 type LION oem "SAMSUNG Electronics"
"INT3F0D" at acpi0 not configured
"ETD0B00" at acpi0 not configured
"PNP0C14" at acpi0 not configured
acpiac0 at acpi0: AC unit online
acpibtn0 at acpi0: LID0
acpibtn1 at acpi0: PWRB
"SAM0714" at acpi0 not configured
"INT340E" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
acpivideo0 at acpi0: GFX0
acpivout0 at acpivideo0: DD02
cpu0: Enhanced SpeedStep 1596 MHz: speeds: 1701, 1700, 1600, 1500, 1400,
1300, 1200, 1100, 1000, 900, 800, 799 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09
inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 4000" rev 0x09
drm0 at inteldrm0
inteldrm0: msi
inteldrm0: 1366x768, 32bpp
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
xhci0 at pci0 dev 20 function 0 "Intel 7 Series xHCI" rev 0x04: msi
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev
3.00/1.00 addr 1
"Intel 7 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured
ehci0 at pci0 dev 26 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int 16
usb1 at ehci0: USB revision 2.0
uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev
2.00/1.00 addr 1
azalia0 at pci0 dev 27 function 0 "Intel 7 Series HD Audio" rev 0x04: msi
azalia0: codecs: Realtek ALC269, Intel/0x2806, using Realtek ALC269
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 7 Series PCIE" rev 0xc4: msi
pci1 at ppb0 bus 1
iwn0 at pci1 dev 0 function 0 "Intel Centrino Advanced-N 6235" rev 0x24:
msi, MIMO 2T2R, AGN, address c4:85:08:c2:29:5f
ppb1 at pci0 dev 28 function 3 "Intel 7 Series PCIE" rev 0xc4: msi
pci2 at ppb1 bus 2
re0 at pci2 dev 0 function 0 "Realtek 8168" rev 0x06: RTL8168E/8111E-VL
(0x2c80), msi, address e8:03:9a:b4:f6:48
rgephy0 at re0 phy 7: RTL8169S/8110S/8211 PHY, rev. 5
ehci1 at pci0 dev 29 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int 23
usb2 at ehci1: USB revision 2.0
uhub2 at usb2 configuration 1 interface 0 "Intel EHCI root hub" rev
2.00/1.00 addr 1
pcib0 at pci0 dev 31 function 0 "Intel HM76 LPC" rev 0x04
ahci0 at pci0 dev 31 function 2 "Intel 7 Series AHCI" rev 0x04: msi,
AHCI 1.3
ahci0: port 0: 6.0Gb/s
scsibus1 at ahci0: 32 targets
sd0 at scsibus1 targ 0 lun 0: <ATA, Samsung SSD 850, EMT0> SCSI3
0/direct fixed naa.5002538d40bc2e17
sd0: 476940MB, 512 bytes/sector, 976773168 sectors, thin
ichiic0 at pci0 dev 31 function 3 "Intel 7 Series SMBus" rev 0x04: apic
2 int 18
iic0 at ichiic0
spdmem0 at iic0 addr 0x52: 4GB DDR3 SDRAM PC3-12800 SO-DIMM
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0
pms0: Elantech Touchpad, version 3, firmware 0x450f00
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
vmm0 at mainbus0: VMX/EPT
error: [drm:pid0:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch
fifo underrun on pch transcoder A
error: [drm:pid0:intel_pch_fifo_underrun_irq_handler] *ERROR* PCH
transcoder A FIFO underrun
uhub3 at uhub1 port 1 configuration 1 interface 0 "Intel Rate Matching
Hub" rev 2.00/0.00 addr 2
uvideo0 at uhub3 port 4 configuration 1 interface 0 "Generic WebCam
SC-13HDL12131N" rev 2.00/0.05 addr 3
video0 at uvideo0
uhub4 at uhub2 port 1 configuration 1 interface 0 "Intel Rate Matching
Hub" rev 2.00/0.00 addr 2
ugen0 at uhub4 port 5 "Intel product 0x07da" rev 2.00/78.69 addr 3
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
root on sd0a (7bac44119da9d8ea.a) swap on sd0b dump on sd0b


Reply | Threaded
Open this post in threaded view
|

Re: openbsd 63-eta and dhcpclient problem

Peter Hessler
please include the output of "dhclient -vv re0"


On 2018 Mar 09 (Fri) at 09:14:08 +0100 (+0100), Holger Glaess wrote:
:hi
:
:
:i have here an fresh installed openbsd 6.3-beta on an samsung ultrabook
:series 5
:
:problem is the he don't get an ip address on his ethernet interface.
:
:
:i see on my dhcp server the request coming and he send an offer but the
:samsung diden't get it.
:
:if i boot an simple stupid ubuntu 16.04.02 install cd , the interface works
:and got an ip.
:
:dmesg below.
:
:there is no config for the dhclient .
:
:bug ?
:
:
:holger
:

--
The Arkansas legislature passed a law that states that the Arkansas
River can rise no higher than to the Main Street bridge in Little
Rock.

Reply | Threaded
Open this post in threaded view
|

Re: openbsd 63-eta and dhcpclient problem

Holger Glaess
hi


~ 1>dhclient -vv re0
re0: DHCPDISCOVER - interval 1
re0: DHCPDISCOVER - interval 1
re0: DHCPDISCOVER - interval 1
re0: DHCPDISCOVER - interval 1
re0: DHCPDISCOVER - interval 1
re0: DHCPDISCOVER - interval 1
re0: DHCPDISCOVER - interval 1
re0: DHCPDISCOVER - interval 1
re0: DHCPDISCOVER - interval 1
re0: DHCPDISCOVER - interval 1
re0: no lease ... sleeping


and part of my log from the dhcp server


Mar  9 10:05:34 furt dhcpd[72447]: DHCPDISCOVER from e8:03:9a:b4:f6:48
via vlan100
Mar  9 10:05:34 furt dhcpd[72447]: DHCPOFFER on 192.168.131.101 to
e8:03:9a:b4:f6:48 via vlan100
Mar  9 10:05:35 furt dhcpd[72447]: DHCPDISCOVER from e8:03:9a:b4:f6:48
via vlan100
Mar  9 10:05:35 furt dhcpd[72447]: DHCPOFFER on 192.168.131.101 to
e8:03:9a:b4:f6:48 via vlan100
Mar  9 10:05:36 furt dhcpd[72447]: DHCPDISCOVER from e8:03:9a:b4:f6:48
via vlan100
Mar  9 10:05:36 furt dhcpd[72447]: DHCPOFFER on 192.168.131.101 to
e8:03:9a:b4:f6:48 via vlan100
Mar  9 10:05:37 furt dhcpd[72447]: DHCPDISCOVER from e8:03:9a:b4:f6:48
via vlan100
Mar  9 10:05:37 furt dhcpd[72447]: DHCPOFFER on 192.168.131.101 to
e8:03:9a:b4:f6:48 via vlan100
Mar  9 10:05:38 furt dhcpd[72447]: DHCPDISCOVER from e8:03:9a:b4:f6:48
via vlan100
Mar  9 10:05:38 furt dhcpd[72447]: DHCPOFFER on 192.168.131.101 to
e8:03:9a:b4:f6:48 via vlan100


holger



Am 09.03.2018 um 09:37 schrieb Peter Hessler:

> please include the output of "dhclient -vv re0"
>
>
> On 2018 Mar 09 (Fri) at 09:14:08 +0100 (+0100), Holger Glaess wrote:
> :hi
> :
> :
> :i have here an fresh installed openbsd 6.3-beta on an samsung ultrabook
> :series 5
> :
> :problem is the he don't get an ip address on his ethernet interface.
> :
> :
> :i see on my dhcp server the request coming and he send an offer but the
> :samsung diden't get it.
> :
> :if i boot an simple stupid ubuntu 16.04.02 install cd , the interface works
> :and got an ip.
> :
> :dmesg below.
> :
> :there is no config for the dhclient .
> :
> :bug ?
> :
> :
> :holger
> :
>

Reply | Threaded
Open this post in threaded view
|

Re: openbsd 63-eta and dhcpclient problem

Peter Hessler
Can you run "tcpdump -c100 -ni re0 port 67 or port 68", while running
dhclient?  The dhclient process doesn't see the responses from the
server, and I want to make sure they are being delivered to the network
card.


On 2018 Mar 09 (Fri) at 10:08:13 +0100 (+0100), Holger Glaess wrote:
:hi
:
:
:~ 1>dhclient -vv re0
:re0: DHCPDISCOVER - interval 1
:re0: DHCPDISCOVER - interval 1
:re0: DHCPDISCOVER - interval 1
:re0: DHCPDISCOVER - interval 1
:re0: DHCPDISCOVER - interval 1
:re0: DHCPDISCOVER - interval 1
:re0: DHCPDISCOVER - interval 1
:re0: DHCPDISCOVER - interval 1
:re0: DHCPDISCOVER - interval 1
:re0: DHCPDISCOVER - interval 1
:re0: no lease ... sleeping
:
:
:and part of my log from the dhcp server
:
:
:Mar  9 10:05:34 furt dhcpd[72447]: DHCPDISCOVER from e8:03:9a:b4:f6:48 via
:vlan100
:Mar  9 10:05:34 furt dhcpd[72447]: DHCPOFFER on 192.168.131.101 to
:e8:03:9a:b4:f6:48 via vlan100
:Mar  9 10:05:35 furt dhcpd[72447]: DHCPDISCOVER from e8:03:9a:b4:f6:48 via
:vlan100
:Mar  9 10:05:35 furt dhcpd[72447]: DHCPOFFER on 192.168.131.101 to
:e8:03:9a:b4:f6:48 via vlan100
:Mar  9 10:05:36 furt dhcpd[72447]: DHCPDISCOVER from e8:03:9a:b4:f6:48 via
:vlan100
:Mar  9 10:05:36 furt dhcpd[72447]: DHCPOFFER on 192.168.131.101 to
:e8:03:9a:b4:f6:48 via vlan100
:Mar  9 10:05:37 furt dhcpd[72447]: DHCPDISCOVER from e8:03:9a:b4:f6:48 via
:vlan100
:Mar  9 10:05:37 furt dhcpd[72447]: DHCPOFFER on 192.168.131.101 to
:e8:03:9a:b4:f6:48 via vlan100
:Mar  9 10:05:38 furt dhcpd[72447]: DHCPDISCOVER from e8:03:9a:b4:f6:48 via
:vlan100
:Mar  9 10:05:38 furt dhcpd[72447]: DHCPOFFER on 192.168.131.101 to
:e8:03:9a:b4:f6:48 via vlan100
:
:
:holger
:
:
:
:Am 09.03.2018 um 09:37 schrieb Peter Hessler:
:> please include the output of "dhclient -vv re0"
:>
:>
:> On 2018 Mar 09 (Fri) at 09:14:08 +0100 (+0100), Holger Glaess wrote:
:> :hi
:> :
:> :
:> :i have here an fresh installed openbsd 6.3-beta on an samsung ultrabook
:> :series 5
:> :
:> :problem is the he don't get an ip address on his ethernet interface.
:> :
:> :
:> :i see on my dhcp server the request coming and he send an offer but the
:> :samsung diden't get it.
:> :
:> :if i boot an simple stupid ubuntu 16.04.02 install cd , the interface works
:> :and got an ip.
:> :
:> :dmesg below.
:> :
:> :there is no config for the dhclient .
:> :
:> :bug ?
:> :
:> :
:> :holger
:> :
:>
:

--
So far as I can remember, there is not one word in the Gospels in
praise of intelligence.
                -- Bertrand Russell

Reply | Threaded
Open this post in threaded view
|

Re: openbsd 63-eta and dhcpclient problem

Holger Glaess
hi


strange

i did the test again with booting the ubuntu cd , then i reboot to
openbsd 6.3

since this time dhcp on re works . i did also an complete poweroff and

reboot direkt to openbsd is works now ..... i dont  know why .

i start to have this problem with an current version 6.2 from feb .2018 but
i dident care about it , i think the interface is broken .

today i try the linux , first and wonder why is ethernet working.

did you need the tcpdump farther ?

holger



Am 09.03.2018 um 10:22 schrieb Peter Hessler:
> tcpdump -c100 -ni re0 port 67 or port 6

Reply | Threaded
Open this post in threaded view
|

Re: openbsd 63-eta and dhcpclient problem

Peter Hessler
No need for the tcdump any more.  I wanted to see if you were receiving
the packets or not. If you're getting a lease, then clearly you're now
receiving the packets.


On 2018 Mar 09 (Fri) at 11:06:43 +0100 (+0100), Holger Glaess wrote:
:hi
:
:
:strange
:
:i did the test again with booting the ubuntu cd , then i reboot to openbsd
:6.3
:
:since this time dhcp on re works . i did also an complete poweroff and
:
:reboot direkt to openbsd is works now ..... i dont  know why .
:
:i start to have this problem with an current version 6.2 from feb .2018 but
:i dident care about it , i think the interface is broken .
:
:today i try the linux , first and wonder why is ethernet working.
:
:did you need the tcpdump farther ?
:
:holger
:
:
:
:Am 09.03.2018 um 10:22 schrieb Peter Hessler:
:> tcpdump -c100 -ni re0 port 67 or port 6
:

--
Miksch's Law:
        If a string has one end, then it has another end.

Reply | Threaded
Open this post in threaded view
|

Re: openbsd 63-eta and dhcpclient problem

Holger Glaess
hi


the problem is not gone.


i left the computer for a couple of hours ,then i try to work with hin
but he lost the

connection .


i saw tine re interface with an ip and the outgoing dhcp request by
tcpdump .

but he is not able to cumunicatate through ethernet.

i reboot the system , nothing work but he set the ip from the lease db
of the dhclient

i delete thies and reboot again , nothing.


next i reboot the linux , ethernet work

then i reboot back to openbsd ethernet work !

i can do an connect , for example , ssh to an other system


there is something wrong .

holger




Am 09.03.2018 um 11:39 schrieb Peter Hessler:

> No need for the tcdump any more.  I wanted to see if you were receiving
> the packets or not. If you're getting a lease, then clearly you're now
> receiving the packets.
>
>
> On 2018 Mar 09 (Fri) at 11:06:43 +0100 (+0100), Holger Glaess wrote:
> :hi
> :
> :
> :strange
> :
> :i did the test again with booting the ubuntu cd , then i reboot to openbsd
> :6.3
> :
> :since this time dhcp on re works . i did also an complete poweroff and
> :
> :reboot direkt to openbsd is works now ..... i dont  know why .
> :
> :i start to have this problem with an current version 6.2 from feb .2018 but
> :i dident care about it , i think the interface is broken .
> :
> :today i try the linux , first and wonder why is ethernet working.
> :
> :did you need the tcpdump farther ?
> :
> :holger
> :
> :
> :
> :Am 09.03.2018 um 10:22 schrieb Peter Hessler:
> :> tcpdump -c100 -ni re0 port 67 or port 6
> :
>

Reply | Threaded
Open this post in threaded view
|

Re: openbsd 63-eta and dhcpclient problem

Stuart Henderson
On 2018-03-09, Holger Glaess <[hidden email]> wrote:

> hi
>
>
> the problem is not gone.
>
>
> i left the computer for a couple of hours ,then i try to work with hin
> but he lost the
>
> connection .
>
>
> i saw tine re interface with an ip and the outgoing dhcp request by
> tcpdump .
>
> but he is not able to cumunicatate through ethernet.
>
> i reboot the system , nothing work but he set the ip from the lease db
> of the dhclient
>
> i delete thies and reboot again , nothing.
>
>
> next i reboot the linux , ethernet work
>
> then i reboot back to openbsd ethernet work !
>
> i can do an connect , for example , ssh to an other system
>
>
> there is something wrong .

I would suggest:

- Save pcidump -vvxx to a file when it's broken

- Check tcpdump on the OpenBSD system with the problem and see if it
is RECEIVING anything from the network

- If you can run tcpdump on the DHCP server, do that as well (while you
run dhclient), see if it can hear anything the OpenBSD system is SENDING
on the network

- Boot to Linux and back again to hopefully fix it

- Save pcidump -vvxx to a different file when it's working

- Run "sendbug -P > somefile" as root on the machine where you're having
problems to get a report template which will include pcidump, b64-encoded
acpi files and dmesg. Edit and fill in a description of the problem, as
clear as you can. Include a diff of the two pcidump output files. Read
through again and check that it makes sense on its own then send to bugs@.