In my effort to make a bootimage work with netwoeking I have entered
a new problem.
I have a motherbord mounted tulip-circuit implementing my
ethernet-connectivity.
When trying to mount this in my bootimage with the command:
io-net -v -dtulip -pttcpip
if=en0:180.180.45.20:255.255.255.0,
route=180.180.45.0:255.255.255.0:180.180.45.0,
verbose=2
I constantly get answers
“sendto: No route to host” when pinging myself (180.180.45.20) or other
computers.
But when pinging myself as 127.0.0.1, it succeeds.
I have tried a number of variations as specified in help-files with and
without sub-masks, route-tables…
Always the same answer
What do I wrong? Has someone any solutions?
/Gunnar
Try it without the route:
io-net -dtulip -pttcpip if=en0:180.180.45.20:255.255.255.0
The route to network 180.180.45.0 will be created for you
(you’re dirextly connected to it).
With the above, ‘cat /proc/ipstats’ should look like:
verbosity level 0
ip checksum errors: 0
udp checksum errors: 0
tcp checksum errors: 0
packets sent: 0
packets received: 7
en0 : addr 180.180.45.20 netmask 255.255.255.0 up
lo0 : addr 127.0.0.1 netmask 255.0.0.0 up
DST: 180.180.45.0 NETMASK: 255.255.255.0 GATEWAY: en0
DST: 127.0.0.0 NETMASK: 255.0.0.0 GATEWAY: lo0
If it doesn’t, look at the output of ‘pidin’ and
ensure you only have 1 io-net running.
-seanb
: In my effort to make a bootimage work with netwoeking I have entered
: a new problem.
: I have a motherbord mounted tulip-circuit implementing my
: ethernet-connectivity.
: When trying to mount this in my bootimage with the command:
: io-net -v -dtulip -pttcpip
: if=en0:180.180.45.20:255.255.255.0,
: route=180.180.45.0:255.255.255.0:180.180.45.0,
: verbose=2
: I constantly get answers
: “sendto: No route to host” when pinging myself (180.180.45.20) or other
: computers.
: But when pinging myself as 127.0.0.1, it succeeds.
: I have tried a number of variations as specified in help-files with and
: without sub-masks, route-tables…
: Always the same answer
: What do I wrong? Has someone any solutions?
: /Gunnar