On 15.07.05 Bluebottle change log wrote:
AosIP.Mod AosIPv4.Mod AosIPv6.Mod, AosDHCP.Mod - bug corrected for UDP broadcast, performance improvements CharacterLineup.Mod - update WMPerfMon.Mod - shows available heap space
I have just booted the current crazy fresh CD: DHCP still does not work! Some weeks ago I have done a hard-disk-installation -- if I enter all network parameters manually, then network will work. Any suggestions how to debug AOS DHCP? Reading full DHCP specs and connecting an Linux-computer running a network monitor like Etherreal should work, but maybe there is a simpler way? Here is the kernel log when booting CD: Log started Aos 15.07.05 Single-processor IDE0..1: 14 000001F0 000003F6 reset ok IDE2..3: 15 00000170 00000376 reset ok IDE2: no reset IDE0: 43979MB, 16383*16*63, (89355*16*63), LBA, IBM-DTLA-307045, ver 5.21 IDE2: packet cd-rom device, removable, Pioneer DVD-ROM ATAPIModel DVD-106S 0122, ver 5.0 Bus-master chipset not detected AosDiskFS: Index not found on RAM0 AosDiskFS: Scanning RAM0... marking 0 files AosDiskFS: 31992K of 32000K available on RAM0 AosDiskVolumes: IDE0 invalid partition AosDiskVolumes: IDE2#0 {P0 AosDisplayLinear: GlobalSetCacheProperties = 2304} AosUhci: Initialised USB UHCI controller at base 0D400H, Irq: 9 USB version: 1.0 AosUhci: Initialised USB UHCI controller at base 0D000H, Irq: 9 USB version: 1.0 AosUsb: Driver UsbHub (integrated USB hub driver) has been added. AosUsb: USB driver loaded. AosUsb: Driver UsbMouse (USB mouse driver) has been added. AosUsb: Driver UsbStorage (Usb Storage Device Driver) has been added. Default font installedOpenType 0.45 BBPort /3.12.2004 eos, pl Manager.New finished Disp.format = 2 {P0 Bottom up...New background-->Mouse Cursor-->NIL } {P0 3Com90x#0 auto-selection not supported} {P0 Media = 00800000} {P0 3Com90x#0 half-duplex} {P0 IntEnable = 000004C2} {P0 Install Handler IRQ = 0A} {P0 No need for Timer} Searching devices... Find finished. Autostart: executing StartMenu.Open Loading range 00007E4A..00007F4A Loading range 00007945..00007A45 Loading range 00008B57..00008C57 Loading range 00008955..00008A55 Loading range 0000622E..0000632E Loading range 0000F51C..0000F51E Loading range 00005420..00005520 Loading range 0000531F..0000541F Loading range 0000F532..0000F538 Loading range 00004E1A..00004F1A Autostart: executing WMRestorable.Load Auto.dsk No image list found loading {P0 Starting logger} loading AosInitNet: Module initialized. Searching for installed devices... AosInitNet: LinkDevice 'Loopback' found. AosInitNet: LinkDevice 'Loopback': Get interface configuration. Error code: 0 AosInitNet: Add interface for LinkDevice 'Loopback'. Error code: 0 {P0 === Interface === Interface name: Loopbackv6 Attached device: Loopback (LinkLinked) MAC address: 00:00:00:00:00:00:00:00 Local address: ::1 Default routers: Prefix: ::/64 DNS server: none } AosInitNet: Add interface for LinkDevice 'Loopback'. Error code: 0 {P0 === Interface === Interface name: Loopbackv4 Attached device: Loopback (LinkLinked) MAC address: 00:00:00:00:00:00:00:00 Local address: 127.0.0.1 Netmask: 255.255.0.0 Gateway address: Subnet: 127.0.0.0 Net broadcast: 127.0.255.255 DNS server: none } AosInitNet: LinkDevice '3Com90x#0' found. AosInitNet: LinkDevice '3Com90x#0': Get interface configuration. Error code: 0 AosInitNet: Add interface for LinkDevice '3Com90x#0'. Error code: 0 {P0 === Interface === Interface name: v6link-local3Com90x#0 Attached device: 3Com90x#0 (LinkUnknown) MAC address: 00:01:02:B9:02:2F:00:00 Local address: FE80::201:2FF:FEB9:22F Default routers: Prefix: FE80::/64 DNS server: none } AosInitNet: Add interface for LinkDevice '3Com90x#0'. Error code: 0 AosInitNet: Finished searching for installed devices. AosDHCP: Starting DHCP on interface 'v4auto3Com90x#0'... {P0 AosDHCP: Discover - xid 585048800} {P0 AosDHCP: Discover - xid 585048801} {P0 AosDHCP: Discover - xid 585048802} AosDHCP: Finished DHCP on interface 'v4auto3Com90x#0'. Error code: 3502 {P0 ETH Oberon / Aos 15.07.05} Partitions: IDE0 89355*16*63=90069840 -> 5606*255*63=90060390 Partitions: GetGeometry result 2503 AosFATVolumes: Device IDE0#6 {P0 Kernel 7 discarded finalizers, 0 pending finalizers} Macro file Macros.XML loaded.
On 7/18/05, Stefan Salewski <Salewski@physnet.uni-hamburg.de> wrote:
DHCP still does not work!
I have two DHCP-capable devices on my home network, some junk Accton (?) DSL modem and an SMC wireless access point. I liked the management interface of the SMC so I had been doing DHCP using it, but I found that I could not pull an address from Bluebottle and (poorly) assumed it was the client and not the server. Swapping back to the Accton worked perfectly, so I don't doubt that the Bluebottle client implementation may be less forgiving than your average Windows box, but it may be worthwhile to try an alternate DHCP server if you have one available, just to check. -Jack
Am Montag, 18. Juli 2005 19:52 schrieb Stefan Salewski:
I have just booted the current crazy fresh CD: DHCP still does not work!
I have traced the DHCP communication between my computer running Win2000 and our DHCP-server with Ethereal. There are some significant differences between the windows DHCP-Discover message and the AOS Discover message created by AosDHCP.CreateDiscoveryMsg. I think that our DHCP-Server will not recognize the AOS DHCP-Discover message. So it seems to be necessary to read some documentation about DHCP and then to modify AosDHCP.CreateDiscoveryMsg() until our DHCP server can understand it. Is it necessary to reboot after each modification of AosDHCP.CreateDiscoverMsg() to test DHCP protocoll or is there a way to relaunch network without rebooting? (like ipconfig /release -- ipconfig /renew in windows or ifconfig up -- ifconfig down in linux) Best regards Stefan Salewski
participants (2)
-
Jack Johnson -
Stefan Salewski