VOIP with a linksys PAP2
Kevin J. Cummings
cummings at kjchome.homeip.net
Mon Jun 13 17:24:53 UTC 2005
THUFIR HAWAT wrote:
> [root at localhost ~]# ifconfig
> eth0 Link encap:Ethernet HWaddr 00:0A:E6:A0:24:27
> inet addr:192.168.2.175 Bcast:192.168.2.255 Mask:255.255.255.0
> inet6 addr: fe80::20a:e6ff:fea0:2427/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:6864 errors:0 dropped:0 overruns:0 frame:0
> TX packets:6765 errors:0 dropped:1 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:4312260 (4.1 MiB) TX bytes:1249117 (1.1 MiB)
> Interrupt:5 Base address:0xd400
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:156 errors:0 dropped:0 overruns:0 frame:0
> TX packets:156 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:16680 (16.2 KiB) TX bytes:16680 (16.2 KiB)
>
> [root at localhost ~]# route
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 192.168.2.0 * 255.255.255.0 U 0 0 0 eth0
> 169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
> default 192.168.2.1 0.0.0.0 UG 0 0 0 eth0
> [root at localhost ~]# which route
> /sbin/route
>
>
> heh, thanks. I just woke up, but unfortunately must deal with
> personal stuff and can't take a further look at this for the moment.
> however, just getting that info was a big help :)
Indeed, I see no mention of eth1 here, but perhaps its not configured?
Does "ifconfig eth1" tell you anything?
And what is the 169.254.0.0 route from? It looks like an address range
that Microsoft Windows uses when it can't find a DHCP server....
Since all 3 routes are via eth0, it looks like all IP traffic from your
Linux computer are using eth0. This should/will change if you can
configure eth1 correctly with your PAP2 on it.
--
Kevin J. Cummings
kjchome at rcn.com
cummings at kjchome.homeip.net
cummings at kjc386.framingham.ma.us
More information about the fedora-list
mailing list