FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora User

 
 
LinkBack Thread Tools
 
Old 06-01-2011, 02:46 PM
Tom Horsley
 
Default Routing not working

On Wed, 01 Jun 2011 10:25:27 -0400
Genes MailLists wrote:

> On 06/01/2011 10:02 AM, Tom Horsley wrote:
> > On Tue, 31 May 2011 09:29:09 -0400
> > Tom Horsley wrote:
> >
>
> >
> > Anyone have any pointers for debugging routing?
> > Anyone know of something that maybe changed in
> > this vicinity in f15?
>
> One quick question - did you change your iptables rules to use the new
> interface names ?

Yep. I found and fixed all the eth0 names in any of the
config files involved.

Most of the info about what I'm doing is described here:

http://home.comcast.net/~tomhorsley/hardware/rtl8192cu/rtl8192cu.html#Success

This works great under fedora 14, but my phone can't talk
to anything (other than the DHCP server) on fedora 15 doing
all the same stuff. It gets the wi-fi connection, but thats it.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 06-01-2011, 03:07 PM
Genes MailLists
 
Default Routing not working

On 06/01/2011 10:46 AM, Tom Horsley wrote:
> On Wed, 01 Jun 2011 10:25:27 -0400
>
> Most of the info about what I'm doing is described here:
>
> http://home.comcast.net/~tomhorsley/hardware/rtl8192cu/rtl8192cu.html#Success
>
> This works great under fedora 14, but my phone can't talk
> to anything (other than the DHCP server) on fedora 15 doing
> all the same stuff. It gets the wi-fi connection, but thats it.

I'll try and go over what you did - unfortunately, I am totally
unfamiliar with hostapd or why you need it (is it related to your dongle
somehow ?) and how it interacts with other parts of
firewall/routing/networking.

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 ?


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 06-01-2011, 03:24 PM
Tom Horsley
 
Default Routing not working

On Wed, 01 Jun 2011 11:07:54 -0400
Genes MailLists wrote:

> I'll try and go over what you did - unfortunately, I am totally
> unfamiliar with hostapd or why you need it (is it related to your dongle
> somehow ?) and how it interacts with other parts of
> firewall/routing/networking.

That's what turns it into an access point rather than running the
dongle in normal mode where it is a client of some other access point.

I'll have to wait till I have a chance to boot f15 again to get
the additional info, but I have selinux disabled, so I doubt
I'm getting any AVCs.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 06-01-2011, 04:23 PM
Genes MailLists
 
Default Routing not working

On 06/01/2011 11:24 AM, Tom Horsley wrote:
> On Wed, 01 Jun 2011 11:07:54 -0400
> Genes MailLists wrote:
>
>> I'll try and go over what you did - unfortunately, I am totally
>> unfamiliar with hostapd or why you need it (is it related to your dongle
>> somehow ?) and how it interacts with other parts of
>> firewall/routing/networking.
>
> That's what turns it into an access point rather than running the
> dongle in normal mode where it is a client of some other access point.
>
> I'll have to wait till I have a chance to boot f15 again to get
> the additional info, but I have selinux disabled, so I doubt
> I'm getting any AVCs.


Ok - and the hostapd is the fedora F15 version installed via yum?
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 06-01-2011, 04:32 PM
Tom Horsley
 
Default Routing not working

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:9A6: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 thrff Fragment thrff
Power Managementn

mon.wlan0 IEEE 802.11bg Mode:Monitor Tx-Power=27 dBm
Retry long limit:7 RTS thrff Fragment thrff
Power Managementff

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.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 06-01-2011, 05:20 PM
Tom Horsley
 
Default Routing not working

On Wed, 01 Jun 2011 12:23:04 -0400
Genes MailLists wrote:

> Ok - and the hostapd is the fedora F15 version installed via yum?

Yep, that's the one I normally use. I also tried building from
the latest source on the hostapd home page, but got the same
results.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 06-01-2011, 05:49 PM
Genes MailLists
 
Default Routing not working

On 06/01/2011 12:32 PM, Tom Horsley wrote:
> On Wed, 01 Jun 2011 11:07:54 -0400

>
> ifconfig says:
>
> em1 Link encap:Ethernet HWaddr 00:1E:4F:9A6: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

ipv6 looks on to me ..

>
> 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

I suppose this has something to do with hostapd ?


>
> 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

ditto
>

> 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

I assume the default route is to your internet gateway ..

>
> Here's ip addr show:

> 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.

Possible - I think I'd try turning off IPV6 first .. to make sure its
not interfering in some way .. probably not but might not hurt to test that.



--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 06-01-2011, 06:21 PM
Tom Horsley
 
Default Routing not working

On Wed, 01 Jun 2011 13:49:30 -0400
Genes MailLists wrote:

> > I'm starting to wonder if the ralink driver it is using is
> > just flaky on f15.
>
> Possible - I think I'd try turning off IPV6 first .. to make sure its
> not interfering in some way .. probably not but might not hurt to test that.

Actually, in the flaky behavior department, I just tried booting f15
one more time, and this time everything started working when I ran
the script. I think the fact that it sometimes works says I'm probably
doing routing correctly, but some other random problem is screwing me
up. Maybe I need some delays, or I should be doing things in a different
order or something. It seems like wlan0 sometimes just stops working
when I poke through the logs. The dongle does get quite warm when it
is running, maybe it is just overheating.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 06-01-2011, 06:31 PM
Genes MailLists
 
Default Routing not working

On 06/01/2011 02:21 PM, Tom Horsley wrote:
> Actually, in the flaky behavior department, I just tried booting f15
> one more time, and this time everything started working when I ran
> the script. I think the fact that it sometimes works says I'm probably
> doing routing correctly, but some other random problem is screwing me
> up. Maybe I need some delays, or I should be doing things in a different
> order or something. It seems like wlan0 sometimes just stops working
> when I poke through the logs. The dongle does get quite warm when it
> is running, maybe it is just overheating.


Ah ... could well be ... maybe its time for a re-dongle :-)
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 06-01-2011, 06:39 PM
Tom Horsley
 
Default Routing not working

On Wed, 01 Jun 2011 14:31:21 -0400
Genes MailLists wrote:

> Ah ... could well be ... maybe its time for a re-dongle :-)

My next step is finding the digital thermometer we have around
here somewhere and measuring the temp on f14 compared to f15 :-).

Thanks for all the help.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 

Thread Tools




All times are GMT. The time now is 10:45 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org