Ulot, Richard, Dimitris, thanks for the advice,
On 06/04/2012 16:46, Ulot Olhado wrote:
> You should only have one default gateway that "points" to the internet.
Yes, I was trying to achieve that. I use XFCE and the network manager
applet seems 'not' to let me edit the eth0 connection so that the IF
detail is, for example:
<blank for gateway>
Instead, the applet doesn't let me 'apply' the settings unless the
gateway field is filled in.
Then, if the gateway field is filled in, the netbook treats the eth0
gateway address as the default route, instead of using the wlan0
gateway entry as the default route.
I think I understand what I need to achieve, I'm just having
difficulty using the setup utilities.
> You can use the route command at the cli to see your routes there.
> Removing the default gateway on the eth0 device will probably solve you
> problem based on what you said.
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
192.168.13.0 * 255.255.255.0 U 2 0
192.168.0.0 * 255.255.255.0 U 1 0
default 192.168.0.190 0.0.0.0 UG 0 0
As I mentioned, I don't seem to be able to remove the gateway entry
At one time, I used to use firestarter which allowed me to explicitly
assign the 'internet' port, and the port for 'local network' access.
In system-config-firewall I don't seem to be able to do that; I had
set 'masquerade' thinking that might cause the same effect, but
I'm going to search the internet for how to do this at cli level - I
will post back.
Thanks again for the help.
Using AspireOne netbook as a (temporary) replacement internet gateway
router, combined with a proxy server.
Due to the layout of the building, using wlan0 as the connection to
the internet (ADSL wireless router), and using wired eth0 port to
serve the local network clients. The intention is that clients will
use the netbook as their gateway, through eth0, and the netbook will
masquerade their traffic and then onward route to the internet over
the wlan port. Simple, basic, router, set up with
system-config-firewall to masquerade eth0, the local net traffic
The proxy server is needed so that some applications on other systems
can temporarily route their traffic through the netbook, without
having to reconfigure the default route settings on their hosts.
Installed tinyproxy to do this.
But tinyproxy, though configured to send outbound traffic to the
address of the ADSL router [192.168.13.1], appears to be placing its
outbound traffic on eth0, not on wlan0. Actually, tinyproxy doesn't
'know' about ports, only addresses, so it is the netbook that is
placing traffic for the ADSL router back onto the local net, instead
of on wlan0. I'm guessing, but I wonder if the default route is (for
some reason) set to be reached using eth0 instead of wlan0.
Using network manager applet, I can see that both eth0 and wlan0 have
default gateways and (of course) these are different because the two
ports are on entirely different networks.
How do people check the default route?
Grateful for any advice,
When I plug/unplug ac adapter, upower doesn't report that it's state
changed, kde's power manager doesn't switch profiles. If I start with
ac adapter plugged in and then unplug it, battery indicator shows that
battery is discharging, but ac adapter is plugged in. Battery state is
reported correctly. This problem exists in every linux distribution I
tried for every kernel version from 2.6 to 3.4. Also it seems that
this bug affects many people (open bugs in kde, upower bugtrackers).
I found a workaround and I think I must share it. I rebuilt kernel
with ACPI_PROCFS_POWER=y ("Deprecated power /proc/acpi directories")
and noticed that if I do "cat /proc/acpi/ac_adapter/AC/state" then
state of the adapter becomes correct in kde, upower's output, etc.
I added a file to /etc/acpi/events/ with following contents:
action=cat /proc/acpi/ac_adapter/AC/state > /dev/null
After restarting acpid everything works. The only problem is that
ACPI_PROCFS_POWER is deprecated. I hope this bug will be fixed before
the option will be removed. And I think this workaround must be
described somewhere in documentation/FAQ/wiki.