Re: DHCP question
On Fri, Jul 25, 2008 at 6:07 PM, Henning Brauer [EMAIL PROTECTED] wrote: if that still doesn't work... after install, at the boot prompt, do boot -c, and the the upcoming UKC prompt do a disable acpi followed by quit once the system is running send dmesgs with and without acpi and acpidump output (forgot exact instructions, ask list archives) to marco@ and jordan@ openbsd.org Henning Brauer Hello. Apologies for the relatively late reply. I was kinda hoping that OpenBSD would run OOTB on this. However, from the looks of it, might take sometime to get it working. Since our team is on a clock, I got 4.3 CD working on another computer without any problems. Everything works OOTB and we have set that up for our needs. As and when time permits, I shall try and follow up on this network problem. As an aside, would a different NIC solve this problem? Hari
Re: DHCP question
* Hari [EMAIL PROTECTED] [2008-07-29 02:52]: problem. As an aside, would a different NIC solve this problem? no. you have interrupt routing problems. -- Henning Brauer, [EMAIL PROTECTED], [EMAIL PROTECTED] BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting - Hamburg Amsterdam
Re: DHCP question
fxp0: warning: SCB timed out (x 3) fxp0: config command timeout - Forwarded message from Hari [EMAIL PROTECTED] - From: Hari [EMAIL PROTECTED] Date: Fri, 25 Jul 2008 09:46:28 +0900 To: Stuart Henderson [EMAIL PROTECTED] Subject: Re: DHCP question On Thu, Jul 24, 2008 at 7:31 PM, Stuart Henderson [EMAIL PROTECTED] wrote: misc@ doesn't take attachments, those need to be inline Thought as much...apologies. Here are the dmesgs for the virgin system. bsd.rd: begin OpenBSD 4.4-beta (RAMDISK_CD) #824: Tue Jul 22 18:29:32 MDT 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD cpu0: Intel(R) Celeron(R) CPU 2.66GHz (GenuineIntel 686-class) 2.67 GHz cpu0: FPU,V86,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,SBF,SSE3,MWAIT,DS-CPL,TM2,CNXT-ID,CX16,xTPR real mem = 526516224 (502MB) avail mem = 502517760 (479MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 11/02/05, BIOS32 rev. 0 @ 0xffe90, SMBIOS rev. 2.3 @ 0xf0450 (62 entries) bios0: vendor Dell Inc. version A01 date 11/02/2005 bios0: Dell Inc. Dell DC051 apm0 at bios0: Power Management spec V1.2 acpi at bios0 function 0x0 not configured pcibios0 at bios0: rev 2.1 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfeb00/240 (13 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82801FB LPC rev 0x00) pcibios0: PCI bus #3 is the last bus bios0: ROM list: 0xc/0xa800! 0xca800/0x1800! cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82915G Host rev 0x04 vga1 at pci0 dev 2 function 0 Intel 82915G Video rev 0x04 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) Intel 82801FB HD Audio rev 0x04 at pci0 dev 27 function 0 not configured ppb0 at pci0 dev 28 function 0 Intel 82801FB PCIE rev 0x04: irq 11 pci1 at ppb0 bus 1 ppb1 at pci0 dev 28 function 1 Intel 82801FB PCIE rev 0x04 pci2 at ppb1 bus 2 uhci0 at pci0 dev 29 function 0 Intel 82801FB USB rev 0x04: irq 9 uhci1 at pci0 dev 29 function 1 Intel 82801FB USB rev 0x04: irq 5 uhci2 at pci0 dev 29 function 2 Intel 82801FB USB rev 0x04: irq 4 uhci3 at pci0 dev 29 function 3 Intel 82801FB USB rev 0x04: irq 3 ehci0 at pci0 dev 29 function 7 Intel 82801FB USB rev 0x04: irq 9 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb2 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0xd4 pci3 at ppb2 bus 3 fxp0 at pci3 dev 8 function 0 Intel 82801FB LAN rev 0x04, i82562: irq 10, address 00:16:76:13:ad:54 inphy0 at fxp0 phy 1: i82562G 10/100 PHY, rev. 0 ichpcib0 at pci0 dev 31 function 0 Intel 82801FB LPC rev 0x04: PM disabled pciide0 at pci0 dev 31 function 1 Intel 82801FB IDE rev 0x04: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility atapiscsi0 at pciide0 channel 0 drive 0 scsibus0 at atapiscsi0: 2 targets, initiator 7 cd0 at scsibus0 targ 0 lun 0: TSSTcorp, CDRWDVD TS-H492C, DE02 ATAPI 5/cdrom removable cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 pciide0: channel 1 ignored (disabled) pciide1 at pci0 dev 31 function 2 Intel 82801FB SATA rev 0x04: DMA, channel 0 configured to native-PCI, channel 1 configured to native-PCI pciide1: using irq 10 for native-PCI interrupt wd0 at pciide1 channel 0 drive 0: WDC WD800JD-75MSA1 wd0: 16-sector PIO, LBA48, 76293MB, 15625 sectors wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5 Intel 82801FB SMBus rev 0x04 at pci0 dev 31 function 3 not configured usb1 at uhci0: USB revision 1.0 uhub1 at usb1 Intel UHCI root hub rev 1.00/1.00 addr 1 usb2 at uhci1: USB revision 1.0 uhub2 at usb2 Intel UHCI root hub rev 1.00/1.00 addr 1 usb3 at uhci2: USB revision 1.0 uhub3 at usb3 Intel UHCI root hub rev 1.00/1.00 addr 1 usb4 at uhci3: USB revision 1.0 uhub4 at usb4 Intel UHCI root hub rev 1.00/1.00 addr 1 isa0 at ichpcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 biomask f7fd netmask f7fd ttymask rd0: fixed, 3800 blocks uhidev0 at uhub1 port 1 configuration 1 interface 0 vendor 0x0461 USB Optical Mouse rev 2.00/2.00 addr 2 uhidev0: iclass 3/1 uhid at uhidev0 not configured uhidev1 at uhub1 port 2 configuration 1 interface 0 Dell Dell USB Keyboard rev 1.10/2.00 addr 3 uhidev1: iclass 3/1 ukbd0 at uhidev1 wskbd1 at ukbd0 mux 1 wskbd1: connecting to wsdisplay0 softraid0 at root root on rd0a swap on rd0b dump on rd0b umass0 at uhub0 port 5 configuration 1 interface 0 BUFFALO USB Flash Disk rev 2.00/40.00 addr 2 umass0: using SCSI over Bulk-Only scsibus1 at umass0: 2 targets, initiator 0 sd0 at scsibus1 targ 1 lun 0: BUFFALO, USB Flash Disk, 4000 SCSI0 0/direct removable sd0: 1920MB, 244 cyl, 255 head, 63 sec, 512 bytes/sec, 3932160 sec total end bsd: begin OpenBSD 4.4-beta (GENERIC) #985: Tue Jul 22 18:14:49 MDT 2008 [EMAIL PROTECTED]:/usr/src/sys
Re: DHCP question
* Hari [EMAIL PROTECTED] [2008-07-24 04:44]: On Wed, Jul 23, 2008 at 9:28 PM, Henning Brauer [EMAIL PROTECTED] wrote: ..., so please grab 4.4-beta fron the snapshots dir on ftp and try that. if that still doesn't work, get us full dmesgs as stuart already outlined. I tried with OpenBSD4.4 beta (July 22, 2008) install. Still facing the same network problem. Attached are the dmesgs for bsd.rd and bsd for OpenBSD4.4-latest. the list doesn't take attachments. if that still doesn't work... after install, at the boot prompt, do boot -c, and the the upcoming UKC prompt do a disable acpi followed by quit once the system is running send dmesgs with and without acpi and acpidump output (forgot exact instructions, ask list archives) to marco@ and jordan@ openbsd.org -- Henning Brauer, [EMAIL PROTECTED], [EMAIL PROTECTED] BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting - Hamburg Amsterdam
DHCP question
Hello. I just finished installing OpenBSD 4.3. The dhcp setup during network configuration was fine, meaning, IP address was properly assigned. I went ahead with the default values provided. However, after rebooting post installation, I am getting the following messages that seems to point to a network problem (and of course, no IP address is assigned): messages fxp0: warning: SCB timed out (x 3) fxp0: config command timeout DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 1 send_packet: Network is down No DHCPOFFERS received. No working leases in persistent database - sleeping. /messages Several `intervals` are tried. Dump of some relevant(?) files: #ifconfig lo0: flags-8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33208 groups: lo inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 fxp0: flags-8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33208 lladdr 00:16:76:13:ad:54 media: Ethernet autoselect (100baseTX full-duplex) status: active inet6 fe80::216::76ff::fe13::ad54%fxp0 prefixlen 64 tentative scopeid 0x1 enc0: flags=0 mtu 1536 #cat /etc/hosts: ::1 localhost.WORKGROUP locahost 127.0.0.1 localhost.WORKGROUP localhost ::1 mercury.WORKGROUP mercury 127.0.0.1 mercury.WORKGROUP mercury #cat /etc/hostname.fxp0: dhcp NONE NONE NONE #cat /etc/resolv.conf lookup file bind # hostname mercury.my.domain #domainname (none) For my internet connection, I have a router that acts as a DHCP server assigning IPs as 192.168.11.x. Why is the OpenBSD box not assigned an IP by this router? Can anyone please let me know how I can get the network up and running on the OpenBSD box? Please let me know in case I have missed out on listing any config files. Thanks. Hari
Re: DHCP question
$man fxp timed out - problem with network from your post : send_packet: Network is down -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hari Sent: Wednesday, July 23, 2008 9:33 AM To: misc@openbsd.org Subject: DHCP question Hello. I just finished installing OpenBSD 4.3. The dhcp setup during network configuration was fine, meaning, IP address was properly assigned. I went ahead with the default values provided. However, after rebooting post installation, I am getting the following messages that seems to point to a network problem (and of course, no IP address is assigned): messages fxp0: warning: SCB timed out (x 3) fxp0: config command timeout DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 1 send_packet: Network is down No DHCPOFFERS received. No working leases in persistent database - sleeping. /messages Several `intervals` are tried. Dump of some relevant(?) files: #ifconfig lo0: flags-8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33208 groups: lo inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 fxp0: flags-8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33208 lladdr 00:16:76:13:ad:54 media: Ethernet autoselect (100baseTX full-duplex) status: active inet6 fe80::216::76ff::fe13::ad54%fxp0 prefixlen 64 tentative scopeid 0x1 enc0: flags=0 mtu 1536 #cat /etc/hosts: ::1 localhost.WORKGROUP locahost 127.0.0.1 localhost.WORKGROUP localhost ::1 mercury.WORKGROUP mercury 127.0.0.1 mercury.WORKGROUP mercury #cat /etc/hostname.fxp0: dhcp NONE NONE NONE #cat /etc/resolv.conf lookup file bind # hostname mercury.my.domain #domainname (none) For my internet connection, I have a router that acts as a DHCP server assigning IPs as 192.168.11.x. Why is the OpenBSD box not assigned an IP by this router? Can anyone please let me know how I can get the network up and running on the OpenBSD box? Please let me know in case I have missed out on listing any config files. Thanks. Hari
Re: DHCP question
On Wed, Jul 23, 2008 at 4:53 PM, Tomas Bodzar [EMAIL PROTECTED] wrote: $man fxp timed out - problem with network from your post : send_packet: Network is down The network is good and working and this OpenBSD box is able to grab an IP address during the initial network configuration during installation*. I have checked the cables, etceverything is fine. Its only when I reboot post install, the network is not found and consequently no IP is assigned. * To verify this, I have reinstalled OpenBSD 4.3 multiple times (on the same computer, same location). _Everytime_, an IP address is assigned properly during the initial configuration. Hari
Re: DHCP question
On Wed, Jul 23, 2008 at 5:05 PM, Tomas Bodzar [EMAIL PROTECTED] wrote: Ok.So next step. $sudo ifconfig fxp0 dhcp up gives what? $sudo ifconfig fxp0 dhcp up ifconfig: dhcp: bad value $ :-(
Re: DHCP question
Ok.So next step. $sudo ifconfig fxp0 dhcp up gives what? -Original Message- From: Hari [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 23, 2008 10:00 AM To: Tomas Bodzar Cc: misc@openbsd.org Subject: Re: DHCP question On Wed, Jul 23, 2008 at 4:53 PM, Tomas Bodzar [EMAIL PROTECTED] wrote: $man fxp timed out - problem with network from your post : send_packet: Network is down The network is good and working and this OpenBSD box is able to grab an IP address during the initial network configuration during installation*. I have checked the cables, etceverything is fine. Its only when I reboot post install, the network is not found and consequently no IP is assigned. * To verify this, I have reinstalled OpenBSD 4.3 multiple times (on the same computer, same location). _Everytime_, an IP address is assigned properly during the initial configuration. Hari
Re: DHCP question
Eh,I missed something.Look at /etc/hosts and $hostname Why is localhost.WORKGROUP localhost in /etc/hosts and mercury.my.domain in $hostname ? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hari Sent: Wednesday, July 23, 2008 9:33 AM To: misc@openbsd.org Subject: DHCP question Hello. I just finished installing OpenBSD 4.3. The dhcp setup during network configuration was fine, meaning, IP address was properly assigned. I went ahead with the default values provided. However, after rebooting post installation, I am getting the following messages that seems to point to a network problem (and of course, no IP address is assigned): messages fxp0: warning: SCB timed out (x 3) fxp0: config command timeout DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 1 send_packet: Network is down No DHCPOFFERS received. No working leases in persistent database - sleeping. /messages Several `intervals` are tried. Dump of some relevant(?) files: #ifconfig lo0: flags-8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33208 groups: lo inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 fxp0: flags-8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33208 lladdr 00:16:76:13:ad:54 media: Ethernet autoselect (100baseTX full-duplex) status: active inet6 fe80::216::76ff::fe13::ad54%fxp0 prefixlen 64 tentative scopeid 0x1 enc0: flags=0 mtu 1536 #cat /etc/hosts: ::1 localhost.WORKGROUP locahost 127.0.0.1 localhost.WORKGROUP localhost ::1 mercury.WORKGROUP mercury 127.0.0.1 mercury.WORKGROUP mercury #cat /etc/hostname.fxp0: dhcp NONE NONE NONE #cat /etc/resolv.conf lookup file bind # hostname mercury.my.domain #domainname (none) For my internet connection, I have a router that acts as a DHCP server assigning IPs as 192.168.11.x. Why is the OpenBSD box not assigned an IP by this router? Can anyone please let me know how I can get the network up and running on the OpenBSD box? Please let me know in case I have missed out on listing any config files. Thanks. Hari
Re: DHCP question
On Wed, Jul 23, 2008 at 5:11 PM, Tomas Bodzar [EMAIL PROTECTED] wrote: Eh,I missed something.Look at /etc/hosts and $hostname Why is localhost.WORKGROUP localhost in /etc/hosts and mercury.my.domain in $hostname I have long suspected that this is the problem. I am a novice at this and I have little understanding. I have gone through the man pages for /etc/hosts but I could not figure out what exactly I was doing wrong. What should /etc/hosts read as? And what should the $hostname be? The machine is to be named mercury. $sudo ifconfig fxp0 up fxp0: warning: SCB timed out (x3) fxp0: config command timeout Hari
Re: DHCP question
did you try 'dhclient' ? On Jul 23, 2008, at 1:08 PM, Hari wrote: On Wed, Jul 23, 2008 at 5:05 PM, Tomas Bodzar [EMAIL PROTECTED] wrote: Ok.So next step. $sudo ifconfig fxp0 dhcp up gives what? $sudo ifconfig fxp0 dhcp up ifconfig: dhcp: bad value $ :-(
Re: DHCP question
Hari wrote: On Wed, Jul 23, 2008 at 5:36 PM, Tony Abernethy [EMAIL PROTECTED] wrote: Silly question, but WHAT IP is actually assigned during install? I think something like ifconfig before the halt might work I assume you are installing from CD, not from network It might be as simple as a cable not completely plugged in. IIRC, it was 192.168.11.8. The DNS was properly identified as the router (192.168.11.1). I dont think there is a problem with the cabling. (I double checked this with a laptop). Hari If you got an IP, at lot of things have to be working. ?? What from /etc/hostname.fxp0
Re: DHCP question
On Wed, Jul 23, 2008 at 05:08:31PM +0900, Hari wrote: On Wed, Jul 23, 2008 at 5:05 PM, Tomas Bodzar [EMAIL PROTECTED] wrote: Ok.So next step. $sudo ifconfig fxp0 dhcp up gives what? $sudo ifconfig fxp0 dhcp up ifconfig: dhcp: bad value please try: ps ax | grep dhclient Is dhclient still running? if so please kill this process $sudo pkill dhclient Then try to get a lease $sudo dhclient fxp0 Regards Robert -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? FreeBSD: Are you guys coming or what? OpenBSD: Hey guys you left some holes out there!
Re: DHCP question
On Wed, Jul 23, 2008 at 5:36 PM, Tony Abernethy [EMAIL PROTECTED] wrote: Silly question, but WHAT IP is actually assigned during install? I think something like ifconfig before the halt might work I assume you are installing from CD, not from network It might be as simple as a cable not completely plugged in. IIRC, it was 192.168.11.8. The DNS was properly identified as the router (192.168.11.1). I dont think there is a problem with the cabling. (I double checked this with a laptop). Hari
Re: DHCP question
Hari wrote: Hello. I just finished installing OpenBSD 4.3. The dhcp setup during network configuration was fine, meaning, IP address was properly assigned. I went ahead with the default values provided. However, after rebooting post installation, I am getting the following messages that seems to point to a network problem (and of course, no IP address is assigned): messages fxp0: warning: SCB timed out (x 3) fxp0: config command timeout DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 1 send_packet: Network is down No DHCPOFFERS received. No working leases in persistent database - sleeping. /messages Several `intervals` are tried. Dump of some relevant(?) files: #ifconfig lo0: flags-8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33208 groups: lo inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 fxp0: flags-8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33208 lladdr 00:16:76:13:ad:54 media: Ethernet autoselect (100baseTX full-duplex) status: active inet6 fe80::216::76ff::fe13::ad54%fxp0 prefixlen 64 tentative scopeid 0x1 enc0: flags=0 mtu 1536 Silly question, but WHAT IP is actually assigned during install? I think something like ifconfig before the halt might work I assume you are installing from CD, not from network It might be as simple as a cable not completely plugged in. Good Luck
Re: DHCP question
On Wed, Jul 23, 2008 at 04:33:27PM +0900, Hari wrote: Hello. I just finished installing OpenBSD 4.3. The dhcp setup during network configuration was fine, meaning, IP address was properly assigned. I went ahead with the default values provided. However, after rebooting post installation, I am getting the following messages that seems to point to a network problem (and of course, no IP address is assigned): messages fxp0: warning: SCB timed out (x 3) fxp0: config command timeout DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 1 send_packet: Network is down No DHCPOFFERS received. No working leases in persistent database - sleeping. /messages Several `intervals` are tried. Dump of some relevant(?) files: #ifconfig lo0: flags-8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33208 groups: lo inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 fxp0: flags-8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33208 isn't having LOOPBACK flag and mtu 33208 on a 'real' interface strange? -- vi vi vi -- the number fo the beast
Re: DHCP question
Hari wrote: On Wed, Jul 23, 2008 at 5:11 PM, Tomas Bodzar [EMAIL PROTECTED] wrote: Eh,I missed something.Look at /etc/hosts and $hostname Why is localhost.WORKGROUP localhost in /etc/hosts and mercury.my.domain in $hostname I have long suspected that this is the problem. I am a novice at this and I have little understanding. I have gone through the man pages for /etc/hosts but I could not figure out what exactly I was doing wrong. What should /etc/hosts read as? And what should the $hostname be? The machine is to be named mercury. $sudo ifconfig fxp0 up fxp0: warning: SCB timed out (x3) fxp0: config command timeout Hari My (not so) humble opinion. /etc/hosts is the poor man's DNS -- what name to what IP ::1 localhost.foo.bar localhost 127.0.0.1 localhost.foo.bar localhost ::1 gw.foo.bar gw this-box 192.168.10.1gw this-box gw.foo.bar 192.168.10.22 that-box Actually the local box can have a lot of names, all for the same IP. Looks like your hostname goes into /etc/myname
Re: DHCP question
On Wed, Jul 23, 2008 at 05:19:26PM +0900, Hari wrote: On Wed, Jul 23, 2008 at 5:11 PM, Tomas Bodzar [EMAIL PROTECTED] wrote: Eh,I missed something.Look at /etc/hosts and $hostname Why is localhost.WORKGROUP localhost in /etc/hosts and mercury.my.domain in $hostname I have long suspected that this is the problem. I am a novice at this and I have little understanding. I have gone through the man pages for /etc/hosts but I could not figure out what exactly I was doing wrong. What should /etc/hosts read as? And what should the $hostname be? The machine is to be named mercury. $sudo ifconfig fxp0 up fxp0: warning: SCB timed out (x3) fxp0: config command timeout I thing here is the real problem. It seems the fxp0 interface fails to do some initializing. This probably results in the interface not being fully enabled/up. I'me not sure what SCB is but i think is related to signaling / irq ? Do you see this also with the bsd.rd kernel? Please look if there are differences between the to in dmesg and ifconfig fxp0 ? Regards Robert -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? FreeBSD: Are you guys coming or what? OpenBSD: Hey guys you left some holes out there!
Re: DHCP question
On Wed, Jul 23, 2008 at 5:48 PM, Almir Karic [EMAIL PROTECTED] wrote: #ifconfig lo0: flags-8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33208 groups: lo inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 fxp0: flags-8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33208 isn't having LOOPBACK flag and mtu 33208 on a 'real' interface strange? Apologies. This is my fault. I copied the text incorrectly. #ifconfig lo0: flags-8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33208 groups: lo inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 fxp0: flags-8803UP,BROADCAST,SIMPLEX,MULTICAST mtu 1500 Rest is OK. Apologies once again. Hari
Re: DHCP question
On Wed, Jul 23, 2008 at 5:57 PM, Tony Abernethy [EMAIL PROTECTED] wrote: My (not so) humble opinion. /etc/hosts is the poor man's DNS -- what name to what IP ::1 localhost.foo.bar localhost 127.0.0.1 localhost.foo.bar localhost ::1 gw.foo.bar gw this-box 192.168.10.1gw this-box gw.foo.bar 192.168.10.22 that-box Actually the local box can have a lot of names, all for the same IP. Looks like your hostname goes into /etc/myname I just popped the CD in and the installation is on now. This is what am getting during network configuration: System hostname? mercury Configure the network? [Yes] Available interfaces are: fxp0 Which one do you want to initialize? (or 'done') [fxp0] Symbolic (host) name for fxp0? [mercury] The media options for fxp0 are currently media: Ethernet autoselect (qoobaseTX full-duplex) Do you want to change the media options? [no] IPv4 address for fxp0? (or 'none' or 'dhcp') dhcp Issuing hostname-associated DHCP request for fxp0. DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 2 DHCPOFFER from 192.168.11.1 DHCPREQUEST on fxp0 to 255.255.255.255 port 67 DHCPACK from 192.168.11.1 bound to 192.168.11.8 -- renewal in 86400 seconds IPv6 address for fxp0? (or rtsol or none) [none] No more interfaces to initialize. DNS domain name? (e.g. 'bar.com') [my.domain] DNS nameserver? (IP address or 'none') [192.168.11.1] none Default IPv4 route? (IPv4 address, 'dhcp' or 'none') [dhcp] Edit hosts with ed? [no] Do you want to do any manual network configuration? [no] After this, ifconfig on the system gives: $ifconfig lo: flags=8008LOOPBACK,MULTICAST mtu 33208 groups: lo fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:16:76:13:ad:54 groups: dhcp egress media: Ethernet autoselect (100baseTX full-duplex) status: active inet6 fe80:216:76ff:fe13:ad54%fxp0 prefixlen 64 scopeid 0x1 inet 192.168.11.8 netmask 0xff00 broadcast 192.168.11.255 After rebooting, the network is not up. Getting the error messages I posted initially. Hari
Re: DHCP question
On Wed, Jul 23, 2008 at 6:16 PM, Robert Blacquiere [EMAIL PROTECTED] wrote: I thing here is the real problem. It seems the fxp0 interface fails to do some initializing. This probably results in the interface not being fully enabled/up. I'me not sure what SCB is but i think is related to signaling / irq ? Do you see this also with the bsd.rd kernel? Please look if there are differences between the to in dmesg and ifconfig fxp0 ? I checked dmesg and the output of 'ifconfig fxp0 up'. There is no difference. The only time out messages listed in dmesg are from fxp0 (dmesg | grep -i time). How do I check the SCB thing with the bsd.rd kernel? Hari
Re: DHCP question
Almir Karic wrote On Wed, Jul 23, 2008 at 04:33:27PM +0900, Hari wrote: Hello. I just finished installing OpenBSD 4.3. The dhcp setup during network configuration was fine, meaning, IP address was properly assigned. I went ahead with the default values provided. However, after rebooting post installation, I am getting the following messages that seems to point to a network problem (and of course, no IP address is assigned): messages fxp0: warning: SCB timed out (x 3) fxp0: config command timeout DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 1 send_packet: Network is down No DHCPOFFERS received. No working leases in persistent database - sleeping. /messages Several `intervals` are tried. Dump of some relevant(?) files: #ifconfig lo0: flags-8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33208 groups: lo inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 fxp0: flags-8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33208 isn't having LOOPBACK flag and mtu 33208 on a 'real' interface strange? mine shows (normal) MTU 1500 Overlength packets are treated like errors by most everything. (IIRC) # ifconfig fxp0 fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:90:27:36:ef:22 groups: egress media: Ethernet autoselect (100baseTX full-duplex) status: active inet 12.49.127.241 netmask 0xff80 broadcast 12.49.127.255 inet6 fe80::290:27ff:fe36:ef22%fxp0 prefixlen 64 scopeid 0x1 -- vi vi vi -- the number fo the beast
Re: DHCP question
On 2008-07-23, Tomas Bodzar [EMAIL PROTECTED] wrote: Eh,I missed something.Look at /etc/hosts and $hostname Why is localhost.WORKGROUP localhost in /etc/hosts and that's based on the domain names you received by dhcp. mercury.my.domain in $hostname ? and that's based on responses to questions during installation. /etc/hosts should have a FQDN which matches whatever your hostname is set as pointing at 127.0.0.1.
Re: DHCP question
On 2008-07-23, Hari [EMAIL PROTECTED] wrote: On Wed, Jul 23, 2008 at 6:16 PM, Robert Blacquiere [EMAIL PROTECTED] wrote: I thing here is the real problem. It seems the fxp0 interface fails to do some initializing. This probably results in the interface not being fully enabled/up. I'me not sure what SCB is but i think is related to signaling / irq ? Do you see this also with the bsd.rd kernel? Please look if there are differences between the to in dmesg and ifconfig fxp0 ? I checked dmesg and the output of 'ifconfig fxp0 up'. There is no difference. The only time out messages listed in dmesg are from fxp0 (dmesg | grep -i time). How do I check the SCB thing with the bsd.rd kernel? Please post full unedited dmesg from bsd.rd and from bsd. Since you have no network with bsd, but you do have network with bsd.rd, you can write a file with bsd e.g. dmesg /dmesg.bsd, then boot bsd.rd and interrupt the installation. Mount the disk, e.g. mount /dev/wd0a /mnt, then you can run dhclient manually (dhclient fxp0). Save the bsd.rd dmesg too, use ftp to upload them both to another machine. Alternatively just use serial console if you have the right cable.
Re: DHCP question
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hari Sent: Wednesday, July 23, 2008 9:33 AM To: misc@openbsd.org Subject: DHCP question fxp0: warning: SCB timed out (x 3) Is 'SCB' a typo for 'SBC'? I have SBC DSL, and did have some weirdness getting it to work, which I resolved by adding a line to my 'dhclient.conf' file: supersede domain-name-servers [SBC.Name.Server.1], [SBC.Name.Server.2]; For my internet connection, I have a router that acts as a DHCP server assigning IPs as 192.168.11.x. Why is the OpenBSD box not assigned an IP by this router? Can anyone please let me know how I can get the network up and running on the OpenBSD box? I also had some trouble with the modem/router that SBC sends non-commercial users by default. I picked up the Netopia Router that SBC sends to its commercial clients on eBay, for 1/3 of what SBC sells it for, and it did DHCP with my OBSD box fine. -- -wittig http://www.robertwittig.com/ http://robertwittig.net/ http://robertwittig.org/ .
Re: DHCP question
On Wed, Jul 23, 2008 at 11:24:58AM +, Stuart Henderson wrote: | I checked dmesg and the output of 'ifconfig fxp0 up'. There is no | difference. The only time out messages listed in dmesg are from fxp0 | (dmesg | grep -i time). | | How do I check the SCB thing with the bsd.rd kernel? | | Please post full unedited dmesg from bsd.rd and from bsd. | | Since you have no network with bsd, but you do have network with | bsd.rd, you can write a file with bsd e.g. dmesg /dmesg.bsd, | then boot bsd.rd and interrupt the installation. Mount the disk, | e.g. mount /dev/wd0a /mnt, then you can run dhclient manually | (dhclient fxp0). Save the bsd.rd dmesg too, use ftp to upload | them both to another machine. | | Alternatively just use serial console if you have the right | cable. Saving these files to a floppy (for the oldtimers) or USB attached storage has proven quite useful for me. Cheers, Paul 'WEiRD' de Weerd -- [++-]+++.+++[---].+++[+ +++-].++[-]+.--.[-] http://www.weirdnet.nl/
Re: DHCP question
the amount of bad advice in this thread is incredible. fxp0 works in bsd.rd, doesn't with bsd. now what is the biggest difference that affects things like interrupt routing between those? ight, ACPI. lots of work has been done in the area, so please grab 4.4-beta fron the snapshots dir on ftp and try that. if that still doesn't work, get us full dmesgs as stuart already outlined. -- Henning Brauer, [EMAIL PROTECTED], [EMAIL PROTECTED] BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting - Hamburg Amsterdam
Re: DHCP question
On Wed, Jul 23, 2008 at 9:28 PM, Henning Brauer [EMAIL PROTECTED] wrote: ..., so please grab 4.4-beta fron the snapshots dir on ftp and try that. if that still doesn't work, get us full dmesgs as stuart already outlined. I tried with OpenBSD4.4 beta (July 22, 2008) install. Still facing the same network problem. Attached are the dmesgs for bsd.rd and bsd for OpenBSD4.4-latest. Hari [demime 1.01d removed an attachment of type application/octet-stream which had a name of dmesg.44.bsd.out] [demime 1.01d removed an attachment of type application/octet-stream which had a name of dmesg.44.bsd.rd.out]
dhcp question
List, I have a 4.1 GENERIC machine acting as DHCP server, serving out IP addresses to 7 diskless client machines. Each client machine needs to be pushed a different configuration file in order to start a process once booted. There is a chance that any number of clients may be replaced at any time. My initial thinking was to define a range of 7 IP addresses in dhcpd.conf so when the client has got an IP it can then request a file named as the clients IP address from the server. However if a client needs replacing the new client will dhcp for an address but dhcpd will complain (justifiably) that there are no spare addresses (the lease-time being 1 day). So if I defined a large pool of IP addresses in dhcpd.conf that would avert the problem described above, however I'm struggling to think of a solution on how would clients would request the correct configuration file? and how could I handle new clients replacing broken ones with regard to dishing out the correct configuration file? Apologies for such woolly posting, I'm just hoping for some inspired ideas. Thanks for your time
Re: dhcp question
On Tue, Jul 03, 2007 at 02:45:00PM +0100, mgb wrote:
So if I defined a large pool of IP addresses in dhcpd.conf that
would avert the problem described above, however I'm struggling to
think of a solution on how would clients would request the correct
configuration file? and how could I handle new clients replacing
broken ones with regard to dishing out the correct configuration
file?
Use lladdrs, not IP addresses, to name or serve the files. This is
how most PXE setups work. See pxeboot(8) for some discussion.
--
o--{ Will Maier }--o
| web:...http://www.lfod.us/ | [EMAIL PROTECTED] |
*--[ BSD Unix: Live Free or Die ]--*
Re: dhcp question
mgb wrote: List, I have a 4.1 GENERIC machine acting as DHCP server, serving out IP addresses to 7 diskless client machines. Each client machine needs to be pushed a different configuration file in order to start a process once booted. There is a chance that any number of clients may be replaced at any time. My initial thinking was to define a range of 7 IP addresses in dhcpd.conf so when the client has got an IP it can then request a file named as the clients IP address from the server. However if a client needs replacing the new client will dhcp for an address but dhcpd will complain (justifiably) that there are no spare addresses (the lease-time being 1 day). since these clients are probably wired, why not lower the lease time to, say, 30 minutes? this would allow you to rotate machines pretty easily and have the new one pickup shortly after the old one is removed. depends on how quickly you're planning to rotate the dhcp clients. 30 minutes of time between disconnecting one (maybe b/c it's broken?) and reconnecting another to take its place seems reasonable. if this doesn't cut it fish around for a way to terminate dhcp leases as a function of whether the diskless services are active for a given client. maybe RADIUS could be helpful... don't have much experience here. cheers, jake So if I defined a large pool of IP addresses in dhcpd.conf that would avert the problem described above, however I'm struggling to think of a solution on how would clients would request the correct configuration file? and how could I handle new clients replacing broken ones with regard to dishing out the correct configuration file? Apologies for such woolly posting, I'm just hoping for some inspired ideas. Thanks for your time
DHCP question
Hi, I'm wondering whether it's possible to have dhcpd give out addresses more randomly and changing the addresses more for hosts that renew their lease. I don't understand DHCP too well but I'm trying to make sense of the RFC. Is it not wanted that hosts on DHCP enjoy a random IP? Or is use of DHCP mainly for making configuration of hosts easier in a large network? In my setup here at home the router changes addresses frequently (this has many benefits, such as deterring people from using static ip's on the wifi) however I'd like the DHCP clients to enjoy a rather ever changing address as well, I've set the leases to 10 seconds or so but the other host seems to not want to move away from the IP it was given. I was hoping it would pick an IP out of the range option in dhcpd.conf. Thanks for feedback, -peter
Re: DHCP question
From: [EMAIL PROTECTED] Is it not wanted that hosts on DHCP enjoy a random IP? Or is use of DHCP mainly for making configuration of hosts easier in a large network? Does a random IP taste better to the interface card than a static one? The *whole* point of DHCP is to make configuration of hosts on a LAN easier to configure. What benefit is there to randomizing it from the system's perspective? It's not like the network stack has ADHD and gets bored with the same old IP address every day. In my setup here at home the router changes addresses frequently (this has many benefits, such as deterring people from using static ip's on the wifi) How is that deterrent? And why does it matter? The point of the IP address is to allow you to communicate on the network. Who cares if it is always changing? however I'd like the DHCP clients to enjoy a rather ever changing address as well, I've set the leases to 10 seconds or so but the other host seems to not want to move away from the IP it was given. I was hoping it would pick an IP out of the range option in dhcpd.conf. I think you're trying to find a solution for a problem that doesn't exist. DS
Re: DHCP question
On 6/22/06, Peter Philipp [EMAIL PROTECTED] wrote: In my setup here at home the router changes addresses frequently (this has many benefits, such as deterring people from using static ip's on the wifi) however I'd like the DHCP clients to enjoy a rather ever changing address as well, I've set the leases to 10 seconds or so but the other host seems to not want to move away from the IP it was given. I was hoping it would pick an IP out of the range option in dhcpd.conf. I'm being good and not unleashing a torrent of vitriol and bile at you for that idea. DHCP will do a renew to try hang on to the address it currently has before it'll ask for a new one. I'm not so sure that breaking the protocol is a good idea (ie. don't do it). Someone else asked what the real problem you're trying to solve is. If this is a real problem (and not you wanting to have the l33t-est ftp server on the block) I suggest that you go look at the pf table features in dhcpd (in -current). Let dhcpd detect campers and use pf to punish them. Let dhcpd put the currently leased addresses in a table and block everything else. Don't shoot yourself in the foot with a broken dhcp server. CK -- GDB has a 'break' feature; why doesn't it have 'fix' too?
