At 23:11 01/02/2008 -0600, Darrick Hartman (lists) wrote:
>What's lsmod look like? You should not have to compile your own kernel,
>but it would be helpful to know which kernel module is needed for that
>hardware (I'm assuming the tulip module).
Apparently, that NIC is known to be a bit of a pain to work with, so I
looked through my stuff, and found a no-name NIC based on the RealTek
RTL8139 chip that worked out of the box:
==========
eth1 Link encap:Ethernet HWaddr 00:48:54:3D:9E:EB
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:151 errors:0 dropped:0 overruns:0 frame:0
TX packets:51 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:17688 (17.2 KiB) TX bytes:13026 (12.7 KiB)
Interrupt:6 Base address:0xef00
============
Since AstLinux is not based on a stock distro, I can't use the network
scripts I'm used to to enable routing, so Il'l just type the usual "echo
"1" > /proc/sys/net/ipv4/ip_forward" and see if a remote IP phone on the
Net is able to connect and talk with the IP phone on 192.168.1.2/24 through
the 192.168.0.4/24 that is connected to the WAN.
============
pbx ~ # route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
default 192.168.0.254 0.0.0.0 UG 0 0 0 eth0
============
Thanks.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to [EMAIL
PROTECTED]
