network fails Hi there,
something goes wrong with your dhcp-code. When I receive dhcp-data from my server (data correct), I cannot ping the Kolibri from my linux box, host unreachable. The ethstats prog increases the IP packets receive count.
When I configure the same ip data as in dhcp manually, all works fine.
facts:
OS: KoOS 0.5.3p2
Host: amd 350 MHz, 128 MB RAM
Boot: from hd, fat32 with w98 loader
NIC: rtl8139
LAN: dhcpd on linux 2.4
IP 192,168,10.164/26
Gateway 192.168.10.130
<3 minutes later>
I solved the problem for my enviironment ;-)
The problem in your implementation is, that it needs 3 digits for each IP oktet, like "010" instead of simply "10". Editing my /etc/dhcpd.conf solved the problem. But later one should change the client code, not the server config.
I will have a look into the stackcfg.asm, but my assemler knowlegde is not very great.
So long, much thanks for that great work, you won a new user ;-)
PS.: It would be great, if you at least the comments in example files write in english, or even better all comments in source.
The dhcp request don not use NICs MAC adress, I have a fixed IP in my dhcpd.conf, but its not recognized.
Sry 4 my critics in this networking stuff... I am a sysadmin, thats my job *g*
hidnplayr- 06-27-2006
kolibri/menuetos does not reply to ping.
derPENGUIN- 06-27-2006
sure, it does.
jason.b.c- 06-27-2006
You've got it on the internet..???
I don't know if it does reply to a ping or not, Wish i did..
Try and go to here https://www.grc.com/x/ne.dll?bh0bkyd2 , Then click Proceed and then All Common Ports..
Hope that might help.. :wink:
hidnplayr- 06-28-2006
oh sorry but AFAIK it doesnt reply, well, if you say so...
i dont really get your problem here, is it with the DHCP client that you have to config the stack manually???
derPENGUIN- 06-28-2006
@jason.b.c
Your link points to a portscanner. Thank you, but I dont need that. I can scan my boxes with nmap in LAN. KoOS reply to ping, if I configured the IP manually.
@hidnplayr
Yes, exactly that is the problem. The dhcp client dos not work correctly. May be, it dos not update the stack at all. And, thats sure, it dosn't submit the MAC.
Dex- 06-28-2006
@derPENGUIN, i have read your posts with interest, i am implementing network stuff, on my own OS, as you are a sysadmin (i am new to network coding) you may be able to advice on design etc.
My first steps was i need a ethernet card driver, (rtl8139 driver ) which the basic are done for this driver, now i have set up a lan with 2 pc, my OS and 2 rtl8139 cards and crossover cable, also i have linux on i pc and win98 on the other (note my OS boots from floppy.
What parts do you think i should start with, at what point should i get to before moving off lan etc.
Thanks in advances.
Note: My OS is single-tasking .
jason.b.c- 06-28-2006
@jason.b.c
Your link points to a portscanner. Thank you, but I dont need that. I can scan my boxes with nmap in LAN. KoOS reply to ping, if I configured the IP manually.
Oh i know it does .! :D I provided that because on that site you can do a test that will tell you for sure if it replies to a ping or not..
Which my computer does not reply to pings... :D YAH..!
Madis731- 06-29-2006
I will go a bit off-topic but the most of these problems are related to network. The network stack and other applications don't tell you if it succeeded or failed or if it did anything at all. There is no signal. You just click some buttons and hope the "thing" you need, happens.
Some error-message would be helpful and a succession message also. In other OSs you can see the buttons moving when you click and when it doesn't need applying or whatever the name of the button is - its grayed out. So you know that it DID try it and DID succeed. When it stays the same and displays an error message instead - you know that you have to try it some other way...
I will put all my strength in WYSIWYG MeOS...because OS can't be trusted if it doesn't Get You What You THINK You See :D
hidnplayr- 06-29-2006
@jason.b.c
@hidnplayr
Yes, exactly that is the problem. The dhcp client does not work correctly. May be, it dos not update the stack at all. And, thats sure, it dosn't submit the MAC.
well, the DHCP client doesnt update the stack at all, it is made for doing so manually.
you could easily change the DHCP client so that it does.
EDIT: do not fear, the rescue team is here! (i'm working on an automated dhcp client :p)
Another EDIT:
download here: http://menuet.homelinux.net/images/9/98/Autodhcp.zip
edit AUTORUN.DAT with notepad and add this line to run my progam when menuet/kolibri boots:
/RD/1/AUTODHCP <NO> 30 # Dhcp client
derPENGUIN- 07-05-2006
Oh, great. I see, there is some good work in progress. Sry, I was<some days offline, and atm i am sitting in a inet cafe, but whem i come back online at home, i will test your ttol.
Because of the trouble with that dhcp stuff i started writing my own, but it dos not work atm. I spent too much time to read the MAC, but thats done now.
I added for that a new kernel function, 52.15, with that code:
cmp ebx,4
je read
cmp ebx,0
je read
mov eax,ebx ; false param, give it back
jmp end
read:
mov eax,[node_addr+ebx]
end:
I hope, I remembered it correctly, as I said, I sit in a inet cafe... This function returns whith mcall 52,15,4 the right 4 MAC bytes in eax, with ebx=0 the left 2 bytes. But all in mirrored order, e.g. 06:05:04:03:02:01. Can someone sort it`
Thanks so far, when i am back in web, i will upload all my code.
Happy hacking ;-)
Forumer™ is Voted #1 Free Forum Hosting provider
Build your own community today with the largest message board hosting company.