error in network layer ?
Submitted by Trickkiste on Fri, 04/30/2004 - 15:20.
hi,
I tried to use the NAT network of the vmware, but I got several errors, e.g. the ping could not ping to localhost:'
(I did
ifconfig 127.0.0.1 loopback
ping 127.0.0.1
and got )
java.net.NoRouteToHostException : 127.0.0.1
after that I did
route add 127.0.0.1 loopback
and I got
Ping 127.0.0.1 attemp 0
Exception in QueueProcessor
java.lang.NullPointerException: NP at adress ...
org.jnode.net.ipv4.layer.IPv4NetworkLayer!recieve (145)
did I anything wrong / has anyone a solution for that ?
thanks,
Andreas
- Login to post comments
does it work?
Hi,
will you tell me if it works for you?
I think it has to be possible to ping at least the loopback device.
After that it has to be possible to ping other ip's.
So, please post if it works and how you configuered your System (what hardware / what has to be done in JNode)
Thx
Trickkiste
Your paper on JNode
Dear Andreas,
I'm Birkey, a developer for JNode, currently working with Martin on JNode's deployment framework.
Martin recommanded your paper "Analyse und Erweiterung des Java-Betriebsystems ’JNODE’" to me, but I cannot read German
Do you have an English version of that paper? I think it's helpful for me for I'm working on a paper about JNode, especailly its Arch and Component Model from
the component-based extension OS perspective.
Best regards
-Birkey
I have looked at it and it sh
I have looked at it and it should work now, but please test it. Still there are some problems with the routing, but Pavlos it looking at it.
Regards,
Martin
Btw. it's "ifconfig loopback 127.0.0.1"
it works
Hi,
I have testet it on VMware and it works.
But I got one Deadlock message.
Trickkiste
LanceDriver
Hi,
I can now configure the loopback device and let it ping itsself.
But for the vwmare emulated network card it does not work.
I did :
ifconfig eth0 192.168.0.100
route add 192.168.0.100 eth0
ping 192.168.0.100
What I got was :
ERROR [TxDescriptorRing]: Not owner of descriptor index 0
device eth0 shows the following information :
Device: eth0
state:started
driver:org.jnode.driver.net.lance.LanceDriver
implemented API's:
org.jnode.driver.net.NetDeviceAPI
org.jnode.driver.DeviceAPI
Location 0,16,0
Configuration device=0x2000, vendor=0x1022, class=02:00:00, revision=16 headertype=0, intr-pin=1, intr-line=9, base-addresses={IO:00001000-0000101F, MEM32:FD000000-FD00001F}
any suggestions ?
thx,
Trickkiste
There was an error when sendi
There was an error when sending data to the same hardware address as the device hardware address, this should be fixed now, please check it out.
Regards,
Martin
good work
Hi,
now it works also for my eth0 device.
But I am still not able to do a :
dhcp eth0
it says:
Trying to configure eth0...
ERROR [TxDescriptorRing]: Not owner of descriptor index 0
java.net.SocketTimeoutException: Timeout in recive
org.jnode.net.util.AbstractDatagramSocketImpl!recive (246)
java.net.DatagramSocket!recive (431)
org.jnode.net.ipv4.bootp.BOOTPClient$1!run (100)
org.jnode.vm.VmAccessController!doPrivileged (175)
org.jnode.net.ipv4.bootp.BOOTPClient!configureDevice (61 [java.security.AccessController#doPrivileged 144])
org.jnode.net.command.DhcpCommand!main (36)
...
Trickkiste
Try entring the "dhcp eth0" a
Try entring the "dhcp eth0" again when this happens. Looks like a timeout when jnode is waiting for response from the dhcp server. Sometimes I get the same, maybe we should make a nicer timeout message... I think I'll try monitoring the dhcp request/reply, maybe this will tell me something.
Regards,
Martin
This is probably because
This is probably because the first time a method is called, it takse o bit of time to be compiled in the VM.
Adjusting this timeout maybe will help Martin.
sounds good
Hi,
good idea,
I will try some more network related things...
Trickkiste
same with dhcp
hi,
i got the same error while dhcp tries to configures the eth0 device...
Trickkiste
I am working on some problems
I am working on some problems like this.
I am thinking to fix also the automatic route configuration with the ifconfig.
state of your work ?
Hi,
how far are you with that ?
Andreas
Currently, i have fixed a pro
Currently, i have fixed a problem, with which when there was an incoming packet with 4th byte set to 255, it was proccesed. Even if you dont have set an IP address to the interface. Also, with this problem the IP stack does not work with subnets different than the default.
For me everything is ok, but martin got some exceptions. I have not added the code to cvs, because any jnode systems connected to a lan will become unstable if you have the same problem.
Branch in CVS
Why don't you make a branch in CVS and check them in there, then we can all test, without breaking the HEAD branch.
Ewout
I am not good with cvs. Can I
I am not good with cvs. Can I make a branch of a sub-folder of a project?
Anyway, martin has found the error in my changes and yesterday I have added them to cvs.
Trickkiste, can you check if the problem you have described is fixed?
Some changes in the routing system will follow.
no good news
Hi,
I have tested it on my VMware workstation and it was not fixed.
I will try it on a real machine.
Andreas