[BusyBox] Networking problems
nawawi
mohd.nawawi at gmail.com
Sun Apr 17 15:15:29 UTC 2005
you can try to up loopback dev first.. ifconfig lo 127.0.0.1<http://127.0.0.1>up
On 4/17/05, Sam Robb <uclibc at oneparticularharbor.net> wrote:
>
> All,
>
> Please forgive if this is a FAQ - but I've searched the docs
> and Google in vain for some information about how to set up
> networking with BusyBox. I'm particularly frustrated in that
> I *had* gotten networking into a working state, but have since
> managed to muck things up and befuddle myself.
>
> I have BB set up to generate the ip, ifconfig, etc. applets.
> My kernel has networking support turned on, and my network cards
> are compiled built-in instead of as modules. Everything comes
> together when I reboot my x86 system (using my kernel and my
> RFS) - the kernel sees the network cards, ifconfig can configure
> them ('ifconfig eth0 192.168.1.101 <http://192.168.1.101> up'), 'route'
> returns what
> looks like valid information, etc.
>
> Despite all that - I am completely unable to see or interact
> with the network. On a second machine on the same Ethernet hub,
> ethereal doesn't even see the packets generated by this machine;
> they look like they're getting consigned to the network bit-bucket
> for some reason. When I reboot the system into FC3, I'm able to
> interact with the network on both the network interfaces (eth0
> and eth1) - so I don't think there are any cabling problems or
> hardware problems contributing to the complete lack of networkness :-/
>
> -Samrobb
>
>
> _______________________________________________
> busybox mailing list
> busybox at mail.busybox.net
> http://busybox.net/mailman/listinfo/busybox
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/busybox/attachments/20050417/1a9fb588/attachment.html
More information about the busybox
mailing list