Routing not working
Tom Horsley
horsley1953 at gmail.com
Wed Jun 1 16:32:19 UTC 2011
On Wed, 01 Jun 2011 11:07:54 -0400
Genes MailLists wrote:
> In the meantime can you provide the outputs of what I suggested
> previously for the F15 system. Are you seeing any AVC's by the way ?
I got the info from f15, but I also found when I rebooted
that the wi-fi on the phone couldn't connect this time because
the dhcpd died for no obvious reason after my script started
it. Also, I'm not using any ipv6 on f14 or f15 (as far as I know).
Anyway, other than substituting em1 for eth0, the output I gathered
on f15 looked identical to the output on f14:
ifconfig says:
em1 Link encap:Ethernet HWaddr 00:1E:4F:9A:D6:E5
inet addr:10.134.30.143 Bcast:10.134.30.255 Mask:255.255.255.0
inet6 addr: fe80::21e:4fff:fe9a:d6e5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2468 errors:0 dropped:0 overruns:0 frame:0
TX packets:700 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:218060 (212.9 KiB) TX bytes:76510 (74.7 KiB)
Interrupt:21 Memory:febe0000-fec00000
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:1081 errors:0 dropped:0 overruns:0 frame:0
TX packets:1081 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:83988 (82.0 KiB) TX bytes:83988 (82.0 KiB)
mon.wlan0 Link encap:UNSPEC HWaddr 94-44-52-45-F3-3A-E0-F1-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:78 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6855 (6.6 KiB) TX bytes:0 (0.0 b)
wlan0 Link encap:Ethernet HWaddr 94:44:52:45:F3:3A
inet addr:192.168.9.1 Bcast:192.168.9.255 Mask:255.255.255.0
inet6 addr: fe80::9644:52ff:fe45:f33a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:55 errors:0 dropped:4 overruns:0 frame:0
TX packets:51 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13720 (13.3 KiB) TX bytes:13844 (13.5 KiB)
Here's iwconfig:
lo no wireless extensions.
em1 no wireless extensions.
wlan0 IEEE 802.11bg Mode:Master Frequency:2.462 GHz Tx-Power=27 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:on
mon.wlan0 IEEE 802.11bg Mode:Monitor Tx-Power=27 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Here's ip route:
10.134.30.0/24 dev em1 proto kernel scope link src 10.134.30.143
192.168.9.0/24 dev wlan0 proto kernel scope link src 192.168.9.1
169.254.0.0/16 dev em1 scope link metric 1002
default via 10.134.30.196 dev em1
Here's ip addr show:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:1e:4f:9a:d6:e5 brd ff:ff:ff:ff:ff:ff
inet 10.134.30.143/24 brd 10.134.30.255 scope global em1
inet6 fe80::21e:4fff:fe9a:d6e5/64 scope link
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 94:44:52:45:f3:3a brd ff:ff:ff:ff:ff:ff
inet 192.168.9.1/24 brd 192.168.9.255 scope global wlan0
inet6 fe80::9644:52ff:fe45:f33a/64 scope link
valid_lft forever preferred_lft forever
4: mon.wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UNKNOWN qlen 1000
link/ieee802.11/radiotap 94:44:52:45:f3:3a brd ff:ff:ff:ff:ff:ff
Here's /proc/sys/net/ipv4/ip_forward
1
I'm starting to wonder if the ralink driver it is using is
just flaky on f15.
More information about the users
mailing list