Bypass the login manager or flimflam

[Ankman]

This topic was discussed already, but that was in April 2011 that I
cannot even send a followup. So I start a new thread.

I would also like to bypass the login manager because of my "strange"
network and/or design flaw in Chromium (Lime).

I use an encrypted ad-hoc connection from notebook (Linux) to netbook
(Linux, or Chromium). IPs on both side shall also be static as I do
not want to use the DHCP server on the other computer, although I
could install it.

I have two issues with that.

1. Chromium does not "see" my ad-hoc source, just like Windows 7
Starter (by purpose as I learned). It only sees it for may be a minute
when I re-initiate the cell on the other computer. Then I select it in
Chromium from the drop down list and insert the WLAN password.

2. What I can see in the Chromium logs (CTRL-ALT-F8) is that it seems
to connect successfully, but fails to obtain an IP address (as DHCP is
not running on the other computer). When I'm quick and use ifconfig
and route to set all up manually, I can then ping servers in the
internet. I also created a /etc/resolv.conf manually. But after a few
seconds the login manager (or flimflam) assumes the connection was
unsuccessful and drops the device, which also clears the routing
table, although I was connected.

So I can set up a connection manually, but Chromium won't keep it.
That's why I would like to bypass the login manager if possible and
set up the connection manually. Otherwise it would be nice to have an
option to tell it to use a fix IP instead of using DHCP.

[Sam Leffler]

You should be able to connect to an existing adhoc network (people w/
older phones use it for tethering). Not sure we've tested static key
wep (guess that's what you mean by "encrypted") but it should work.

You might start by identifying your system and build. Past that you
can check system logs via chrome:system and/or turn debug msgs up with
wpa_debug (for wpa_supplicant). Since you say you join the adhoc
network but don't get a dhcp lease it sounds like this is an issue at
a lower layer and you'll likely not find anything in the logs. If
you're building your own image you can add tcpdump (it's automatically
included in test images) and collect packet traces.

-Sam

> --
> Chromium OS discuss mailing list: chromium-...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en

[Ankman]

Hi Sam,

thank you for the reply.

I use the hexxeh.net version I downloaded from that web page. Haven't
it here so cannot tell you the exact build right now.

Yes, WEP is the encryption on adhoc.

I don't get a dhcp lease because it's not desired on my side. The
other computer, which routes the internet via WLAN adhoc, has no DHCP
server running. Not Chromiums fault here.

All shall have fixed IPs. That works with another Linux or a Windows
computer where I set up fixed IPs. On this computer (netbook) I also
have Chromium on an USB stick, which doesn't connect because insisting
doing DHCP. That's why - in my case - it would be nice to tell
Chromium to have a fix IP rather then doing DHCP. Or bypass the main
login screen and set up everything manually on a text console.

> > Chromium OS discuss mailing list: chromium-os-disc...@chromium.org

[Sam Leffler]

There is static ip config support hidden under about:flags. The
implementation has limitations which is why it's not on by default.

-Sam

> Chromium OS discuss mailing list: chromium-...@chromium.org

[Ankman]

On Feb 5, 4:04 pm, Sam Leffler <sleff...@chromium.org> wrote:
> There is static ip config support hidden under about:flags.  The
> implementation has limitations which is why it's not on by default.

I activated it, and after logout and login (even reboot ;-) I found a
new tab in the Options. But I can not select "static IP", it's grayed
out. I also tried the "proxy server" box. I could open it but there
also not change anything.

[Ankman]

Let me also add the following information.

So I went out to have "normal" internet (other than my static IP -
adhoc) and was able to connect to the router, got an IP and then got
past the initial login screen. That was a while ago.

Back at home to my surprise then I noticed the initial login screen
didn't come anymore. So I was able to follow your advice and activated
static IP and stuff (which didn't work, see post above).

Yesterday then I was not using the browser to try to connect to the
internet but did all manually (iw, ifconfig and so on). I was able to
get a stable internet connection with static IP to my adhoc network. I
could ping other server, ssh to my other box and to machines in other
countries where I have Linux accounts.

But when I went to the browser and just wanted to load google.com it
did nothing. For a split second it seemed to try to load, then
nothing. No error, no changes to the blank page there (showing "Most
visited" though). But I was still online and could use the console.

I assume it's a permission issue (connection was not established via
the Chrome browser, so it doesn't like to connect?). I couldn't see
anything in the logs though.

Before I test more here I might go to an internet cafe at the weekend
again and see if I can get online the way it's supposed to be - via
the browser (settings/internet).