GSM connection timeout after suspend / resume
Hi! After suspend / resume I get a "GSM connection failed: (32) Network timeout". What I need to do is right click on nm-applet and deselect / select "activate mobile broadband" I'm using a Lenovo X220 with a Ericsson F5521gw card. System is Ubuntu Lucid with the following packages: modemmanager : 1:0.4+git.20101103t150351.a2d54b1 network-manager : 1:0.8.4-0 network-manager-gnome : 1:0.8.4-0 I have put debug for modem-manager here: http://pastebin.com/MXE8QzBe and the NetworkManager debug here: http://pastebin.com/AHYNMdAD Best regards! Hans-Gerd ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
captiveportal autologin
Hi, does someone has an idea about automatically detetect and or login into an captive portal with networkmanager mechanism. Thank you. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
getting result of "at+cpin?" via dbus
Hi, can somebody tell me if there is a way to get the output of "at+cpin?" for a connected modem via dbus api? I already found org.freedesktop.ModemManager.Modem.Gsm.Card.EnablePin() but nothing for getting the current SIM state. I'm on the way to disable PIN Protection on all of our SIM Cards. Because I need to do this more or less fully automated I need a way to check the active state and let the user enter the PIN one time in a popup. Thank you! -- HG ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems initializing the modem
Am Donnerstag, den 14.10.2010, 10:35 +0200 schrieb Dan Williams : > On Sat, 2010-10-09 at 10:39 +0200, van Schelve wrote: >> Hi. >> >> I was able to reproduce a problem where I get many issue tickets from >> our users in the field for. >> >> The problem from user side is that the system is offline after login >> and they are not able to connect manually until they have used the >> rfkill swich. We have a session autostart to bring up a 3g based >> systemconnection in the case that the system is offline. If that fails >> the user can start the connection by hand using nm-applet. But if the >> modem-manager fails to initialize the modem the user cannot start the >> connection because there is no entry in the list. This problem occurs >> very often. >> >> I was able to reproduce the issue - which was very difficult - while >> running modem-manager in debug mode and capture some logs and I really >> hope they are useful. >> >> Some user reports that they run into this issue very often, some >> others never have seen this. They all have the same components and >> identical hardware / bios / firmware etc. >> >> The attached syslog.stripped only contains the NetworkManager >> messages. There was no modem-manager logs in the original file maybe >> because modem-manager was started with --debug option. > > The problem shown in the MM log where MM would not finish probing the > modem due to the incoming CnS packets has been fixed in git now. Thanks > for the logs, they were quite necessary in diagnosing the issue and they > made me add a bunch of testcases for stuff like this. > > The actual fix is: > http://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=dd8a061d28ecaf286bfba3bdbd2a495c45cfb4a4 > > Any testing/confirmation that this fixes the modem detection issue would > be appreciated, thanks! > > Dan Hi Dan, after some internal testing I have now modemmanager 1:0.4+git.20101014t221514.9fa20cd in production. At the moment it looks much better but I cannot give a qualified feedback from the field right now. In general it would be fine to have the debug output from modemmanager in syslog. This would help to see the different debug in the right sequence. HG ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Automatic re-connect script for 3G connections (van Schelve)
Am 22.10.2010 um 19:58 schrieb Dan Williams: > On Fri, 2010-10-22 at 14:03 +0200, van Schelve wrote: >> Am Freitag, den 22.10.2010, 11:17 +0200 schrieb Florian Hackenberger >> : >>> Hi! >>> >>> dcbw on #nm told me that van Schelve has a script at hand which >>> automatically reconnects nm manager using a 3G connection. >>> >>> van Schelve: Would you mind sharing that script with me? >>> >>> Thanks in advance, Florian >> >> Hi! >> >> That's not completely correct. I wrote a script to dialup a 3G >> connection conditionally. The intention for this script was to bring up >> a 3g connection during gnome-autostart when a user logs in and after >> suspend / resume. >> >> I won't use the autoconnect feature from network-manager at that time. >> >> Dan: I am interesting in automatically reconnect a broken mobile 3G >> connection as well ;-) > > Yeah, this needs doing and I have some ideas for it. I suppose we > should see if there's a way to physically cut power to the device if it > gets wedged too badly, which devices often do. Any ideas on how to do > that? There is some new kernel stuff in 2.6.35 and later that we can > try I think. > > Dan > Hm, what's with the pppd persist option? Would this be helpful? In our old system I have enabled this in /etc/ppp/options and in some situations this was helpful. Sometimes we see "carrier lost" due to temporary bad signal for example in a tunnel or while traveling in a train Hans-Gerd ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Automatic re-connect script for 3G connections (van Schelve)
Am Freitag, den 22.10.2010, 11:17 +0200 schrieb Florian Hackenberger
:
> Hi!
>
> dcbw on #nm told me that van Schelve has a script at hand which
> automatically reconnects nm manager using a 3G connection.
>
> van Schelve: Would you mind sharing that script with me?
>
> Thanks in advance, Florian
Hi!
That's not completely correct. I wrote a script to dialup a 3G
connection conditionally. The intention for this script was to bring up
a 3g connection during gnome-autostart when a user logs in and after
suspend / resume.
I won't use the autoconnect feature from network-manager at that time.
Dan: I am interesting in automatically reconnect a broken mobile 3G
connection as well ;-)
Attached you can find my script. Hope it will help you!
#!/usr/bin/python
import dbus,syslog,time
syslog.openlog('wwan-autoconnect')
bus = dbus.SystemBus()
def print_one_services_connections(service_name, desc):
# Ask the settings service for the list of connections it provides
proxy = bus.get_object(service_name,
"/org/freedesktop/NetworkManagerSettings")
settings = dbus.Interface(proxy,
"org.freedesktop.NetworkManagerSettings")
connection_paths = settings.ListConnections()
# List each connection's name, UUID, and type
for path in connection_paths:
con_proxy = bus.get_object(service_name, path)
connection = dbus.Interface(con_proxy,
"org.freedesktop.NetworkManagerSettings.Connection")
config = connection.GetSettings()
# Get the details of the 'connection' setting
s_con = config['connection']
if s_con['id'] == "MYCONN":
return path
def print_devices(service_name, desc):
# Ask the settings service for the list of connections it provides
proxy = bus.get_object(service_name, "/org/freedesktop/NetworkManager")
nm = dbus.Interface(proxy, "org.freedesktop.NetworkManager")
device_paths = nm.GetDevices()
# List each device
for path in device_paths:
con_proxy = bus.get_object(service_name, path)
connection = dbus.Interface(con_proxy,
"org.freedesktop.DBus.Properties")
prop =
connection.Get('org.freedesktop.NetworkManager.Device','DeviceType')
# We are only interested in GSM devices
if prop == 3:
return path
bus = dbus.SystemBus()
# constants for accessing gnome network manager
busName = 'org.freedesktop.NetworkManager'
busPath = '/org/freedesktop/NetworkManager'
busInterface = 'org.freedesktop.NetworkManager'
proxy = bus.get_object("org.freedesktop.NetworkManager",
"/org/freedesktop/NetworkManager")
status = dbus.Interface(proxy,
"org.freedesktop.DBus.Properties").Get("org.freedesktop.NetworkManager","State")
if status == 4:
syslog.syslog("Starte Mobilverbindung")
#time.sleep(15)
nm = dbus.Interface(proxy, "org.freedesktop.NetworkManager")
con = print_one_services_connections("org.freedesktop.NetworkManager",
"System")
if con != None:
for i in range(5):
dev = print_devices("org.freedesktop.NetworkManager",
"System")
if dev == None:
time.sleep(2)
else:
break
if dev != None:
nm.ActivateConnection("org.freedesktop.NetworkManagerSystemSettings",con,dev,"/")
else:
syslog.syslog("Kein aktives Modem gefunden")
else:
syslog.syslog("Keine Mobilkonfiguration vorhanden")
else:
syslog.syslog("Netzwerk ist aktiv. Mobile Einwahl nicht erforderlich")
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Unable to connect to mobile broadband: +CME ERROR:30
Am Donnerstag, den 14.10.2010, 11:09 +0200 schrieb Dan Williams : > On Thu, 2010-10-14 at 09:30 +0200, van Schelve wrote: >> Am Mittwoch, den 13.10.2010, 21:00 +0200 schrieb van Schelve >> : >> > Am Mittwoch, den 13.10.2010, 12:49 +0200 schrieb Dan Williams >> > : >> >> On Mon, 2010-10-11 at 10:43 +0200, van Schelve wrote: >> >>> Hi, >> >>> >> >>> I found a different problem where I get reports from our users in the >> >>> field. They tell us that they are not able to connect to mobile >> >>> network. >> >>> >> >>> In the logs I captured I found a cme error 30 which means "No network >> >>> service". I tried it two or three times with still the same problem. >> >>> Then I tested with a second identical laptop with an identical setup >> >>> and I was able to bring up the mobile connection on this system without >> >>> any problem. >> >>> >> >>> So I decided to use the rfkill switch on the laptop where I found the >> >>> problem with the result that dialin was possible after doing th rfkill >> >>> cycle. >> >> >> >> Interesting; your module seems to have firmware 1.1.8.3, while I have 3 >> >> different modules with 1.1.8.15, 1.1.9.3, and 2.0.8.19. I think >> >> 2.0.8.19 screwed my device though, so don't try it. I've noticed odd >> >> problems like this on other Sierra devices in the past that were solved >> >> by firmware updates (AC875 and AC881), but it's pretty hard to find >> >> firmware upgrades for their embedded modules. Do you know offhand if >> >> any of the devices in the field has other firmware than 1.1.8.3? >> > >> > We have completely identical hardware in the field. All the systems are >> > Lenovo Thinkpad T61 with identical BIOS 2.10 version and the same >> > firmware >> > on the embedded sierra device : 1.1.8.3. I think changing the firmware >> > to >> > a different version woud be a really bad option. Our systems are spread >> > all over germany and I don't think the firmware update would be >> > possible >> > under linux. >> >> I talked about this problem with a contact at SierraWireless. He said >> that >> a firmware upgrade will not help in this case. But what can help is >> checking >> for PS attach and dial only if PS attach status is attached. Dialing >> without >> PS attach can bring modem into unwanted condition that sometimes >> restart is >> needed to recover. > > Hmm, interesting. I'll try a few things out then. > > Dan > Hi Dan, I got an additional hint I'll forward to you now: "... Since you have enabled +CREG=2 notification for registration, there is no need to query registration status. Let the modem find the network and register and you will be notified. So, do not execute +CREG? Do not attempt PPP connection unless there is PS attach. As I mentioned before, check for PS attach status after you have received registration. ..." HG ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Unable to connect to mobile broadband: +CME ERROR:30
Am Mittwoch, den 13.10.2010, 21:00 +0200 schrieb van Schelve : > Am Mittwoch, den 13.10.2010, 12:49 +0200 schrieb Dan Williams > : >> On Mon, 2010-10-11 at 10:43 +0200, van Schelve wrote: >>> Hi, >>> >>> I found a different problem where I get reports from our users in the >>> field. They tell us that they are not able to connect to mobile >>> network. >>> >>> In the logs I captured I found a cme error 30 which means "No network >>> service". I tried it two or three times with still the same problem. >>> Then I tested with a second identical laptop with an identical setup >>> and I was able to bring up the mobile connection on this system without >>> any problem. >>> >>> So I decided to use the rfkill switch on the laptop where I found the >>> problem with the result that dialin was possible after doing th rfkill >>> cycle. >> >> Interesting; your module seems to have firmware 1.1.8.3, while I have 3 >> different modules with 1.1.8.15, 1.1.9.3, and 2.0.8.19. I think >> 2.0.8.19 screwed my device though, so don't try it. I've noticed odd >> problems like this on other Sierra devices in the past that were solved >> by firmware updates (AC875 and AC881), but it's pretty hard to find >> firmware upgrades for their embedded modules. Do you know offhand if >> any of the devices in the field has other firmware than 1.1.8.3? > > We have completely identical hardware in the field. All the systems are > Lenovo Thinkpad T61 with identical BIOS 2.10 version and the same > firmware > on the embedded sierra device : 1.1.8.3. I think changing the firmware > to > a different version woud be a really bad option. Our systems are spread > all over germany and I don't think the firmware update would be > possible > under linux. I talked about this problem with a contact at SierraWireless. He said that a firmware upgrade will not help in this case. But what can help is checking for PS attach and dial only if PS attach status is attached. Dialing without PS attach can bring modem into unwanted condition that sometimes restart is needed to recover. > > On the other hand it was good luck that I was able to see this issue on > my system. I'm thinking about enabling debug on all our systems this > way: > > cat > /usr/share/dbus-1/system-services/org.freedesktop.ModemManager.service > [D-BUS Service] > Name=org.freedesktop.ModemManager > Exec=/usr/sbin/modem-manager --debug >> > /var/log/modem-manager-debug.log > User=root > > and starting NetworkManager --log-level=debug in the upstart initscript > > What do you mean? Would this be ok? > >> >> In any case, I'll add some code to ModemManager to get better Sierra >> device status for GSM devices to help debug this issue. If you run into >> this problem yourself, we want the output of AT!GSTATUS? to get more >> info if you can. >> > > But this means I need to disable mobile broadband temporary because > otherwise > the serial port is blocked by modem-manager and I cannot get the > information at > the same time. Having more debug in sierraplugin would be very helpful > because > I have seen other issues that I have not reported yet (for example SIM > Busy) > > HG > >> Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Unable to connect to mobile broadband: +CME ERROR:30
Am Mittwoch, den 13.10.2010, 12:49 +0200 schrieb Dan Williams : > On Mon, 2010-10-11 at 10:43 +0200, van Schelve wrote: >> Hi, >> >> I found a different problem where I get reports from our users in the >> field. They tell us that they are not able to connect to mobile >> network. >> >> In the logs I captured I found a cme error 30 which means "No network >> service". I tried it two or three times with still the same problem. >> Then I tested with a second identical laptop with an identical setup >> and I was able to bring up the mobile connection on this system without >> any problem. >> >> So I decided to use the rfkill switch on the laptop where I found the >> problem with the result that dialin was possible after doing th rfkill >> cycle. > > Interesting; your module seems to have firmware 1.1.8.3, while I have 3 > different modules with 1.1.8.15, 1.1.9.3, and 2.0.8.19. I think > 2.0.8.19 screwed my device though, so don't try it. I've noticed odd > problems like this on other Sierra devices in the past that were solved > by firmware updates (AC875 and AC881), but it's pretty hard to find > firmware upgrades for their embedded modules. Do you know offhand if > any of the devices in the field has other firmware than 1.1.8.3? We have completely identical hardware in the field. All the systems are Lenovo Thinkpad T61 with identical BIOS 2.10 version and the same firmware on the embedded sierra device : 1.1.8.3. I think changing the firmware to a different version woud be a really bad option. Our systems are spread all over germany and I don't think the firmware update would be possible under linux. On the other hand it was good luck that I was able to see this issue on my system. I'm thinking about enabling debug on all our systems this way: cat /usr/share/dbus-1/system-services/org.freedesktop.ModemManager.service [D-BUS Service] Name=org.freedesktop.ModemManager Exec=/usr/sbin/modem-manager --debug >> /var/log/modem-manager-debug.log User=root and starting NetworkManager --log-level=debug in the upstart initscript What do you mean? Would this be ok? > > In any case, I'll add some code to ModemManager to get better Sierra > device status for GSM devices to help debug this issue. If you run into > this problem yourself, we want the output of AT!GSTATUS? to get more > info if you can. > But this means I need to disable mobile broadband temporary because otherwise the serial port is blocked by modem-manager and I cannot get the information at the same time. Having more debug in sierraplugin would be very helpful because I have seen other issues that I have not reported yet (for example SIM Busy) HG > Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Problems initializing the modem
Hi. I was able to reproduce a problem where I get many issue tickets from our users in the field for. The problem from user side is that the system is offline after login and they are not able to connect manually until they have used the rfkill swich. We have a session autostart to bring up a 3g based systemconnection in the case that the system is offline. If that fails the user can start the connection by hand using nm-applet. But if the modem-manager fails to initialize the modem the user cannot start the connection because there is no entry in the list. This problem occurs very often. I was able to reproduce the issue - which was very difficult - while running modem-manager in debug mode and capture some logs and I really hope they are useful. Some user reports that they run into this issue very often, some others never have seen this. They all have the same components and identical hardware / bios / firmware etc. The attached syslog.stripped only contains the NetworkManager messages. There was no modem-manager logs in the original file maybe because modem-manager was started with --debug option. HG ** (modem-manager:1202): DEBUG: (tty/ttyS1): port's parent platform driver is not whitelisted ** (modem-manager:1202): DEBUG: (tty/ttyS2): port's parent platform driver is not whitelisted ** (modem-manager:1202): DEBUG: (tty/ttyS3): port's parent platform driver is not whitelisted ** (modem-manager:1202): DEBUG: <1286544679.57594> (ttyS0) device open count is 1 (open) ** (modem-manager:1202): DEBUG: (ttyS0): probe requested by plugin 'Generic' ** (modem-manager:1202): DEBUG: <1286544679.62350> (ttyUSB0) device open count is 1 (open) ** (modem-manager:1202): DEBUG: (ttyUSB0): probe requested by plugin 'Sierra' ** (modem-manager:1202): DEBUG: <1286544679.70352> (ttyUSB1) device open count is 1 (open) ** (modem-manager:1202): DEBUG: (ttyUSB1): probe requested by plugin 'Sierra' ** (modem-manager:1202): DEBUG: <1286544679.75353> (ttyUSB2) device open count is 1 (open) ** (modem-manager:1202): DEBUG: (ttyUSB2): probe requested by plugin 'Sierra' ** (modem-manager:1202): DEBUG: <1286544679.157071> (ttyS0): --> 'AT+GCAP' ** (modem-manager:1202): DEBUG: <1286544679.962648> (ttyUSB0): --> 'AT+GCAP' ** (modem-manager:1202): DEBUG: <1286544680.770868> (ttyUSB1): --> 'AT+GCAP' ** (modem-manager:1202): DEBUG: <1286544681.689444> (ttyUSB2): --> 'AT+GCAP' ** (modem-manager:1202): DEBUG: (net/pan0): could not get port's parent device ** (modem-manager:1202): DEBUG: <1286544682.491039> (ttyUSB0): <-- '+GCAP: +CGSM,+DS,+ESOK' ** (modem-manager:1202): DEBUG: <1286544682.491110> (ttyUSB2): <-- 'OK' ** (modem-manager:1202): DEBUG: <1286544682.491493> (ttyUSB0) device open count is 0 (close) ** (modem-manager:1202): DEBUG: <1286544682.503657> (ttyUSB2): --> 'AT+GCAP' ** (modem-manager:1202): DEBUG: <1286544683.304696> (ttyUSB2): <-- 'OK' ** (modem-manager:1202): DEBUG: <1286544683.309378> (ttyUSB0) device open count is 1 (open) ** (modem-manager:1202): DEBUG: <1286544683.309409> (ttyUSB0) device open count is 2 (open) ** (modem-manager:1202): DEBUG: Added modem /sys/devices/pci:00/:00:1d.1/usb6/6-1 ** (modem-manager:1202): DEBUG: (tty/ttyUSB0): outstanding support task prevents export of /sys/devices/pci:00/:00:1d.1/usb6/6-1 ** (modem-manager:1202): DEBUG: (tty/ttyUSB1): outstanding support task prevents export of /sys/devices/pci:00/:00:1d.1/usb6/6-1 ** (modem-manager:1202): DEBUG: <1286544683.309593> (ttyUSB0): --> 'AT+CPIN?' ** (modem-manager:1202): DEBUG: <1286544683.319579> (ttyUSB2): --> 'AT+GCAP' ** (modem-manager:1202): DEBUG: <1286544684.196160> (ttyS0): --> 'AT+GCAP' ** (modem-manager:1202): DEBUG: <1286544684.997272> (ttyUSB1): <-- '~\0kk\0\0\7\0\0\0\0\0\0\0~' ** (modem-manager:1202): DEBUG: <1286544684.997314> (ttyUSB2): <-- 'OK' ** (modem-manager:1202): DEBUG: <1286544684.997351> (ttyUSB0): <-- '+CPIN: READYOK' ** (modem-manager:1202): DEBUG: <1286544684.997419> (ttyUSB0) device open count is 1 (close) ** (modem-manager:1202): DEBUG: (tty/ttyUSB1): outstanding support task prevents export of /sys/devices/pci:00/:00:1d.1/usb6/6-1 ** (modem-manager:1202): DEBUG: <1286544684.997501> (ttyUSB0): --> 'ATE0' ** (modem-manager:1202): DEBUG: <1286544685.3103> (ttyUSB2): --> 'ATI' ** (modem-manager:1202): DEBUG: <1286544685.403644> (ttyUSB2): <-- 'Sierra Wireless, Inc.MC8775APP1OK' ** (modem-manager:1202): DEBUG: <1286544685.403689> (ttyUSB0): <-- 'OK' ** (modem-manager:1202): DEBUG: <1286544685.403743> (ttyUSB1): --> 'AT+GCAP' ** (modem-manager:1202): DEBUG: <1286544686.204750> (ttyUSB0): --> 'AT+CGSN' ** (modem-manager:1202): DEBUG: <1286544686.214004> (ttyUSB2) device open count is 0 (close) ** (modem-manager:1202): DEBUG: (tty/ttyUSB1): outstanding support task prevents export of /sys/devices/pci:00/:00:1d.1/usb6/6-1 ** (modem-manager:1202): DEBUG: <1286544686.223494> (ttyUSB0): <-- '352678013064321OK' ** (modem-manager:1202): DEB
Re: problems with 3g based connections
Am Donnerstag, den 22.07.2010, 16:29 +0200 schrieb Dan Williams : > On Fri, 2010-07-16 at 12:16 +0200, van Schelve wrote: >> Am Donnerstag, den 15.07.2010, 02:00 +0200 schrieb Dan Williams >> : >> > On Mon, 2010-07-05 at 08:42 +0200, van Schelve wrote: >> >> >> Hi, >> >> >> >> >> >> some days ago I have reported a curious issue with modem-manager. >> >> >> My main Problem is that I'm sometimes not able to dialup a modem >> based >> >> 3g >> >> >> connection. The connection is not listed in nm-applet in this case >> and >> >> in >> >> >> syslog I have entries like this one: >> >> >> >> >> >> ... >> >> >> May 21 10:055:28 nc0631 modem-manager: (tty/ttyUSB0): outstanding >> >> support >> >> >> task prevents export of >> /sys/devices/pci:00/:00:1d.1/usb6/6-1 >> >> >> ... >> >> > >> >> > This means that some ports of the modem are still being detected and >> >> > probed. The modem cannot be used until all ports have completed >> >> > detection. >> >> > >> >> >> @Dan, you asked me to bring more debug but I'm not able to reproduce >> >> this >> >> >> issue while manually starting nm / mm in debug mode. >> >> >> Therefore: is it possible to run network-manager / modem-manager per >> >> >> default in debug mode while starting over upstart? >> >> > >> >> > Possibly, but the debug output doesn't go to syslog, so unless it >> gets >> >> > stored somewhere by upstart it'll get lost. >> >> >> >> We were able to capture the debug output. Without debug we run 6 of 10 >> >> times into >> >> this problem. Running mm in debug mode we were able to reproduce it 3 >> of >> >> 10 times. >> >> >> >> http://pastebin.com/RS5vDxwJ >> >> http://pastebin.com/FmZbkJnc >> >> http://pastebin.com/97GPPbZW >> > >> > This is good stuff; near the end of the log entries you'll see: >> > >> > ** (modem-manager:1054): DEBUG: <1278077341.1209> (ttyUSB1): --> 00 78 >> f0 >> > 7e >> > ** (modem-manager:1054): DEBUG: <1278077342.610807> (ttyUSB1): <-- 7e 00 >> > 0a 6b 24 00 00 07 00 00 00 00 00 00 00 7e >> > ** (modem-manager:1054): DEBUG: <1278077349.610774> (ttyUSB1): <-- 7e 00 >> > 0a 6b 25 00 00 07 00 00 00 00 00 00 00 7e >> > ** (modem-manager:1054): DEBUG: <1278077356.610695> (ttyUSB1): <-- 7e 00 >> > 0a 6b 26 00 00 07 00 00 00 00 00 00 00 7e >> > ** (modem-manager:1054): DEBUG: <1278077363.610729> (ttyUSB1): <-- 7e 00 >> > 0a 6b 27 00 00 07 00 00 00 00 00 00 00 7e >> > ** (modem-manager:1054): DEBUG: <1278077370.610737> (ttyUSB1): <-- 7e 00 >> > 0a 6b 28 00 00 07 00 00 00 00 00 00 00 7e >> > ** (modem-manager:1054): DEBUG: <1278077377.606758> (ttyUSB1): <-- 7e 00 >> > 0a 6b 29 00 00 07 00 00 00 00 00 00 00 7e >> > >> > so ttyUSB1 is a Sierra CnS port (their "Control and Status" protocol) >> > and MM isn't correctly failing out the QCDM probe. What modem is this >> > again? Manufacturer: Sierra Wireless, Inc. Model: MC8775 Revision: H1_1_8_3MCAP C:/WS/FW/H1_1_8_3MCAP/MSM6280/SRC 2007/03/08 18:17:59 IMEI: 352678013570525 IMEI SV: 6 FSN: D280428046710 3GPP Release 5 +GCAP: +CGSM,+DS,+ES >> > >> Dan, you're right. It is the CnS port of the Sierra Wireless MC8775. >> And I think we found the reason for the problem. In addition to all the >> networkmanager components we have a special application, called wsm, that >> displays several informations from the modem like signal strenth, cell >> information >> active band, firmware version, hardware version. I tested with a 0.4 version of modem-manager but we are still having the issue. For ttyUSB1 I can follow you. But why do we see this for ttyUSB0 in the logs as well? I have attached the logs to this mail. Hope it's OK. >> >> These information are taken via CnS. We have disabled this tool and did >> some further >> tests with the result that in 50 / 50 tries everything works fine. >> >> So we decided to remove the wsm tool from users autostart and hope that we >> will get >> the cell information in the future direct from nm-applet. >> >> But if you are intereted in our tool, I can sen
Re: how to let http brings up networkmanager modem connectivity?
Of you can Start your Webbrowser with a Customer Script, it should Be easy to trigger the dialup with a small dbus based script. We are doing something similar in session autostart in the case that the system is offline. I can sent it to you if needed. Am 16.09.2010 um 20:38 schrieb hong sheng : > Let's forget other situations as they are similar, and assume we need to > bring up modem connectivity only when starting the web-brower application, > what should we do in the application? > > thanks > > hong > > 2010/9/16 José Queiroz > And how do you intend to differentiate one from the other? > > 2010/9/16 hong sheng > I mean "bring up the 3G connectivity automatically when we start web brower > application", not just http. > > hong > > > 2010/9/15 Raphaël Jacquot > > > On 15 sept. 2010, at 23:49, hong sheng wrote: > > > Hi > > > > I would skip the networkmanager applet in our platform. In stead, I want to > > let the http brower automatically bring up the 3G connectivity for > > NetworkManager. So, what d-bus message I should send to bring up the 3G > > connectivity ? > > > > Thanks > > > > Hong > > sounds pretty shortsighted, considering that the internet contains many more > things than http... > > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re:GSM modem enable failed: (32) Failed to find a usable modem character set
Hi, > Hi, > I had been trying to connect my SAMSUNG Mobile USB Modem. I had the > same problem. I could successfully hack Networkmanager and Modemmanager > to support my device. > My problem became bit more complex. I checked the specific laptop a bit more. I removed the SIM card and put it into my mobile phone to verify if the SIM is OK. Everything was fine there. So I put it back into the laptop. Now I cannot reproduce the error any more on that system! Anyway. As I told before, we are currently in rollout of a big number of Linux Systems (~5000) using NetworkManager. They are all the same model: Lenovo Thinkpad T61 with an embedded Sierra Modem MC8775. This should be perfectly supported by. In the last days I'm getting more and more error reports from our user helpdesk because our users in the field are running into big issues when they using the internal modem. I have divided the several reports (currently we are getting about 20 per day) into these categories: 1. The user is not able to bring up the system-connection: In this situation the user is trying to establish a broadband connection by selecting the system-connection in nm-applet. It looks like that the connection will be initialized but at the end the user is getting a connection error (like "... disconnected" or "... failed"). Sometimes it helps to disable the modem using the rfkill switch. Our support staff found some log entries in syslog like "carrier lost" or "failed to find a usable modem character set" have a look 2. The connection is up but no data transfer is possible The user is able to establish a mobile connection. The ppp0 interface get's an ip and I can see the login on my central radius server. But no IP communication is possible. I have seen the situation today with one customer in the field. He had a connection based on EDGE but I was not able to ping the remote system. 3. The modem is not recognized by modemmanager. The user cannot establish the mobile connection because it is not in the list. He has to use the hw-rfkill switch in front of his laptop to powercycle the modem. Then the modem-manager is able to find the modem and the connection is in the nm-applet list. > My guess is that your 3g based modem not supported by currently > available modem manager plug-ins and generic GSM plug-in is not working > for you. > If you really want to support the modem you can roll your own and hack > it. Just comment out few places where modem manager checks for the best > character set; so that it works fine even if it is horrid, and > evil.(Just what I did- It may not be right way) At the end this might be a solution. But I don't believe that the existing sierra_plugin is so broken. > > For debugging, you can make following arrangements. > 1.Remove NM from upstart -Otherwise it keep on re-spawning and makes > difficult to debug > 2.Kill NM - stop currently running instance > 3.Kill modem manager > 4.Launch modem manager on a debugger with break points (may be > mm-generic-gsm.c: mm_generic_gsm_enable_complete a good place to start) > 5.Launch NM on separate terminal with --no-daemon A more generic debug option in network-manager / modem-manager would be very helpful. The problem is that all the systems are spread all over germany. So I cannot debug them in your suggested way. I need to use the distribution specific upstart job for starting the components in debug mode. Currently I'm trying to find a way doing this in upstart. But It's not so easy. A more generic debug option would be very helpful (see my last post: http://mail.gnome.org/archives/networkmanager-list/2010-September/msg00036.html) > > All the best I really need it! > -shakthi HG ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
GSM modem enable failed: (32) Failed to find a usable modem character set
Hi, I asked for a generic debug mechanism for network-manager / modem-manager. The reason for my request is that we get a big number of different connection issues with network-manager / modem-manger. One of the problem is now reproducable by me. When trying to bring up the 3g based systemconnection I get the following error: GSM modem enable failed: (32) Failed to find a usable modem character set I have put the full debug output on pastebin: http://pastebin.com/PaE8LYUJ I'm using the following versions: network-manager 1:0.8.1~git.20100526t083526.8bd5168-1 modemmanager1:0.3.1~git.20100525t222447.6c3ae7d-1 Thank you! ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
debugging networkmanager
Hi, would it be possible to write networkmanager / modemmanager debug output to syslog based on a configuration option? We are currently in rollout of a big number of Linux systems. Our support team gets more and more reports of problems in mobile environment. Users are not able to get their 3g based connection working and so on. Therefore I would like to enable debug on a wide number of machines in the field. One possibillity is to modify the upstart script for networkmanager but I think it would be a good idea to have a generic debug mechanism based on a config option. What do you think? ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: resolv.conf reproducable empty when connected to ethernet and 3g and disconnect from 3g
Am 29.07.2010 um 00:02 schrieb Dan Williams : > On Wed, 2010-07-28 at 11:01 +0200, van Schelve Hans-Gerd wrote: >> >> Am 28.07.2010 um 11:10 schrieb Dan Williams : >> >>> On Tue, 2010-07-27 at 09:53 +0200, van Schelve Hans-Gerd wrote: >>>> >>>> Am 23.07.2010 um 01:39 schrieb Dan Williams : >>>> >>>>> On Wed, 2010-07-21 at 08:45 +0200, van Schelve wrote: >>>>>> Hi. >>>>>> >>>>>> We found a reproducable bug with NetworkManager. In the end you have a >>>>>> connection but resolv.conf is empty and. >>>>>> >>>>>> How to reproduce: >>>>>> >>>>>> * establish a mobile broadband connection (make sure everything else is >>>>>> disconnected) >>>>>> * Connect to ethernet in parallel >>>>>> * disconnect from mobile broadband connection >>>>>> * check /etc/resolv.conf. The file will not contain any dns server >>>>>> >>>>>> Please tell me if you need further information. >>>>> >>>>> I can't reproduce with the new NM 0.8.1 release using plain resolv.conf. >>>>> Are you using a system with resolvconf or netconf enabled? >>>>> >>>> >>>> Dan, What do you mean with a resolvconf or netconf enabled System? >>> >>> i.e. Debian (resolvconf) or SUSE (netconf). If you have the resolvconf >>> or netconf binaries installed, then you're probably using them. If you >>> don't, then NM is probably set up to talk directly to /etc/resolv.conf. >>> >>> Dan >> >> >> Ah, ok. I checked my ubuntu based system. There is no netconf or resolvconf >> Package installed. > > Ok, at this point we need to do more debugging internally then. Are you > able to rebuild the Ubuntu NM package? If so, please do that and see if > you can reproduce the problem. If you can still reproduce it with your > rebuilt package, then we can add a patch to print out what's going on in > src/named-manager/ and isolate your issue. > Sure. It's build from git source by us. > Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: resolv.conf reproducable empty when connected to ethernet and 3g and disconnect from 3g
Am 28.07.2010 um 11:10 schrieb Dan Williams : > On Tue, 2010-07-27 at 09:53 +0200, van Schelve Hans-Gerd wrote: >> >> Am 23.07.2010 um 01:39 schrieb Dan Williams : >> >>> On Wed, 2010-07-21 at 08:45 +0200, van Schelve wrote: >>>> Hi. >>>> >>>> We found a reproducable bug with NetworkManager. In the end you have a >>>> connection but resolv.conf is empty and. >>>> >>>> How to reproduce: >>>> >>>> * establish a mobile broadband connection (make sure everything else is >>>> disconnected) >>>> * Connect to ethernet in parallel >>>> * disconnect from mobile broadband connection >>>> * check /etc/resolv.conf. The file will not contain any dns server >>>> >>>> Please tell me if you need further information. >>> >>> I can't reproduce with the new NM 0.8.1 release using plain resolv.conf. >>> Are you using a system with resolvconf or netconf enabled? >>> >> >> Dan, What do you mean with a resolvconf or netconf enabled System? > > i.e. Debian (resolvconf) or SUSE (netconf). If you have the resolvconf > or netconf binaries installed, then you're probably using them. If you > don't, then NM is probably set up to talk directly to /etc/resolv.conf. > > Dan Ah, ok. I checked my ubuntu based system. There is no netconf or resolvconf Package installed. HG ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: resolv.conf reproducable empty when connected to ethernet and 3g and disconnect from 3g
Am 23.07.2010 um 01:39 schrieb Dan Williams : > On Wed, 2010-07-21 at 08:45 +0200, van Schelve wrote: >> Hi. >> >> We found a reproducable bug with NetworkManager. In the end you have a >> connection but resolv.conf is empty and. >> >> How to reproduce: >> >> * establish a mobile broadband connection (make sure everything else is >> disconnected) >> * Connect to ethernet in parallel >> * disconnect from mobile broadband connection >> * check /etc/resolv.conf. The file will not contain any dns server >> >> Please tell me if you need further information. > > I can't reproduce with the new NM 0.8.1 release using plain resolv.conf. > Are you using a system with resolvconf or netconf enabled? > Dan, What do you mean with a resolvconf or netconf enabled System? How do i find that out? HG ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
resolv.conf reproducable empty when connected to ethernet and 3g and disconnect from 3g
Hi. We found a reproducable bug with NetworkManager. In the end you have a connection but resolv.conf is empty and. How to reproduce: * establish a mobile broadband connection (make sure everything else is disconnected) * Connect to ethernet in parallel * disconnect from mobile broadband connection * check /etc/resolv.conf. The file will not contain any dns server Please tell me if you need further information. NetworkManager (version 0.8.0.997) ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: problems with 3g based connections
Am Donnerstag, den 15.07.2010, 02:00 +0200 schrieb Dan Williams : > On Mon, 2010-07-05 at 08:42 +0200, van Schelve wrote: >> >> Hi, >> >> >> >> some days ago I have reported a curious issue with modem-manager. >> >> My main Problem is that I'm sometimes not able to dialup a modem based >> 3g >> >> connection. The connection is not listed in nm-applet in this case and >> in >> >> syslog I have entries like this one: >> >> >> >> ... >> >> May 21 10:055:28 nc0631 modem-manager: (tty/ttyUSB0): outstanding >> support >> >> task prevents export of /sys/devices/pci:00/:00:1d.1/usb6/6-1 >> >> ... >> > >> > This means that some ports of the modem are still being detected and >> > probed. The modem cannot be used until all ports have completed >> > detection. >> > >> >> @Dan, you asked me to bring more debug but I'm not able to reproduce >> this >> >> issue while manually starting nm / mm in debug mode. >> >> Therefore: is it possible to run network-manager / modem-manager per >> >> default in debug mode while starting over upstart? >> > >> > Possibly, but the debug output doesn't go to syslog, so unless it gets >> > stored somewhere by upstart it'll get lost. >> >> We were able to capture the debug output. Without debug we run 6 of 10 >> times into >> this problem. Running mm in debug mode we were able to reproduce it 3 of >> 10 times. >> >> http://pastebin.com/RS5vDxwJ >> http://pastebin.com/FmZbkJnc >> http://pastebin.com/97GPPbZW > > This is good stuff; near the end of the log entries you'll see: > > ** (modem-manager:1054): DEBUG: <1278077341.1209> (ttyUSB1): --> 00 78 f0 > 7e > ** (modem-manager:1054): DEBUG: <1278077342.610807> (ttyUSB1): <-- 7e 00 > 0a 6b 24 00 00 07 00 00 00 00 00 00 00 7e > ** (modem-manager:1054): DEBUG: <1278077349.610774> (ttyUSB1): <-- 7e 00 > 0a 6b 25 00 00 07 00 00 00 00 00 00 00 7e > ** (modem-manager:1054): DEBUG: <1278077356.610695> (ttyUSB1): <-- 7e 00 > 0a 6b 26 00 00 07 00 00 00 00 00 00 00 7e > ** (modem-manager:1054): DEBUG: <1278077363.610729> (ttyUSB1): <-- 7e 00 > 0a 6b 27 00 00 07 00 00 00 00 00 00 00 7e > ** (modem-manager:1054): DEBUG: <1278077370.610737> (ttyUSB1): <-- 7e 00 > 0a 6b 28 00 00 07 00 00 00 00 00 00 00 7e > ** (modem-manager:1054): DEBUG: <1278077377.606758> (ttyUSB1): <-- 7e 00 > 0a 6b 29 00 00 07 00 00 00 00 00 00 00 7e > > so ttyUSB1 is a Sierra CnS port (their "Control and Status" protocol) > and MM isn't correctly failing out the QCDM probe. What modem is this > again? > Dan, you're right. It is the CnS port of the Sierra Wireless MC8775. And I think we found the reason for the problem. In addition to all the networkmanager components we have a special application, called wsm, that displays several informations from the modem like signal strenth, cell information active band, firmware version, hardware version. These information are taken via CnS. We have disabled this tool and did some further tests with the result that in 50 / 50 tries everything works fine. So we decided to remove the wsm tool from users autostart and hope that we will get the cell information in the future direct from nm-applet. But if you are intereted in our tool, I can send it to you via pm. It's GPL code. Sorry for reporting a non existing issue! HG ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: problems with 3g based connections
>> Hi, >> >> some days ago I have reported a curious issue with modem-manager. >> My main Problem is that I'm sometimes not able to dialup a modem based 3g >> connection. The connection is not listed in nm-applet in this case and in >> syslog I have entries like this one: >> >> ... >> May 21 10:055:28 nc0631 modem-manager: (tty/ttyUSB0): outstanding support >> task prevents export of /sys/devices/pci:00/:00:1d.1/usb6/6-1 >> ... > > This means that some ports of the modem are still being detected and > probed. The modem cannot be used until all ports have completed > detection. > >> @Dan, you asked me to bring more debug but I'm not able to reproduce this >> issue while manually starting nm / mm in debug mode. >> Therefore: is it possible to run network-manager / modem-manager per >> default in debug mode while starting over upstart? > > Possibly, but the debug output doesn't go to syslog, so unless it gets > stored somewhere by upstart it'll get lost. We were able to capture the debug output. Without debug we run 6 of 10 times into this problem. Running mm in debug mode we were able to reproduce it 3 of 10 times. http://pastebin.com/RS5vDxwJ http://pastebin.com/FmZbkJnc http://pastebin.com/97GPPbZW > >> A second problem, reported by our testorganisation is that existing >> connections are sometimes terminated. I cannot see the reason for this >> behaviour. > > Getting logs from modem-manager and from NetworkManager with > NM_PPP_DEBUG=1 are helpful here: > > http://live.gnome.org/NetworkManager/Debugging > > I'd guess that PPP is terminating for some reason, but we need to figure > out why that is, and the NM PPP debug logs might help us figure that > out. There are a ton of reasons why the call might get terminated, and > many of them are network side or handoff-related. Or the firmware > screws up. This happens on other platforms too :) > >> And maybe there is a third problem. It looks like that it takes a long >> time ~6 seconds from powering up the modem until it can be used with >> network-manager. In the logfiles I see that the different ports are >> getting >> probed with all the available plugins. Is there any way to optimize this >> behaviour? > > What do you mean by "powering up"? Just plugging the modem in? The Lenovo Laptops have a switch to disable / enable the radio devices at all once. So it looks like it's like plugging the modem in. > > You might also be forgetting about modeswitching, which takes a few > seconds (perhaps up to 5 or 7) depending on the device. Otherwise, > there might be a few things we can do to eliminate delays, but you'll > also find that on other platforms things take a while to initialize too. > That doesn't mean we can't do better than we do right now, but there > will always be some amount of delay as the device is modeswitched, > detected, and initialized. Ok, I understand. I will do some measurings to determinate how long it took with our old wvdial script and the new nm / mm implementation. > > Getting the ModemManager debug logs help here. Here it is: http://pastebin.com/jLGNrjNq > > Note that some devices (Airlink 3GU and other Longcheer-based modems) > have kernel driver problems that delay their detection by up to 30 or > more seconds. > > Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
problems with 3g based connections
Hi, some days ago I have reported a curious issue with modem-manager. My main Problem is that I'm sometimes not able to dialup a modem based 3g connection. The connection is not listed in nm-applet in this case and in syslog I have entries like this one: ... May 21 10:055:28 nc0631 modem-manager: (tty/ttyUSB0): outstanding support task prevents export of /sys/devices/pci:00/:00:1d.1/usb6/6-1 ... @Dan, you asked me to bring more debug but I'm not able to reproduce this issue while manually starting nm / mm in debug mode. Therefore: is it possible to run network-manager / modem-manager per default in debug mode while starting over upstart? A second problem, reported by our testorganisation is that existing connections are sometimes terminated. I cannot see the reason for this behaviour. And maybe there is a third problem. It looks like that it takes a long time ~6 seconds from powering up the modem until it can be used with network-manager. In the logfiles I see that the different ports are getting probed with all the available plugins. Is there any way to optimize this behaviour? Best regards, -- Hans-Gerd ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: modemmanager broken?
Am Mittwoch, den 02.06.2010, 08:53 +0200 schrieb Dan Williams : > On Mon, 2010-05-31 at 10:17 +0200, wp1191918-hgvs wrote: >> Hi, >> >> I have updated network-manager, network-manager-applet and modem-manager >> to the following git versions: >> modemmanager 1:0.3.1~git.20100525t222447.6c3ae7d-1hgvs >> network-manager 1:0.8.1~git.20100526t083526.8bd5168-1hgvs >> network-manager-gnome1:0.8.1~git.20100526t065235.25dedfb-1hgvs >> >> Now I have the problem, that the internal sierra 3g modem does not get >> initialized by modem-manager. In /var/log/syslog I see the following >> looping messages: >> >> . >> May 31 10:05:28 nc0631 modem-manager: (tty/ttyUSB0): outstanding support >> task prevents export of /sys/devices/pci:00/:00:1d.1/usb6/6-1 >> May 31 10:05:28 nc0631 modem-manager: (tty/ttyUSB0): outstanding support >> task prevents export of /sys/devices/pci:00/:00:1d.1/usb6/6-1 >> . >> >> The complete syslog is on patebin.com: >> >> http://pastebin.com/download.php?i=HW39cShc >> >> The interesting thing is: it sometimes work but sometimes not. It looks >> like that everything is fine when first starting network-manager / >> modem-manager >> and then enable the device. When I change this sequence - first starting >> the device, then starting nm / mm it fails. > > Is there any chance you could run modem-manager with --debug for me? > > 1) stop NM > 2) killall -TERM modem-manager > 3) modem-manager --debug > 4) start NM > 5) reproduce the problem > > so we can see what's stopping ttyUSB0 in that log from being handled by > Sierra? This part isn't supposed to happen: > > May 31 10:05:28 nc0631 modem-manager: (ttyUSB0): probe requested by plugin > 'Generic' > > since the same device that provides ttyUSB0 also also provides ttyUSB2 > and the other ports. > > Dan > Hi Dan, Unfortunately I am not be able to reproduce the issue while running in debug mode. The most situations are after a cold boot. The first indicator is that the 3g connection is not listed in nm-applet. Another situation is while performing an undock sequence with my laptop. Before undocking everything is fine, but after the laptop is out of the dock nm-applet does not list the mobile connection. A third problem is that it takes a long time after power on the internal modem until it can be used to dial up. Is there a way to modify the upstart initscript to enable debug there? Hans-Gerd > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: BT DUN based systemconnections in 0.8.1 beta
Am Mittwoch, den 26.05.2010, 11:01 +0200 schrieb Dan Williams : > On Tue, 2010-05-25 at 15:01 +0200, van Schelve wrote: >> Am Dienstag, den 25.05.2010, 14:39 +0200 schrieb Bastien Nocera >> : >> > On Tue, 2010-05-25 at 13:11 +0200, van Schelve wrote: >> >> Hi, >> >> >> >> I'm still having problems with bluetooth dun based system connections >> in >> >> 0.8.1 beta: >> >> >> >> 1. No ui in nm-applet is available >> >> 2. if created from scratch as system-connection they not shown in >> >> nm-applet >> >> >> >> With cnetworkmanager I'm able to list such a connection but I'm not >> able >> >> to bring it up with >> >> this tool. In this context, can someone explain the commandline >> interface >> >> of networkmanager to me? >> >> >> >> On http://live.gnome.org/NetworkManager/ReleaseProcess I found that BT >> >> DUN >> >> should be included >> >> in the 0.8.1 release. Can someone clarify this? If dun >> systemconnections >> >> are not part of 0.8.1 release >> >> can someone tell me what's missing? >> > >> > You need to pair your device using gnome-bluetooth's wizard, and the >> > wizard to set up DUN will appear on the last page. >> > >> > Cheers >> >> Hi Bastien, >> thank you for your reply but that's not what I'm looking for. What I need >> is >> a systemconnection that can be stored in >> /etc/NetworkManager/system-connections/ >> like it can be done with 3G based as well. On the other hand there is >> nothing >> in nm-applet to modify a exiisting bluetooth connection. So for example >> if >> you >> have different APN's you cannot easy change it. > > With 0.8.1-beta2 (just uploaded) you can use the following syntax: > > http://cgit.freedesktop.org/NetworkManager/NetworkManager/plain/system-settings/plugins/keyfile/tests/keyfiles/ATT_Data_Connect_BT?id=d422ce42c400611369a6951bbc9dc012515a3e5b > > of course, the device has to be paired with Bluez (or some bluetooth > manager like gnome-bluetooth) first. > > Dan Hi Dan, I checked out the latest git versions and it really works now. Thank you for this! I will do intensive testing in the next days. Hans-Gerd ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: BT DUN based systemconnections in 0.8.1 beta
Am Dienstag, den 25.05.2010, 14:39 +0200 schrieb Bastien Nocera : > On Tue, 2010-05-25 at 13:11 +0200, van Schelve wrote: >> Hi, >> >> I'm still having problems with bluetooth dun based system connections in >> 0.8.1 beta: >> >> 1. No ui in nm-applet is available >> 2. if created from scratch as system-connection they not shown in >> nm-applet >> >> With cnetworkmanager I'm able to list such a connection but I'm not able >> to bring it up with >> this tool. In this context, can someone explain the commandline interface >> of networkmanager to me? >> >> On http://live.gnome.org/NetworkManager/ReleaseProcess I found that BT >> DUN >> should be included >> in the 0.8.1 release. Can someone clarify this? If dun systemconnections >> are not part of 0.8.1 release >> can someone tell me what's missing? > > You need to pair your device using gnome-bluetooth's wizard, and the > wizard to set up DUN will appear on the last page. > > Cheers Hi Bastien, thank you for your reply but that's not what I'm looking for. What I need is a systemconnection that can be stored in /etc/NetworkManager/system-connections/ like it can be done with 3G based as well. On the other hand there is nothing in nm-applet to modify a exiisting bluetooth connection. So for example if you have different APN's you cannot easy change it. HG ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
BT DUN based systemconnections in 0.8.1 beta
Hi, I'm still having problems with bluetooth dun based system connections in 0.8.1 beta: 1. No ui in nm-applet is available 2. if created from scratch as system-connection they not shown in nm-applet With cnetworkmanager I'm able to list such a connection but I'm not able to bring it up with this tool. In this context, can someone explain the commandline interface of networkmanager to me? On http://live.gnome.org/NetworkManager/ReleaseProcess I found that BT DUN should be included in the 0.8.1 release. Can someone clarify this? If dun systemconnections are not part of 0.8.1 release can someone tell me what's missing? Thank you! Hans-Gerd ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Re: domainname in serviceproviders.xml
On Mon, 12 Apr 2010 20:52:07 +0200, van Schelve wrote: > On Thu, 08 Apr 2010 16:40:21 -0700, Dan Williams wrote: >> On Wed, 2010-04-07 at 00:27 +0200, Hans-Gerd van Schelve wrote: >>> >>> Am 06.04.2010 um 22:16 schrieb Dan Williams : >>> >>> > On Tue, 2010-04-06 at 20:43 +0200, Hans-Gerd van Schelve wrote: >>> >> Hi. >>> >> >>> >> It looks like that nm is still not able to read bluetooth >>> >> connections from >>> >> system-connection files. I tested this sometimes but it does not >>> >> work. So >>> >> I'm looking for a workaround currently. Our users are not able to >>> >> use their >>> >> SIM cards with any APN. These SIM cards are configured by our >>> >> provider to >>> >> only allow to use our own private APN. So I'm modifying the >>> >> following file: >>> >> /usr/share/mobile-broadband-provider-info/serviceproviders.xml so >>> >> the user >>> >> can only select our APN configuration. My Problem is that the domain >>> >> extension is ignored in this file. I tried mycompany.de>> >> domain> >>> >> but that does not work. Can someone give me a hint? >>> > >>> > That file doesn't have anything to do with or anything. What >>> > are you trying to do here? >>> >>> I added our custom apn entry there so our user can select it from the >>> list and removed all the other entries that do not work for us and >>> therefore should not be available >> >> Ok, that should work. If you remove everything from that file except >> your custom APN, it should be the only one shown in the wizard. > > Hm. No, it's not really possible as I thought first. The missing dns > search > option is one thing. I have to change the resolve.conf to search > mycompany.com > and that's not possible. Second thing is that our user are able to see the > ppp > credentials for username and password. Therefore the system-connection > would be > the best solution. >> >>> > serviceproviders.xml only handles APNs >>> > really (DNS is ignored since it's passed back from PPP). If you >>> > want to >>> > control the search domains, then you'll want modify the NM connection >>> > itself. >>> > >>> > If there's a problem with BT system connections, we should fix > that... >>> >>> Agree. This would be the best. Can I contribute something like special > >>> debug that can help to fix it? >> >> Can you grab the NM log output for me? And possibly 'dmesg' so we can >> see if the kernel is misbehaving. > > Of course. You'll find them at pastebin: > http://pastebin.org/148605 > http://pastebin.org/148608 Dan, are these logs useful? Is someone else here who can reproduce the problem? Can I contribute something else? > >> >> Dan >> > > HG > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Re: domainname in serviceproviders.xml
On Thu, 08 Apr 2010 16:40:21 -0700, Dan Williams wrote: > On Wed, 2010-04-07 at 00:27 +0200, Hans-Gerd van Schelve wrote: >> >> Am 06.04.2010 um 22:16 schrieb Dan Williams : >> >> > On Tue, 2010-04-06 at 20:43 +0200, Hans-Gerd van Schelve wrote: >> >> Hi. >> >> >> >> It looks like that nm is still not able to read bluetooth >> >> connections from >> >> system-connection files. I tested this sometimes but it does not >> >> work. So >> >> I'm looking for a workaround currently. Our users are not able to >> >> use their >> >> SIM cards with any APN. These SIM cards are configured by our >> >> provider to >> >> only allow to use our own private APN. So I'm modifying the >> >> following file: >> >> /usr/share/mobile-broadband-provider-info/serviceproviders.xml so >> >> the user >> >> can only select our APN configuration. My Problem is that the domain >> >> extension is ignored in this file. I tried mycompany.de> >> domain> >> >> but that does not work. Can someone give me a hint? >> > >> > That file doesn't have anything to do with or anything. What >> > are you trying to do here? >> >> I added our custom apn entry there so our user can select it from the >> list and removed all the other entries that do not work for us and >> therefore should not be available > > Ok, that should work. If you remove everything from that file except > your custom APN, it should be the only one shown in the wizard. Hm. No, it's not really possible as I thought first. The missing dns search option is one thing. I have to change the resolve.conf to search mycompany.com and that's not possible. Second thing is that our user are able to see the ppp credentials for username and password. Therefore the system-connection would be the best solution. > >> > serviceproviders.xml only handles APNs >> > really (DNS is ignored since it's passed back from PPP). If you >> > want to >> > control the search domains, then you'll want modify the NM connection >> > itself. >> > >> > If there's a problem with BT system connections, we should fix that... >> >> Agree. This would be the best. Can I contribute something like special >> debug that can help to fix it? > > Can you grab the NM log output for me? And possibly 'dmesg' so we can > see if the kernel is misbehaving. Of course. You'll find them at pastebin: http://pastebin.org/148605 http://pastebin.org/148608 > > Dan > HG ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Re: domainname in serviceproviders.xml
On Thu, 08 Apr 2010 16:40:21 -0700, Dan Williams wrote: > On Wed, 2010-04-07 at 00:27 +0200, Hans-Gerd van Schelve wrote: >> >> Am 06.04.2010 um 22:16 schrieb Dan Williams : >> >> > On Tue, 2010-04-06 at 20:43 +0200, Hans-Gerd van Schelve wrote: >> >> Hi. >> >> >> >> It looks like that nm is still not able to read bluetooth >> >> connections from >> >> system-connection files. I tested this sometimes but it does not >> >> work. So >> >> I'm looking for a workaround currently. Our users are not able to >> >> use their >> >> SIM cards with any APN. These SIM cards are configured by our >> >> provider to >> >> only allow to use our own private APN. So I'm modifying the >> >> following file: >> >> /usr/share/mobile-broadband-provider-info/serviceproviders.xml so >> >> the user >> >> can only select our APN configuration. My Problem is that the domain >> >> extension is ignored in this file. I tried mycompany.de> >> domain> >> >> but that does not work. Can someone give me a hint? >> > >> > That file doesn't have anything to do with or anything. What >> > are you trying to do here? >> >> I added our custom apn entry there so our user can select it from the >> list and removed all the other entries that do not work for us and >> therefore should not be available > > Ok, that should work. If you remove everything from that file except > your custom APN, it should be the only one shown in the wizard. Hm. No, it's not really possible as I thought first. The missing dns search option is one thing. I have to change the resolve.conf to search mycompany.com and that's not possible. Second thing is that our user are able to see the ppp credentials for username and password. Therefore the system-connection would be the best solution. > >> > serviceproviders.xml only handles APNs >> > really (DNS is ignored since it's passed back from PPP). If you >> > want to >> > control the search domains, then you'll want modify the NM connection >> > itself. >> > >> > If there's a problem with BT system connections, we should fix that... >> >> Agree. This would be the best. Can I contribute something like special >> debug that can help to fix it? > > Can you grab the NM log output for me? And possibly 'dmesg' so we can > see if the kernel is misbehaving. Of course. You'll find them at pastebin: http://pastebin.org/148605 http://pastebin.org/148608 > > Dan > HG ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: domainname in serviceproviders.xml
Am 06.04.2010 um 22:16 schrieb Dan Williams : On Tue, 2010-04-06 at 20:43 +0200, Hans-Gerd van Schelve wrote: Hi. It looks like that nm is still not able to read bluetooth connections from system-connection files. I tested this sometimes but it does not work. So I'm looking for a workaround currently. Our users are not able to use their SIM cards with any APN. These SIM cards are configured by our provider to only allow to use our own private APN. So I'm modifying the following file: /usr/share/mobile-broadband-provider-info/serviceproviders.xml so the user can only select our APN configuration. My Problem is that the domain extension is ignored in this file. I tried mycompany.dedomain> but that does not work. Can someone give me a hint? That file doesn't have anything to do with or anything. What are you trying to do here? I added our custom apn entry there so our user can select it from the list and removed all the other entries that do not work for us and therefore should not be available serviceproviders.xml only handles APNs really (DNS is ignored since it's passed back from PPP). If you want to control the search domains, then you'll want modify the NM connection itself. If there's a problem with BT system connections, we should fix that... Agree. This would be the best. Can I contribute something like special debug that can help to fix it? Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: domainname in serviceproviders.xml
Am 06.04.2010 um 22:16 schrieb Dan Williams : > On Tue, 2010-04-06 at 20:43 +0200, Hans-Gerd van Schelve wrote: >> Hi. >> >> It looks like that nm is still not able to read bluetooth >> connections from >> system-connection files. I tested this sometimes but it does not >> work. So >> I'm looking for a workaround currently. Our users are not able to >> use their >> SIM cards with any APN. These SIM cards are configured by our >> provider to >> only allow to use our own private APN. So I'm modifying the >> following file: >> /usr/share/mobile-broadband-provider-info/serviceproviders.xml so >> the user >> can only select our APN configuration. My Problem is that the domain >> extension is ignored in this file. I tried mycompany.de> domain> >> but that does not work. Can someone give me a hint? > > That file doesn't have anything to do with or anything. What > are you trying to do here? I added our custom apn entry there so our user can select it from the list and removed all the other entries that do not work for us and therefore should not be available > serviceproviders.xml only handles APNs > really (DNS is ignored since it's passed back from PPP). If you > want to > control the search domains, then you'll want modify the NM connection > itself. > > If there's a problem with BT system connections, we should fix that... Agree. This would be the best. Can I contribute something like special debug that can help to fix it? > > Dan > > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
domainname in serviceproviders.xml
Hi. It looks like that nm is still not able to read bluetooth connections from system-connection files. I tested this sometimes but it does not work. So I'm looking for a workaround currently. Our users are not able to use their SIM cards with any APN. These SIM cards are configured by our provider to only allow to use our own private APN. So I'm modifying the following file: /usr/share/mobile-broadband-provider-info/serviceproviders.xml so the user can only select our APN configuration. My Problem is that the domain extension is ignored in this file. I tried mycompany.de but that does not work. Can someone give me a hint? Thanks! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
domainname in serviceproviders.xml
Hi. It looks like that nm is still not able to read bluetooth connections from system-connection files. I tested this sometimes but it does not work. So I'm looking for a workaround currently. Our users are not able to use their SIM cards with any APN. These SIM cards are configured by our provider to only allow to use our own private APN. So I'm modifying the following file: /usr/share/mobile-broadband-provider-info/serviceproviders.xml so the user can only select our APN configuration. My Problem is that the domain extension is ignored in this file. I tried mycompany.de but that does not work. Can someone give me a hint? Thanks! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Core dump with nm-applet
Hi. I've installed nm, nm-applet and mm from git. Now when when either click on "Connect to Hidden Wireless network..." or "Create New Wireless Network..." nm-applet core dumps: m525...@nc0631:~/lap-devel/lvm-printing-base/src$ nm-applet (nm-applet:19849): GLib-GObject-WARNING **: invalid (NULL) pointer instance (nm-applet:19849): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (nm-applet:19849): Gtk-CRITICAL **: gtk_combo_box_set_model: assertion `GTK_IS_COMBO_BOX (combo_box)' failed (nm-applet:19849): Gtk-CRITICAL **: gtk_combo_box_set_active: assertion `GTK_IS_COMBO_BOX (combo_box)' failed (nm-applet:19849): GLib-GObject-WARNING **: invalid (NULL) pointer instance (nm-applet:19849): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (nm-applet:19849): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed (nm-applet:19849): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed (nm-applet:19849): Gtk-CRITICAL **: gtk_cell_layout_clear: assertion `GTK_IS_CELL_LAYOUT (cell_layout)' failed (nm-applet:19849): Gtk-CRITICAL **: gtk_cell_layout_pack_start: assertion `GTK_IS_CELL_LAYOUT (cell_layout)' failed (nm-applet:19849): Gtk-CRITICAL **: gtk_cell_layout_add_attribute: assertion `GTK_IS_CELL_LAYOUT (cell_layout)' failed (nm-applet:19849): Gtk-CRITICAL **: gtk_combo_box_set_wrap_width: assertion `GTK_IS_COMBO_BOX (combo_box)' failed (nm-applet:19849): Gtk-CRITICAL **: gtk_combo_box_set_model: assertion `GTK_IS_COMBO_BOX (combo_box)' failed (nm-applet:19849): Gtk-CRITICAL **: gtk_combo_box_set_row_separator_func: assertion `GTK_IS_COMBO_BOX (combo_box)' failed (nm-applet:19849): Gtk-CRITICAL **: gtk_combo_box_set_active: assertion `GTK_IS_COMBO_BOX (combo_box)' failed (nm-applet:19849): GLib-GObject-WARNING **: invalid (NULL) pointer instance (nm-applet:19849): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** (nm-applet:19849): CRITICAL **: security_combo_init: assertion `priv->sec_combo != NULL' failed ** (nm-applet:19849): WARNING **: Couldn't set up wireless security combo box. ** (nm-applet:19849): WARNING **: internal_new_other(): Couldn't create wireless security dialog. (nm-applet:19849): GLib-GObject-WARNING **: instance with invalid (NULL) class pointer (nm-applet:19849): GLib-GObject-CRITICAL **: g_signal_handlers_destroy: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed Segmentation fault (core dumped) Shall I open a bug for this or is it already known? Hans-Gerd ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: gui design of nm-applet
On Tue, 23 Mar 2010 02:40:29 -0700, Dan Williams wrote: > On Fri, 2010-03-19 at 21:23 +0100, Hans-Gerd van Schelve wrote: >> On Wed, 10 Mar 2010 17:50:03 +0100, van Schelve >> wrote: >> > On Tue, 09 Mar 2010 16:55:35 -0800, Dan Williams >> wrote: >> >> On Mon, 2010-03-08 at 13:24 +0100, van Schelve wrote: >> >>> We are planning to rollout NM > 0.8 to a very! big number of mobile >> > Linux >> >>> systems. Our different usecases for NM are Ethernet, 3G datacards, >> >>> bluetooth based 3g and in small numbers wlan as well. >> >>> >> >>> Today we had a discussion about nm-applet in our companay. We are >> > worried >> >>> about our user get overcharge with the usability of nm-applet. The >> >>> biggest >> >>> painpoint we talked about in this context is way nm presents the >> >>> available >> >>> devices, available connections and the active connections. >> >>> >> >>> The horizontal separator should be removed from nm-applet. It looks >> > like >> >>> a >> >>> logical separator between different connection types. >> >> >> >> Hmm, the indentation was supposed to help make that clearer. The >> >> problem is that we do need a mechanism to distinguish between the >> >> "current" network connection for that device and it's associated >> actions >> >> (like disconnect) and the other available connections. Unfortunately >> >> we're currently stuck in a GtkMenu widget where we can't control the >> >> layout in a fine-grained manner without violating a lot of UI >> principles >> >> (since it is still a menu). >> >> >> >>> Maybe it could be a way using differnt font size / weight? Or maybe >> >>> indenting blockwise? >> >> >> >> It might work to make the "available" text in the line smaller perhaps >> >> to differentiate it more from the surrounding text? >> >> >> > >> > What do you think about presenting the list in this way: >> One additional thing I thought about could be a "disconnect" entry >> in each section > > Right, but now you're getting dangeriously close to what we already > have :) When you start adding a Disconnect option, you then need to > physically separate that disconnect option somehow from the rest of the > available connections, because Disconnect isn't a connection and thus > shouldn't be grouped with the other connections unless there's some > visible separation. I don't think so. We discussed this once again. The disconnect option must be in the group because it is directly affected to the one open connection in this group. The line implicate a logical breakup. I tested this with a small number of colleagues that never have seen nm-applet. They all told me the same. They are confused about active connections, available connections and their first impression was that a line is a separation between two devices. > > Would simply making the - Available - text a bit smaller suffice > to reduce the open space? > > Dan Hans-Gerd > >> > >> > - >> > Wired Network >> > [ ] Auto eth0 (100Mit FD) >> disconnect from this device >> > - >> > Mobile Broadband >> > [x] MyCompany >> disconnect from this device >> > - >> > Nokia 6680 (Bluetooth) >> > [ ] MyCompany >> disconnect from this device >> > - >> > Wireless Network >> > [x] Foobar (83%) >> > [ ] blahfasel (60%) >> > [ ] muckebock (50%) >> > Connect to Hidden Wireless Network >> > Create New Wireless Network >> disconnect from this device >> > - >> > VPN >> > [ ] MyCompany (openvpn) >> > [ ] @Home (vpnc) >> disconnect vpn >> > >> > >> > The user is able to activate or deactivate a connection by clicking >> > into >> > a checkbox, or even better using a radio button because you can only >> have >> > one active connection for each physical device. The horizonal rules are >> > not >> > really necessary but I thought you like them ;-) >> > >&g
Re: NetworkManager-Ddispatcher preup / predown
>> Hi. >> >> I know about several discussions about pre-up and pre-down in the past. >> Dan, I understand your position and I can follow your arguments against. > > Yes, I realize there are use-cases where such operations would be nice > to have, and I'm open to it. I haven't gotten around to reviewing the > patch yet though, and it's a fairly major change to the flow of things > so it's not something to be undertaken lightly. > >> But I see a number of usecases where I dont have any idea instead of >> doing >> it with pre-up / pre-down scripts in nm-dispatcher. I know every script >> in >> these phases is a potential risk for nm functionality. From nm site you >> have no chance to control those scripts and it might be that users will >> come up with problem reports that are based on their own scripts. >> >> For example. We need to find solutions for these problems: >> 1. unmount cifs shares before a connection becomes disconnected > > Right, but remember that this is only possible *sometimes*. There will > always be times where the connection just died and no clean > disconnection is possible. I know. The example was using mounts over wlan. Bad Idea. Let's talk about Ethernet and laptops. Laptops can be either in a docked environment where the Ethernet cable is in the dock or they are direct connected. So what we would like to do is: automatically unmount existing mounts using acpi undock event based scripts (user has to press the dock button), unmount in the case a user suspend his laptop, or undock in pre-down phase. So if the user decides to unplug the Ethernet cable from his laptop **before** disconnecting from the network he has to live with a hanging system. We told him before. > But in cases where it's possible to do so, > we should probably try to give these operations at least a few seconds > to complete before killing the connection. Ok, if you are saying "a few seconds" then users should be able to configure the value for this in the global configuration. >> 2. stop any other active connection when a user select another one (maybe >> this can also be done in down event) to make sure the system is single >> homed > > I don't really see the value of this actually. In practice, the > multi-homing is not an issue and it should be transparent. Multi-homing > is also required for less interruption in network connections. If you > had to wait 30 seconds to connect to a wifi access point after > unplugging a cable every time, that's annoying. I'll also note that > Windows and Mac OS X have been multi-homed by default for years. > Yust one example: A user connects to 3g with his internal modem. The signal is bad and he decides to connnect via bluetooth cell phone (he can put it on a windowsill to get a better signal). So he has two ppp based connections active. How do we control that the bluetooth based is the preferred? >> 3. disconnect from the active vpn before the underlaying connection >> becomes disconnected > > Yes. > >> 4. start replication of the mail client before really disconnecting > > Yes, though this has the potential to take a really long time. How long > do we give something like this? I'm not sure I see a usable way to do > this sort of thing if you have say some megabytes of mail to pull over a > slow connection, for example. It might work some places, but certainly > not many other places like 3G connections. That's why I would do it only in Ethernet based connections > This one needs more thought > about what the workflow would be like. How does the user indicate their > desire to disconnect? How do we know how long they are willing to wait > before they really do want to take their laptop with them? etc. > >> Maybe I'm off the track looking fixed to pre-up / pre-down as solution >> for >> these problems. If so please point me onto the right way. > > Most of these are pre-down really; the major use-cases I've seen for > pre-up have been stuff like captive portal login scripts. I went > through all the pre-up and pre-down scripts in an Ubuntu install last > year, and 80% of them were completely bogus things like munging the wifi > attributes, or working around out-of-kernel wifi driver bugs, or other > stuff that no longer needs to be done. But there are some valid cases > like you suggest. > I'm really sure that I could give you a number of interesting use-caes but therefore it's necessary to have the whole picture about what we are doing. I can tell you: it's exciting... > Dan Hans-Gerd ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NetworkManager-Ddispatcher preup / predown
Hi. I know about several discussions about pre-up and pre-down in the past. Dan, I understand your position and I can follow your arguments against. But I see a number of usecases where I dont have any idea instead of doing it with pre-up / pre-down scripts in nm-dispatcher. I know every script in these phases is a potential risk for nm functionality. From nm site you have no chance to control those scripts and it might be that users will come up with problem reports that are based on their own scripts. For example. We need to find solutions for these problems: 1. unmount cifs shares before a connection becomes disconnected 2. stop any other active connection when a user select another one (maybe this can also be done in down event) to make sure the system is single homed 3. disconnect from the active vpn before the underlaying connection becomes disconnected 4. start replication of the mail client before really disconnecting Maybe I'm off the track looking fixed to pre-up / pre-down as solution for these problems. If so please point me onto the right way. Regards, Hans-Gerd ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: gui design of nm-applet
On Wed, 10 Mar 2010 17:50:03 +0100, van Schelve wrote: > On Tue, 09 Mar 2010 16:55:35 -0800, Dan Williams wrote: >> On Mon, 2010-03-08 at 13:24 +0100, van Schelve wrote: >>> We are planning to rollout NM > 0.8 to a very! big number of mobile > Linux >>> systems. Our different usecases for NM are Ethernet, 3G datacards, >>> bluetooth based 3g and in small numbers wlan as well. >>> >>> Today we had a discussion about nm-applet in our companay. We are > worried >>> about our user get overcharge with the usability of nm-applet. The >>> biggest >>> painpoint we talked about in this context is way nm presents the >>> available >>> devices, available connections and the active connections. >>> >>> The horizontal separator should be removed from nm-applet. It looks > like >>> a >>> logical separator between different connection types. >> >> Hmm, the indentation was supposed to help make that clearer. The >> problem is that we do need a mechanism to distinguish between the >> "current" network connection for that device and it's associated actions >> (like disconnect) and the other available connections. Unfortunately >> we're currently stuck in a GtkMenu widget where we can't control the >> layout in a fine-grained manner without violating a lot of UI principles >> (since it is still a menu). >> >>> Maybe it could be a way using differnt font size / weight? Or maybe >>> indenting blockwise? >> >> It might work to make the "available" text in the line smaller perhaps >> to differentiate it more from the surrounding text? >> > > What do you think about presenting the list in this way: One additional thing I thought about could be a "disconnect" entry in each section > > - > Wired Network > [ ] Auto eth0 (100Mit FD) disconnect from this device > - > Mobile Broadband > [x] MyCompany disconnect from this device > - > Nokia 6680 (Bluetooth) > [ ] MyCompany disconnect from this device > - > Wireless Network > [x] Foobar (83%) > [ ] blahfasel (60%) > [ ] muckebock (50%) > Connect to Hidden Wireless Network > Create New Wireless Network disconnect from this device > - > VPN > [ ] MyCompany (openvpn) > [ ] @Home (vpnc) disconnect vpn > > > The user is able to activate or deactivate a connection by clicking into > a checkbox, or even better using a radio button because you can only have > one active connection for each physical device. The horizonal rules are > not > really necessary but I thought you like them ;-) > >>> Are there currently any plans to polish the nm-applet? >> >> Mainly plans to stop using a GtkMenu widget entirely and move to a more >> freeform widget. That's not in-progress yet though. Until then we can >> certainly discuss ways to make the current menu-based approach better, >> especially if we find that users are confused with it. We should have a >> lot better data on the new applet too given that both Ubuntu 9.10 and >> Fedora 12 shipped with it. >> > > You are right. The user will give response. But most of them do have a > more > or less technical background. The users I am thinking about are really > native > end users. They know their business application (more or less). They know > the > difference between eMail and a letter. That's it. > > My problem is that I have thousands of them ;-) > > HG > >> Dan > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
gsm: implement initial unlock dialog for PIN & PUK
I found the new initial unlock dialog for PIN & PUK after testing the latest git code today. I have written a python based gtk application for pin handling some weeks ago. The intention for this small app is that after a fresh system installation the user get's prompted for the PIN until he has entered it at least one time. Then I write the given PIN into a prepared system-connection file and copy this to /etc/NetworkManager/system-connections. If the entered PIN is wrong or the modem is locked I prompt either to reenter the right PIN or to enter the PUK directly. It would be very nice if the new pin dialog would have these features as well. At least it should store the given PIN maybe in gnome-keyring. Otherwise after each power off / on the user gets the pin dialog again and again. Best regards, HG ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: gui design of nm-applet
On Tue, 09 Mar 2010 16:55:35 -0800, Dan Williams wrote: > On Mon, 2010-03-08 at 13:24 +0100, van Schelve wrote: >> We are planning to rollout NM > 0.8 to a very! big number of mobile Linux >> systems. Our different usecases for NM are Ethernet, 3G datacards, >> bluetooth based 3g and in small numbers wlan as well. >> >> Today we had a discussion about nm-applet in our companay. We are worried >> about our user get overcharge with the usability of nm-applet. The >> biggest >> painpoint we talked about in this context is way nm presents the >> available >> devices, available connections and the active connections. >> >> The horizontal separator should be removed from nm-applet. It looks like >> a >> logical separator between different connection types. > > Hmm, the indentation was supposed to help make that clearer. The > problem is that we do need a mechanism to distinguish between the > "current" network connection for that device and it's associated actions > (like disconnect) and the other available connections. Unfortunately > we're currently stuck in a GtkMenu widget where we can't control the > layout in a fine-grained manner without violating a lot of UI principles > (since it is still a menu). > >> Maybe it could be a way using differnt font size / weight? Or maybe >> indenting blockwise? > > It might work to make the "available" text in the line smaller perhaps > to differentiate it more from the surrounding text? > What do you think about presenting the list in this way: - Wired Network [ ] Auto eth0 (100Mit FD) - Mobile Broadband [x] MyCompany - Nokia 6680 (Bluetooth) [ ] MyCompany - Wireless Network [x] Foobar (83%) [ ] blahfasel (60%) [ ] muckebock (50%) Connect to Hidden Wireless Network Create New Wireless Network - VPN [ ] MyCompany (openvpn) [ ] @Home (vpnc) The user is able to activate or deactivate a connection by clicking into a checkbox, or even better using a radio button because you can only have one active connection for each physical device. The horizonal rules are not really necessary but I thought you like them ;-) >> Are there currently any plans to polish the nm-applet? > > Mainly plans to stop using a GtkMenu widget entirely and move to a more > freeform widget. That's not in-progress yet though. Until then we can > certainly discuss ways to make the current menu-based approach better, > especially if we find that users are confused with it. We should have a > lot better data on the new applet too given that both Ubuntu 9.10 and > Fedora 12 shipped with it. > You are right. The user will give response. But most of them do have a more or less technical background. The users I am thinking about are really native end users. They know their business application (more or less). They know the difference between eMail and a letter. That's it. My problem is that I have thousands of them ;-) HG > Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
gui design of nm-applet
We are planning to rollout NM > 0.8 to a very! big number of mobile Linux systems. Our different usecases for NM are Ethernet, 3G datacards, bluetooth based 3g and in small numbers wlan as well. Today we had a discussion about nm-applet in our companay. We are worried about our user get overcharge with the usability of nm-applet. The biggest painpoint we talked about in this context is way nm presents the available devices, available connections and the active connections. The horizontal separator should be removed from nm-applet. It looks like a logical separator between different connection types. Maybe it could be a way using differnt font size / weight? Or maybe indenting blockwise? Are there currently any plans to polish the nm-applet? HG ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Re: Problems with btdun branch
> > I've merged DUN to master in both nm-applet and NM. And fixed the bugs > you found (the state assertion, the BlingSpinner name collision, and a > few more). If you wouldn't mind testing that, I'd be grateful. > > Thanks, > Dan > Hi Dan, it has taken some time for me because I would like to clearify a new problem that came up with the latest master from git. I compiled the sources and installed them on my test system. Now it is not longer possible to bring up any dhcp based connection: ... NetworkManager: Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. NetworkManager: Activation (eth0) Stage 2 of 5 (Device Configure) complete. NetworkManager: Activation (eth0) Stage 3 of 5 (IP Configure Start) started... NetworkManager: (eth0): device state change: 5 -> 7 (reason 0) NetworkManager: Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds) NetworkManager: dhclient started with pid 2478 NetworkManager: Activation (eth0) Stage 4 of 5 (IP6 Configure Get) scheduled... NetworkManager: Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. NetworkManager: Activation (eth0) Stage 4 of 5 (IP6 Configure Get) started... NetworkManager: Activation (eth0) Stage 4 of 5 (IP6 Configure Get) complete. NetworkManager: (wlan0): supplicant interface state: starting -> ready NetworkManager: (wlan0): device state change: 2 -> 3 (reason 42) Internet Systems Consortium DHCP Client V3.1.3 Copyright 2004-2009 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Usage: dhclient [-1dqrx] [-nw] [-p ] [-s server] [-cf config-file] [-lf lease-file][-pf pid-file] [-e VAR=val] [-sf script-file] [interface] but at the end I tested against the main issue. This looks like to be resolved. So it is now possible to bring up dun based bt connections directly. Thank you! It's still open that system wide connections for BT cannot be configured with nm-connection-editor. Also when creating them directly in the filesystem they are ignored. Hans-Gerd ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Re: Problems with btdun branch
On Wed, 17 Feb 2010 12:23:51 -0800, Dan Williams wrote: > On Wed, 2010-02-17 at 14:24 +0100, van Schelve wrote: >> On Wed, 17 Feb 2010 11:55:44 +, Bastien Nocera >> wrote: >> > On Tue, 2010-02-16 at 15:03 -0800, Dan Williams wrote: >> >> On Tue, 2010-02-16 at 11:17 +0100, van Schelve wrote: >> >> > Hi. >> >> > >> >> > I want to tryout the btdun branch to see how the work that is in >> there >> >> > works an can be used in the filed. >> >> > Therefore I compiled the btdun branch of network-manager and >> >> > network-manager-applet under Ubuntu lucid. >> >> > >> >> > Now, when pairing the bluetooth mobile using bluetooth-wizard there >> is >> >> > a >> >> > new checkbox: >> >> > "Access the Internet using your mobile phone (DUN)" >> >> > When activating this checkbox bluetooth-wizard freezes. When >> >> > starting >> >> > bluetooth-wizard from command-line I see the following messages when >> >> > trying >> >> > to activate the checkbox: >> >> > >> >> > ** Message: dun_start: starting DUN device discovery... >> >> > >> >> > (bluetooth-wizard:2663): GLib-GObject-WARNING **: cannot register >> >> > existing >> >> > type `BlingSpinner' >> >> >> >> What do you get for: >> >> >> >> grep -r "BlingSpinner" /usr/lib/gnome-bluetooth/plugins >> >> >> >> or >> >> >> >> grep -r "BlingSpinner" /usr/lib64/gnome-bluetooth/plugins >> >> >> >> ? Maybe we just need to rename it so it doesn't use a common name and >> >> is private to NM. Since the plugins are shared objects we do have to >> be >> >> careful about the types we register with glib. >> > >> > That would probably happen if you don't export the BlingSpinner symbol >> > from your plugin, and use it against an older gnome-bluetooth. >> > >> > gnome-bluetooth in master (and the latest release) uses the spinner I >> > put in GTK+. >> > >> > Cheers >> >> Hm, after rebuilding the packages again I was able to do the pairing >> successfully. >> There is an entry in nm-applet for the bluetooth mobile and under this >> the >> available >> connections are listed. Great! >> >> But there are now two new questions: >> >> 1. As it looks to me it is not possible to use an existing nm system >> connection. Is this correct? > > No, this should be possible as long as the configuration is there. If > not, that's a bug. At this point only the 'keyfile' plugin allows > bluetooth configuration. > Then it looks like to be a bug. I have created the connection based on the documentation I found somewhere at live.gnome.org/NetworkManager but maybe it is wrong? [connection] autoconnect = false uuid = 9ff1bcc4-15da-416f-9dce-ced289a64cdd timestamp = 0 type = bluetooth id = Test-BT [bluetooth] bdaddr = 00:16:4e:24:ea:2f name = bluetooth type = dun [ppp] refuse-mschapv2 = true no-vj-comp = false refuse-eap = true require-mppe-128 = false crtscts = false require-mppe = false mru = 0 nobsdcomp = false refuse-pap = true refuse-mschap = true mtu = 0 refuse-chap = false lcp-echo-interval = 0 mppe-stateful = false noauth = true baud = 0 lcp-echo-failure = 0 nodeflate = false [gsm] number = *99# network-type = -1 band = 0 apn = myapn.tda.t-d1.de allowed-bands = 1 username = itu002 password = itumobil [ipv4] dns = 10.22.33.253;10.22.33.249 dns-search = mydomain.de dhcp-send-hostname = false ignore-auto-dns = true ignore-auto-routes = false never-default = false method = auto [serial] baud = 115200 parity = 110 stopbits = 1 bits = 8 send-delay = 0 The permissions for the configuration file are correct. I also restarted nm-applet and NetworkManager but the connection is not shown. >> 2. To bring up a bt based connection I need to dial it twice. After >> selecting the connection the first time >> nm-applet seems to loop but nothing happens. But when I disconnect and >> then connect again to the same connection >> it comes up. > >> I have captured some debug output. I don't know if it's a good idea to >> post these long logs here. Therefore I put >> it on pastebin: >> >> http://pastebin.com/m5c9ad0f4 for network-manager debug and >> http://pastebin.com/m4a0be7b3 for modem-manager debug > > The line: > > NetworkManager: modem_prepare_result: assertion `state == > NM_DEVICE_STATE_CONFIG' failed > > is a bug in NM. Need to fix that; I think this got broken due to the > PIN fixing changes when I merged master last week. > > Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems with btdun branch
On Wed, 17 Feb 2010 11:55:44 +, Bastien Nocera wrote: > On Tue, 2010-02-16 at 15:03 -0800, Dan Williams wrote: >> On Tue, 2010-02-16 at 11:17 +0100, van Schelve wrote: >> > Hi. >> > >> > I want to tryout the btdun branch to see how the work that is in there >> > works an can be used in the filed. >> > Therefore I compiled the btdun branch of network-manager and >> > network-manager-applet under Ubuntu lucid. >> > >> > Now, when pairing the bluetooth mobile using bluetooth-wizard there is >> > a >> > new checkbox: >> > "Access the Internet using your mobile phone (DUN)" >> > When activating this checkbox bluetooth-wizard freezes. When starting >> > bluetooth-wizard from command-line I see the following messages when >> > trying >> > to activate the checkbox: >> > >> > ** Message: dun_start: starting DUN device discovery... >> > >> > (bluetooth-wizard:2663): GLib-GObject-WARNING **: cannot register >> > existing >> > type `BlingSpinner' >> >> What do you get for: >> >> grep -r "BlingSpinner" /usr/lib/gnome-bluetooth/plugins >> >> or >> >> grep -r "BlingSpinner" /usr/lib64/gnome-bluetooth/plugins >> >> ? Maybe we just need to rename it so it doesn't use a common name and >> is private to NM. Since the plugins are shared objects we do have to be >> careful about the types we register with glib. > > That would probably happen if you don't export the BlingSpinner symbol > from your plugin, and use it against an older gnome-bluetooth. > > gnome-bluetooth in master (and the latest release) uses the spinner I > put in GTK+. > > Cheers Hm, after rebuilding the packages again I was able to do the pairing successfully. There is an entry in nm-applet for the bluetooth mobile and under this the available connections are listed. Great! But there are now two new questions: 1. As it looks to me it is not possible to use an existing nm system connection. Is this correct? 2. To bring up a bt based connection I need to dial it twice. After selecting the connection the first time nm-applet seems to loop but nothing happens. But when I disconnect and then connect again to the same connection it comes up. I have captured some debug output. I don't know if it's a good idea to post these long logs here. Therefore I put it on pastebin: http://pastebin.com/m5c9ad0f4 for network-manager debug and http://pastebin.com/m4a0be7b3 for modem-manager debug ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Problems with btdun branch
Hi. I want to tryout the btdun branch to see how the work that is in there works an can be used in the filed. Therefore I compiled the btdun branch of network-manager and network-manager-applet under Ubuntu lucid. Now, when pairing the bluetooth mobile using bluetooth-wizard there is a new checkbox: "Access the Internet using your mobile phone (DUN)" When activating this checkbox bluetooth-wizard freezes. When starting bluetooth-wizard from command-line I see the following messages when trying to activate the checkbox: ** Message: dun_start: starting DUN device discovery... (bluetooth-wizard:2663): GLib-GObject-WARNING **: cannot register existing type `BlingSpinner' (bluetooth-wizard:2663): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (bluetooth-wizard:2663): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed (bluetooth-wizard:2663): Gtk-CRITICAL **: gtk_box_pack: assertion `GTK_IS_WIDGET (child)' failed Maybe someone can help? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Lockdown nm-applet once again
Hi. In the archives I have found this entry: http://www.mail-archive.com/networkmanager-list@gnome.org/msg13808.html The question that was talked about there was how to lockdown the nm-applet. I have successfully tried to lockdown the nm-applet by changing the dbus config as descripted by Dan. It looks like this would be a valid workaround. But I don't know if it is possible to have this config part in a seperate file? I didn't found anything useful in the freedesktop dbus documentation for this question. In general it would be very fine to configure the whole nm-applet in a single config file (f.e. /etc/NetworkManager/nm-applet.conf). Currently there are three steps to lockdown nm-applet: 1. dbus config to disalbe the enable/disable Network option 2. gconf for notification behaviour 3. chmod, selinux, apparmor or whatever for nm-connection-editor -- HG ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Networkmanager + Bluetooth
>> Hi. >> >> After some more testing I found out that NM is able to bring up the >> connection when following these steps: >> >> 1. sudo rfcomm connect hci0 >> 2. In nm-applet you can now start the already configured connection >> >> My questions are now: >> - Is it possible to lable the bluetooth based connections as "Bluetooth" >> or whatever. > > They are, if correctly configured. This already happens for PAN > connections, but DUN connections are not yet natively supported even > though they will work if you create the rfcomm connection underneath NM. > DUN is slated for the 0.8.1 release. > Do you have a timeline for 0.8.1? Do you see a chance that this will be available until March 2010? >> - why do i need to open the rfcomm connection? Isn't it enought to bind >> to >> the mobile? > > You wont' need to do this after real DUN support lands. NM will do it > automatically for you. > Interesting. Best regards and happy new year to all of you! > Dan > > >> -- HG >> >> >> > I am currently looking for way to use bluetooth based dial up together >> > with networkmanager. >> > >> > Can someone give me an overview? What I'm looking for is >> > >> > 1. simple dialog for the initial pairing >> > 2. an entry in nm-applet to bring up or disconnect the connection >> > 3. I need to configure the apn + chap credentials. >> ___ >> NetworkManager-list mailing list >> NetworkManager-list@gnome.org >> http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Networkmanager + Bluetooth
Hmm... really nobody here who can help? > > After some more testing I found out that NM is able to bring up the > connection when following these steps: > > 1. sudo rfcomm connect hci0 > 2. In nm-applet you can now start the already configured connection > > My questions are now: > - Is it possible to lable the bluetooth based connections as "Bluetooth" > or whatever. > - why do i need to open the rfcomm connection? Isn't it enought to bind to > the mobile? > > -- HG > > >> I am currently looking for way to use bluetooth based dial up together >> with networkmanager. >> >> Can someone give me an overview? What I'm looking for is >> >> 1. simple dialog for the initial pairing >> 2. an entry in nm-applet to bring up or disconnect the connection >> 3. I need to configure the apn + chap credentials. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Networkmanager + Bluetooth
Hi. After some more testing I found out that NM is able to bring up the connection when following these steps: 1. sudo rfcomm connect hci0 2. In nm-applet you can now start the already configured connection My questions are now: - Is it possible to lable the bluetooth based connections as "Bluetooth" or whatever. - why do i need to open the rfcomm connection? Isn't it enought to bind to the mobile? -- HG > I am currently looking for way to use bluetooth based dial up together > with networkmanager. > > Can someone give me an overview? What I'm looking for is > > 1. simple dialog for the initial pairing > 2. an entry in nm-applet to bring up or disconnect the connection > 3. I need to configure the apn + chap credentials. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Networkmanager + Bluetooth
Hello, I am currently looking for way to use bluetooth based dial up together with networkmanager. Can someone give me an overview? What I'm looking for is 1. simple dialog for the initial pairing 2. an entry in nm-applet to bring up or disconnect the connection 3. I need to configure the apn + chap credentials. Thanks! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Python sample
Hi! I'm looking for a python sample code. I need to 1. find out which NM interfaces are currently active and 2. disconnect from a given interface Can someone help? -- HG ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: system-connection for WWAN not working
Hi! Now we talked about the problem. Can someone confirm this is a bug or do I have a wrong configuration? What else can I do? -- Hans-Gerd On Thu, 19 Nov 2009 13:17:46 +0100, van Schelve wrote: >> Well, I am not Dan, and I am not *sure*, but this part of the log of > failed >> session does not seem to support this theory: >> >> >> rcvd [CHAP Challenge id=0x1 , name = >> "UMTS_CHAP_SRVR"] >> ** Message: nm-ppp-plugin: (get_credentials): passwd-hook, requesting >> credentials... >> ** Message: nm-ppp-plugin: (get_credentials): got credentials from >> NetworkManager >> sent [CHAP Response id=0x1 , name = >> "username"] >> rcvd [CHAP Success id=0x1 ""] >> CHAP authentication succeeded >> >> >> Could the radius log be from another session, that failed for a > different >> reason? > > This is possible but during the time from the Logfiles I really did some > tests. > If you think it can be helpful, I will try to capture the logs from a > complete > session again NM and Radius. > > But let me put it together again: > > - T-Mobile Internet connection is OK when configured as User connection > as well as system-connection > > - MyWWAN works only when configured as User connection. When using this > as system-connection connection don't come up. > > I compared T-Mobile and MyWWAN system-connection files from > /etc/NetworkManager/system-connections > and they are different only in password, username and apn (as well as uuid > and id) > > -- Hans-Gerd >> >> Looking closer at the logs, side by side, shows that the difference > starts >> *after* successful authentication, here: >> >> BAD: >> sent [IPCP ConfReq id=0x1 > 0.0.0.0> >> ] >> >> GOOD: >> sent [IPCP ConfReq id=0x1 > 0.0.0.0>] >> >> I cannot tell what exactly goes on here, though... Don't know the PPP >> protocol >> well enough. >> >> Eugene > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: system-connection for WWAN not working
> Well, I am not Dan, and I am not *sure*, but this part of the log of failed > session does not seem to support this theory: > > > rcvd [CHAP Challenge id=0x1 , name = > "UMTS_CHAP_SRVR"] > ** Message: nm-ppp-plugin: (get_credentials): passwd-hook, requesting > credentials... > ** Message: nm-ppp-plugin: (get_credentials): got credentials from > NetworkManager > sent [CHAP Response id=0x1 , name = > "username"] > rcvd [CHAP Success id=0x1 ""] > CHAP authentication succeeded > > > Could the radius log be from another session, that failed for a different > reason? This is possible but during the time from the Logfiles I really did some tests. If you think it can be helpful, I will try to capture the logs from a complete session again NM and Radius. But let me put it together again: - T-Mobile Internet connection is OK when configured as User connection as well as system-connection - MyWWAN works only when configured as User connection. When using this as system-connection connection don't come up. I compared T-Mobile and MyWWAN system-connection files from /etc/NetworkManager/system-connections and they are different only in password, username and apn (as well as uuid and id) -- Hans-Gerd > > Looking closer at the logs, side by side, shows that the difference starts > *after* successful authentication, here: > > BAD: > sent [IPCP ConfReq id=0x10.0.0.0> > ] > > GOOD: > sent [IPCP ConfReq id=0x10.0.0.0>] > > I cannot tell what exactly goes on here, though... Don't know the PPP > protocol > well enough. > > Eugene ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: system-connection for WWAN not working
Hi Dan, as I mentioned in my post from today it looks to me like an authentication problem because these radius log entries: Wed Nov 18 08:48:18 2009 : Auth: Login incorrect (rlm_chap: Wrong user password): [49160/] (from client tmobwanip port 0 cli 49160) Wed Nov 18 08:56:36 2009 : Auth: Login incorrect (rlm_chap: Wrong user password): [49160/] (from client tmobwanip port 0 cli 49160) Please have a look into my other posts. -- Hans-Gerd On Wed, 18 Nov 2009 10:24:37 -0800, Dan Williams wrote: > On Wed, 2009-11-18 at 09:55 +0300, Eugene Crosser wrote: >> Dan Williams wrote: >> > On Tue, 2009-11-17 at 22:52 +0100, van Schelve wrote: >> >> Hi Dan, >> >> >> >> thank you for your help. >> >> >> >> I captured the debug output as you told me. But before pasting the >> >> output >> >> here I have some additional facts: >> >> >> >> The wwan connection I have problems with is based on a own APN. >> >> Because I >> >> was not able to configure this in the GUI I added the needed lines in >> >> /usr/share/mobile-broadband-provider-info/serviceprov: >> >> >> >> >> >> MyWWAN >> >> >> >> >> >> >> >> >> >> >> >> username >> >> password >> >> 10.39.148.254 >> >> 10.39.148.253 >> >> >> >> >> >> >> >> >> >> >> >> I tried to create a system-wide connection for T-Mobile as well with >> >> the >> >> result : It works. But here the debug output: >> > >> > Interesting. It looks like the device is simply unable to negotiate a >> > PPP connection. But you said that T-Mobile seems to work OK. Did this >> > connection work when the connection was a user conncetion? >> >> Looks like pppd insists on using Van Jacobson compression (why?) and the >> remote >> patiently responds that it does not support it. Then the remote gives >> up, and >> eventually session establishment timeouts. (The other provider may >> support it >> and therefore work.) >> Could it be that the local pppd is somehow configured to force VJ >> compression? > > Could be. Check the connection editor, it'll be a checkbox called "Use > TCP Header Compression". If that's not checked, then look > in /etc/ppp/options and make sure vjcomp isn't set there. > Unfortunately, there's no way to get pppd to stop > reading /etc/ppp/options when being driven by NM. > > Dan > >> Eugene >> >> > Dan >> > >> >> NetworkManager: starting... >> >> NetworkManager: modem-manager is now available >> >> NetworkManager:SCPlugin-Ifupdown: init! >> >> NetworkManager:SCPlugin-Ifupdown: update_system_hostname >> >> NetworkManager:SCPluginIfupdown: management mode: unmanaged >> >> NetworkManager:SCPlugin-Ifupdown: devices added (path: >> >> /sys/devices/pci:00/:00:19.0/net/eth0, iface: eth0) >> >> NetworkManager:SCPlugin-Ifupdown: device added (path: >> >> /sys/devices/pci:00/:00:19.0/net/eth0, iface: eth0): no >> >> ifupdown >> >> configuration found. >> >> NetworkManager:SCPlugin-Ifupdown: devices added (path: >> >> /sys/devices/pci:00/:00:1c.1/:03:00.0/net/wlan0, iface: >> >> wlan0) >> >> NetworkManager:SCPlugin-Ifupdown: device added (path: >> >> /sys/devices/pci:00/:00:1c.1/:03:00.0/net/wlan0, iface: >> >> wlan0): >> >> no ifupdown configuration found. >> >> NetworkManager:SCPlugin-Ifupdown: devices added (path: >> >> /sys/devices/pci:00/:00:1c.1/:03:00.0/net/wmaster0, iface: >> >> wmaster0) >> >> NetworkManager:SCPlugin-Ifupdown: device added (path: >> >> /sys/devices/pci:00/:00:1c.1/:03:00.0/net/wmaster0, iface: >> >> wmaster0): no ifupdown configuration found. >> >> NetworkManager:SCPlugin-Ifupdown: devices added (path: >> >> /sys/devices/virtual/net/lo, iface: lo) >> >> NetworkManager:SCPlugin-Ifupdown: device added (path: >> >> /sys/de
Re: system-connection for WWAN not working
Hi!
I have received the logs from our radius server during my unsuccessful
dial up:
Wed Nov 18 08:48:18 2009 : Auth: Login incorrect (rlm_chap: Wrong user
password): [49160/] (from client tmobwanip port 0
cli 49160)
Wed Nov 18 08:56:36 2009 : Auth: Login incorrect (rlm_chap: Wrong user
password): [49160/] (from client tmobwanip port 0
cli 49160)
So it looks like to me that if the connection is system-wide pppd doesn't
get chap credentials. This suspiction suggests itself because the t-mobile
connection works. But this connection does not need a chap / pap password.
I tested to put username / password in /etc/ppp/{pap,chap}-secrets but
this does not help.
-- Hans-Gerd
On Wed, 18 Nov 2009 09:13:08 +0100, van Schelve
wrote:
> Dan, Eugene.
>
> I have captured the debug from this connection while not available as
> system-connection. It works in this case as you can see:
>
> NetworkManager: Tried to set deprecated property gsm/band
> NetworkManager: Tried to set deprecated property gsm/band
> NetworkManager: Tried to set deprecated property gsm/band
> NetworkManager: Tried to set deprecated property gsm/band
> NetworkManager: (ttyUSB2): new GSM device (driver: 'sierra')
> NetworkManager: (ttyUSB2): exported as
> /org/freedesktop/NetworkManager/Devices/3
> NetworkManager: (ttyUSB2): now managed
> NetworkManager: (ttyUSB2): device state change: 1 -> 2 (reason
2)
> NetworkManager: (ttyUSB2): deactivating device (reason: 2).
> NetworkManager: flush_routes: assertion `iface_idx >= 0' failed
> NetworkManager: flush_addresses: assertion `iface_idx >= 0' failed
> NetworkManager: (ttyUSB2): device state change: 2 -> 3 (reason
0)
> NetworkManager: Activation (ttyUSB2) starting connection
'MyWWAN'
> NetworkManager: (ttyUSB2): device state change: 3 -> 4 (reason
0)
> NetworkManager: Activation (ttyUSB2) Stage 1 of 5 (Device
Prepare)
> scheduled...
> NetworkManager: Activation (ttyUSB2) Stage 1 of 5 (Device
Prepare)
> started...
> NetworkManager: (ttyUSB2): device state change: 4 -> 6 (reason
0)
> NetworkManager: Activation (ttyUSB2) Stage 1 of 5 (Device
Prepare)
> complete.
> NetworkManager: Activation (ttyUSB2) Stage 1 of 5 (Device
Prepare)
> scheduled...
> NetworkManager: Activation (ttyUSB2) Stage 1 of 5 (Device
Prepare)
> started...
> NetworkManager: (ttyUSB2): device state change: 6 -> 4 (reason
0)
> NetworkManager: Activation (ttyUSB2) Stage 1 of 5 (Device
Prepare)
> complete.
> NetworkManager: Activation (ttyUSB2) Stage 2 of 5 (Device
> Configure) scheduled...
> NetworkManager: Activation (ttyUSB2) Stage 2 of 5 (Device
> Configure) starting...
> NetworkManager: (ttyUSB2): device state change: 4 -> 5 (reason
0)
> NetworkManager: Activation (ttyUSB2) Stage 2 of 5 (Device
> Configure) successful.
> NetworkManager: Activation (ttyUSB2) Stage 3 of 5 (IP Configure
> Start) scheduled.
> NetworkManager: Activation (ttyUSB2) Stage 2 of 5 (Device
> Configure) complete.
> NetworkManager: Activation (ttyUSB2) Stage 3 of 5 (IP Configure
> Start) started...
> NetworkManager: (ttyUSB2): device state change: 5 -> 7 (reason
0)
> NetworkManager: Starting pppd connection
> NetworkManager: [1258531195.240804] nm_ppp_manager_start():
> Command line: /usr/sbin/pppd nodetach lock nodefaultroute debug user
> username ttyUSB2 noipdefault noauth usepeerdns lcp-echo-failure 0
> lcp-echo-interval 0 ipparam /org/freedesktop/NetworkManager/PPP/0 plugin
> /usr/lib/pppd/2.4.4/nm-pppd-plugin.so
> Plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so loaded.
> ** Message: nm-ppp-plugin: (plugin_init): initializing
> NetworkManager: [1258531195.258102] nm_ppp_manager_start(): ppp
> started with pid 9331
> NetworkManager: Activation (ttyUSB2) Stage 4 of 5 (IP6 Configure
> Get) scheduled...
> NetworkManager: Activation (ttyUSB2) Stage 3 of 5 (IP Configure
> Start) complete.
> NetworkManager: Activation (ttyUSB2) Stage 4 of 5 (IP6 Configure
> Get) started...
> NetworkManager: Activation (ttyUSB2) Stage 4 of 5 (IP6 Configure
> Get) complete.
> ** Message: nm-ppp-plugin: (nm_phasechange): status 3 / phase 'serial
> connection'
> Removed stale lock on ttyUSB2 (pid 9216)
> using channel 7
> Using interface ppp0
> Connect: ppp0 <--> /dev/ttyUSB2
> ** Message: nm-ppp-plugin: (nm_phasechange): status 5 / phase
'establish'
> sent [LCP ConfReq id=0x1
> ]
> NetworkManager:SCPlugin-Ifupdown: devices added (path:
> /sys/devices/virtual/net/ppp0, iface: ppp0)
> NetworkManager:SCPlugin-Ifupdown: device added (path:
> /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration
> found.
> rcvd [LCP ConfReq id=0x0
> ]
> s
Re: system-connection for WWAN not working
Dan, Eugene. I have captured the debug from this connection while not available as system-connection. It works in this case as you can see: NetworkManager: Tried to set deprecated property gsm/band NetworkManager: Tried to set deprecated property gsm/band NetworkManager: Tried to set deprecated property gsm/band NetworkManager: Tried to set deprecated property gsm/band NetworkManager: (ttyUSB2): new GSM device (driver: 'sierra') NetworkManager: (ttyUSB2): exported as /org/freedesktop/NetworkManager/Devices/3 NetworkManager: (ttyUSB2): now managed NetworkManager: (ttyUSB2): device state change: 1 -> 2 (reason 2) NetworkManager: (ttyUSB2): deactivating device (reason: 2). NetworkManager: flush_routes: assertion `iface_idx >= 0' failed NetworkManager: flush_addresses: assertion `iface_idx >= 0' failed NetworkManager: (ttyUSB2): device state change: 2 -> 3 (reason 0) NetworkManager: Activation (ttyUSB2) starting connection 'MyWWAN' NetworkManager: (ttyUSB2): device state change: 3 -> 4 (reason 0) NetworkManager: Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) started... NetworkManager: (ttyUSB2): device state change: 4 -> 6 (reason 0) NetworkManager: Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) complete. NetworkManager: Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) started... NetworkManager: (ttyUSB2): device state change: 6 -> 4 (reason 0) NetworkManager: Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) complete. NetworkManager: Activation (ttyUSB2) Stage 2 of 5 (Device Configure) scheduled... NetworkManager: Activation (ttyUSB2) Stage 2 of 5 (Device Configure) starting... NetworkManager: (ttyUSB2): device state change: 4 -> 5 (reason 0) NetworkManager: Activation (ttyUSB2) Stage 2 of 5 (Device Configure) successful. NetworkManager: Activation (ttyUSB2) Stage 3 of 5 (IP Configure Start) scheduled. NetworkManager: Activation (ttyUSB2) Stage 2 of 5 (Device Configure) complete. NetworkManager: Activation (ttyUSB2) Stage 3 of 5 (IP Configure Start) started... NetworkManager: (ttyUSB2): device state change: 5 -> 7 (reason 0) NetworkManager: Starting pppd connection NetworkManager: [1258531195.240804] nm_ppp_manager_start(): Command line: /usr/sbin/pppd nodetach lock nodefaultroute debug user username ttyUSB2 noipdefault noauth usepeerdns lcp-echo-failure 0 lcp-echo-interval 0 ipparam /org/freedesktop/NetworkManager/PPP/0 plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so Plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so loaded. ** Message: nm-ppp-plugin: (plugin_init): initializing NetworkManager: [1258531195.258102] nm_ppp_manager_start(): ppp started with pid 9331 NetworkManager: Activation (ttyUSB2) Stage 4 of 5 (IP6 Configure Get) scheduled... NetworkManager: Activation (ttyUSB2) Stage 3 of 5 (IP Configure Start) complete. NetworkManager: Activation (ttyUSB2) Stage 4 of 5 (IP6 Configure Get) started... NetworkManager: Activation (ttyUSB2) Stage 4 of 5 (IP6 Configure Get) complete. ** Message: nm-ppp-plugin: (nm_phasechange): status 3 / phase 'serial connection' Removed stale lock on ttyUSB2 (pid 9216) using channel 7 Using interface ppp0 Connect: ppp0 <--> /dev/ttyUSB2 ** Message: nm-ppp-plugin: (nm_phasechange): status 5 / phase 'establish' sent [LCP ConfReq id=0x1 ] NetworkManager:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) NetworkManager:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. rcvd [LCP ConfReq id=0x0 ] sent [LCP ConfAck id=0x0 ] rcvd [LCP ConfAck id=0x1 ] ** Message: nm-ppp-plugin: (nm_phasechange): status 6 / phase 'authenticate' rcvd [LCP DiscReq id=0x1 magic=0xc4897c] rcvd [CHAP Challenge id=0x1 <7e969b37b646b5c728bd354e34b515aa>, name = "UMTS_CHAP_SRVR"] ** Message: nm-ppp-plugin: (get_credentials): passwd-hook, requesting credentials... ** Message: nm-ppp-plugin: (get_credentials): got credentials from NetworkManager sent [CHAP Response id=0x1 <332d24b44f6834bd0ecc62af3b7fd0d6>, name = "username"] rcvd [CHAP Success id=0x1 ""] CHAP authentication succeeded CHAP authentication succeeded ** Message: nm-ppp-plugin: (nm_phasechange): status 8 / phase 'network' sent [CCP ConfReq id=0x1 ] sent [IPCP ConfReq id=0x1 ] rcvd [LCP ProtRej id=0x2 80 fd 01 01 00 0f 1a 04 78 00 18 04 78 00 15 03 2f] Protocol-Reject for 'Compression Control Protocol' (0x80fd) received rcvd [IPCP ConfNak id=0x1 ] sent [IPCP ConfReq id=0x2 ] rcvd [IPCP ConfNak id=0x2 ] sent [IPCP ConfReq id=0x3 ] rcvd [IPCP ConfNak id=0x3 ] sent [IPCP ConfReq id=0x4 ] rcvd [IPCP ConfNak id=0x4 ] sent [IPCP ConfReq id=0x5 ] rcvd [IPCP ConfNak id=0x5 ] sent [IPCP ConfReq id=0x6 ] rcvd [IPCP ConfNak id=0x6 ] sent [IPCP ConfReq id=0x7 ] rcvd [IPCP ConfNak id=0x7 ] sent [IPCP
Re: system-connection for WWAN not working
Hi Dan, thank you for your help. I captured the debug output as you told me. But before pasting the output here I have some additional facts: The wwan connection I have problems with is based on a own APN. Because I was not able to configure this in the GUI I added the needed lines in /usr/share/mobile-broadband-provider-info/serviceprov: MyWWAN username password 10.39.148.254 10.39.148.253 I tried to create a system-wide connection for T-Mobile as well with the result : It works. But here the debug output: NetworkManager: starting... NetworkManager: modem-manager is now available NetworkManager:SCPlugin-Ifupdown: init! NetworkManager:SCPlugin-Ifupdown: update_system_hostname NetworkManager:SCPluginIfupdown: management mode: unmanaged NetworkManager:SCPlugin-Ifupdown: devices added (path: /sys/devices/pci:00/:00:19.0/net/eth0, iface: eth0) NetworkManager:SCPlugin-Ifupdown: device added (path: /sys/devices/pci:00/:00:19.0/net/eth0, iface: eth0): no ifupdown configuration found. NetworkManager:SCPlugin-Ifupdown: devices added (path: /sys/devices/pci:00/:00:1c.1/:03:00.0/net/wlan0, iface: wlan0) NetworkManager:SCPlugin-Ifupdown: device added (path: /sys/devices/pci:00/:00:1c.1/:03:00.0/net/wlan0, iface: wlan0): no ifupdown configuration found. NetworkManager:SCPlugin-Ifupdown: devices added (path: /sys/devices/pci:00/:00:1c.1/:03:00.0/net/wmaster0, iface: wmaster0) NetworkManager:SCPlugin-Ifupdown: device added (path: /sys/devices/pci:00/:00:1c.1/:03:00.0/net/wmaster0, iface: wmaster0): no ifupdown configuration found. NetworkManager:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/lo, iface: lo) NetworkManager:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found. NetworkManager:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/pan0, iface: pan0) NetworkManager:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/pan0, iface: pan0): no ifupdown configuration found. NetworkManager:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/vboxnet0, iface: vboxnet0) NetworkManager:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/vboxnet0, iface: vboxnet0): no ifupdown configuration found. NetworkManager:SCPlugin-Ifupdown: end _init. NetworkManager: Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list. NetworkManager: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. NetworkManager: Found radio killswitch rfkill3 (at /sys/devices/pci:00/:00:1c.1/:03:00.0/ieee80211/phy0/rfkill3) (driver ) NetworkManager: Wireless now enabled by radio killswitch NetworkManager:SCPlugin-Ifupdown: (149241120) ... get_connections. NetworkManager:SCPlugin-Ifupdown: (149241120) ... get_connections (managed=false): return empty list. NetworkManager: Tried to set deprecated property gsm/band NetworkManager: Tried to set deprecated property gsm/band NetworkManager:Ifupdown: get unmanaged devices count: 0 NetworkManager: (eth0): carrier is OFF NetworkManager: (eth0): new Ethernet device (driver: 'e1000e') NetworkManager: (eth0): exported as /org/freedesktop/NetworkManager/Devices/0 NetworkManager: (eth0): now managed NetworkManager: (eth0): device state change: 1 -> 2 (reason 2) NetworkManager: (eth0): bringing up device. NetworkManager: (eth0): preparing device. NetworkManager: (eth0): deactivating device (reason: 2). NetworkManager: Added default wired connection 'Auto eth0' for /sys/devices/pci:00/:00:19.0/net/eth0 NetworkManager: (wlan0): driver supports SSID scans (scan_capa 0x01). NetworkManager: (wlan0): new 802.11 WiFi device (driver: 'iwl3945') NetworkManager: (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1 NetworkManager: (wlan0): now managed NetworkManager: (wlan0): device state change: 1 -> 2 (reason 2) NetworkManager: (wlan0): bringing up device. NetworkManager: (wlan0): preparing device. NetworkManager: (wlan0): deactivating device (reason: 2). NetworkManager: device_creator(): /sys/devices/virtual/net/pan0: couldn't determine device driver; ignoring... NetworkManager: device_creator(): /sys/devices/virtual/net/vboxnet0: couldn't determine device driver; ignoring... NetworkManager: (ttyUSB2): new GSM device (driver: 'sierra') NetworkManager: (ttyUSB2): exported as /org/freedesktop/NetworkManager/Devices/2 NetworkManager: (ttyUSB2): now managed NetworkManager: (ttyUSB2):
Re: system-connection for WWAN not working
Hi again. Because I got no answer to my question right now, maybe someone can give me a tip about how to debug this problem. Thank you! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: system-connection for WWAN not working
Hi again. Because I got no answer to my question right now, maybe someone can give me a tip about how to debug this problem. Thank you! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
system-connection for WWAN not working
Hello. I trying to create a system-connection for an internal wwan module under ubuntu-karmic. When configuring as a user connection I am able to use it for dial-up later. Now I changed this connection and set the hook in "available to all users" with the following results: - I need to type in my login password again - a new file is in /etc/NetworkManager/system-connections/: r...@c399415:~# ls -l /etc/NetworkManager/system-connections/ -rw--- 1 root root 749 Nov 16 14:53 MyWWAN - When trying to connect the pppd terminates with signal 15: Nov 16 14:55:56 c399415 pppd[3491]: Plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so loaded. Nov 16 14:55:56 c399415 pppd[3491]: pppd 2.4.5 started by root, uid 0 Nov 16 14:55:56 c399415 pppd[3491]: Removed stale lock on ttyUSB2 (pid 3362) Nov 16 14:55:56 c399415 pppd[3491]: Using interface ppp0 Nov 16 14:55:56 c399415 pppd[3491]: Connect: ppp0 <--> /dev/ttyUSB2 Nov 16 14:55:56 c399415 pppd[3491]: CHAP authentication succeeded Nov 16 14:55:56 c399415 pppd[3491]: CHAP authentication succeeded Nov 16 14:56:16 c399415 pppd[3491]: Terminating on signal 15 - When trying to connect again the NM symbol rotates extremly fast in the gnome-panel but no pppd comes up under the hood. I also tried to create the connection from scratch with sudo nm-connection-editor but the effect is the same. The packages I'm using are the original versions from Karmic: ii network-manager 0.8~a~git.20091013t193206.679d548-0ubuntu1 network management framework daemon ii network-manager-gnome 0.8~a~git.20091014t134532.4033e62-0ubuntu1 network management framework (GNOME frontend Thank you for your help! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
How to disable WLAN permanently?
Hi Folks! Can someone tell me how to disable wlan in networkmanager permanently on a defined number of systems? We won't have wlan support for every system - only for a limited group of users. Blacklisting the specific kernel module will work for the internal wlan card. But what happens if a user has his own usb / pcmcia card? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
3G Pin question
Hi Folks, we are planning a rollout for a big number of laptops with internal 3G Datacard. The 3G configuration is fixed and should not be changed by the user. After a fresh installation and the user is logging in the first time he should add the PIN Number for his SIM Card. I'm thinking about a xinitrc script or somewhere in gnome presession, postlogin What do you guys think about this solution? Any better Ideas? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NM Lockdown
Hi. I would like to know if there is a way for locking down the nm-applet. We want to use NM with centrally managed system-connections for ethernet and 3g on a couple of systems. Our user should be able to connect or disconnect from these both connection types (maybe later on also wlan) but they are not allowed to create or edit their own connection settings. Additionaly they should not be able to activate or deactivate network in general by right click on nm-applet. If PolicyKit would be a solution please give me a sample. Thanks in advance! -- Hans-Gerd ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NM Lockdown or Kioskmode
Hi. I would like to know if there is a way for locking down the nm-applet. We want to use NM with centrally managed system-connections for ethernet and 3g on a couple of systems. Our user should be able to connect or disconnect from these both connection types (maybe later on also wlan) but they are not allowed to create or edit their own connection settings. Additionaly they should not be able to activate or deactivate network in general by right click on nm-applet. If PolicyKit would be a solution please give me a sample. Thanks in advance! -- Hans-Gerd ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NetworkManager and Browser Proxy
Hello List. Does someone know if it is possible to change the Proxy Settings for Mozilla or other applications when the Network interface gets up? I think it must have to go with the NetworkManagerDispatcher but I have currently no Idea how to do it. Best regards. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NetworkManager + PPP
Hello.
In addition to my previous post from yesterday I have seen an other problem
regarding mobile connections based on ppp. In my Laptop (Lenovo x61) there
is an Sierra Wireless MC8775 installed. Normally I see three devices for
this card: /dev/ttyUSB0, /dev/ttyUSB1 and /dev/ttyUSB2. This is the
behavior for many other cards too.
In some situations this devices can be different. For example after
suspend/resume the laptop or you will have ttyUSB{3,4,5} or if there is an
other device installed that provides an ttyUSB0 you will get ttyUSB{4,5,6}.
It seems to me that NetworkManager only checks the availbility for
/dev/ttyUSB0. Is this true? Or do I have an other problem?
-- Hans-Gerd
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
PPP regarding questions
Hello. I am currently playing around with the NetworkManager in Fedora 9. First: Thank you for this great work. I can now use my internal Sierra modem with NetworkManager. Great! But I have two questions at the moment: 1. Is it possible to use different tty's for SIM pin handling and pppd itself? I needed to change the portmapping on our sierra modems from 06,06 to 05,05 (at!nvportmap=05,05). 2. In general I am connected over my WLAN. How can I switch to the mobile connection without being multi homed? There is no disconnect option for wlan devices? Best regards, Hans-Gerd ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
How to use the pppd plugin from svn?
Hello list. I want to give the pppd plugin a try under my Fedora 8 installation. So I installed the NetworkManager-0.7.0-0.6.6.svn3138.fc8 rpm and added the hal stuff: [EMAIL PROTECTED] ~]# cat /usr/share/hal/fdi/information/20thirdparty/10-usbmodem.fdi modem In my laptop (Lenovo x61s) there is a sierra wireless mc8755 installed. After restarting hald, NetworkManager and the modem itself I see three entries "GSM Modem" in the NetworkManager. But how do I have to configure them to create a UMTS connection? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Plans for ppp and ippp
Dan, we are currently using 0.6.4-6.el5 which is included in RHEL5. It is clear for us that we need to upgrade to a newer version either the NM or the whole distribution. At the moment we are bringing up the network during init automatically (including bluetooth pairing if it is necessary. But this is too much unflexible (you have to re reboot if you want to use a different dial up). What do you think about the futures that will the ppp plugin have? -- Hans-Gerd > On Tue, 2007-11-06 at 22:11 +0100, Hans-Gerd van Schelve wrote: >> Hello List. >> >> We have a large Linux Desktop Setup with 6300 mobile Systems. What are the >> projects plans for better support of (i)ppp dialups in NM? >> At the moment there are only options available that allows to dialup or >> hangup >> a >> (i)ppp connection. But there is no feedback for the >> user at the moment. So if something goes wrong during dialup or hangup the >> user >> get's no feedback. >> >> We plan to use internal WWAN modules in our new Laptops, but also want to be >> able to use a bluetooth phone for dialup. What we are missing >> is a userfriendly handling for that. > > What version of NM are you planning on deploying? I'd rather not keep > piling hacks on the dialup stuff in 0.6.x, and with 0.7 better > integrated PPP support is the next item on the list, and something that > I'm pretty sure Tambet and I will start on in the next few weeks. I > don't think there will be much ABI/API breakage from dialup devices, if > any, so if you deployed 0.7 now you'd get the better PPP support in the > near future without much problem. > > Dan > > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Plans for ppp and ippp
Hello List. We have a large Linux Desktop Setup with 6300 mobile Systems. What are the projects plans for better support of (i)ppp dialups in NM? At the moment there are only options available that allows to dialup or hangup a (i)ppp connection. But there is no feedback for the user at the moment. So if something goes wrong during dialup or hangup the user get's no feedback. We plan to use internal WWAN modules in our new Laptops, but also want to be able to use a bluetooth phone for dialup. What we are missing is a userfriendly handling for that. Thanks for discussion. -- Hans-Gerd ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Feature question
Hello list members. Are there any plans to implement ISDN and PPP support in NetworkManager? We are planning to change from our custom network initscript to the Network Manager. But it is not possible at the moment because of missing ISDN and GPRS / UMTS / HSDPA Support. Kind Regards, HG binPl0A3mGI1e.bin Description: Öffentlicher PGP-Schlüssel ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
