Re: Support for direct connection without cross cable / Run Avahi Zeroconfig Services
Hi Sven, On 10/11/2011 07:26 PM, Sven Nielsen wrote: I am not actually sure where the problem is here? My NM can do this without any problems (0.8.1 on Ubuntu Maverick), and I use it all the time. In the nm applet just go to the tab for wired connections, edit your eth0 (or whatever connection), ipv4 settings, and choose "shared with other machines" (my ui is german, so cannot state the exact name of that option). Thanks for this clue, I was wondering about that option, but thought it was for internet connection sharing, so I didn't tried it. Now that I tried it (It's called "Shared to other computers" in the method option), it's working. Yay! :) All the best. -arief ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Support for direct connection without cross cable / Run Avahi Zeroconfig Services
Hi Daniel, On 10/11/2011 03:35 PM, Daniel Yek wrote: > +ACs-AD4 I noticed that windows can setup networking > +ACs-AD4 to a direct-connected ... device > +ACs-AD4 (tested ... with network-drives, such as WD MyBook World) > +ACs-AD4 with ... straight ... ethernet cable. > > Hi, > > Could you make sure that you installed and ran Avahi? > > I think Avahi could enable this same easy, direct, connection > with your WD MyBook World. > > I don't have a way to test it now, but > I am interested to find out if you have luck with Avahi. I have Avahi installed and it's not working with it, but I didn't do any configuration (it should not need any, right?) +AKA- > WD MyBook World and Windows implemented > zeroconfig networking (with address range: 169.254.x.x/255.255.0.0), > which make the direct connection works. Yep, on Windows I can confirm they always setup with 169.254.+ACo- addresses. > Without Avahi, it is possible that a Linux command such as this: > +ACs-ACM ifconfig address 169.254.1.23 eth0 > > could enable HTTP connection to WD MyBook World. What I just did is setting up a Wired connection with Method: Shared to other computers in NM, and it's working. Thanks for the reply and the clues, appreciated. All the best. -arief ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Support for direct connection without cross cable
On 10/11/2011 04:52 AM, Dan Williams wrote: Most network cards have supported direct vs. crossover detection for a while, so that shouldn't be a problem. Ok, just tested this again with Method: Shared to other computers. And it's working :) Thanks for the reply, Dan. All the best. -arief ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Support for direct connection without cross cable
Hi all, I'm just wondering, and might as well send the message on the list, in case someone has more ideas. On recent windows, with recent network cards, I noticed (on a couple laptops) that windows can setup networking to a direct-connected to another device (tested couple of times with network-drives, such as WD MyBook World) with simple straight forward ethernet cable. No crossing needed. I'm wondering if NM (or linux?) can support this as well? I'd appreciate any pointers on this issue. Thanks for your time :) All the best. -arief ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: double network at a time.
I'm forgetting many details now as I'm not with my computer, But if you run nm-connection-editor, you can edit the available network connections, and set the network routes and/or dns setting in there. I'm using much of the same setup to access office net and internet using two different connection (gsm modem to internet, lan to office net) this way. I'll post again later on the details if you still need em. All the best. -arief On 9/6/11, keyur savsani wrote: > hi, > can you please explain how to fix DNS and default route, > i am new to use ubuntu as well as network. > > Thanks. > > On 9/5/11, keyur savsani wrote: >> hello there, >> >> can any one heip me how to use double network at a time. >> >> I want to use LAN network for local connectivity at office and mobile >> broadband for internet use. >> >> Thanks, >> keyur savsani. >> > ___ > 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: NM 0.9 with Sierra USB 305 modem connection problems
On 08/26/2011 04:28 AM, Dan Williams wrote: On Thu, 2011-08-25 at 16:09 -0500, Dan Williams wrote: On Fri, 2011-08-26 at 03:48 +0700, Arief M Utama wrote: On 08/26/2011 03:27 AM, Dan Williams wrote: On Fri, 2011-08-26 at 02:55 +0700, Arief M Utama wrote: Hi all, I'm using Debian's NM 0.9 with MM 0.5 (from experimental repo), with Sierra Wireless modem USB 305 (USB id: 1199:68a3) mobile broadband connection does not work. When the modem is inserted, is the 'sierra_net' driver loaded? Any chance you can get ModemManager debug logging so we can diagnose? Yep, it is loaded. http://live.gnome.org/NetworkManager/Debugging the instructions under "Debugging NetworkManager 0.8.x 3G connections" still apply to 0.9. FYI I have a 306 that I've tested with so at least we expect it to work. Following that instructions, herewith I attached the log result. Bit more info, I already created a "Telkomsel Flash" connection using nm-connection-editor, connecting by clicking on it from the gnome-shell applet. Tried twice, same result no connection. On first try it shows "you are connected" notification but it's actually not connected (probably a gnome-shell issue). On second try it just went to disconnected message quickly. I left my WiFi connection up during the test. One more thing, I noted from the debug log, so many AT commands was sent to the modem. Wondered about this, as with my ppp chatscripts, basically I only use following AT commands to make it work flawlessly: Using wvdial doesn't allow use of the network port the modem exposes, which limits the connection speed; at the higher 3G/4G speeds we're seeing these days, PPP just doesn't allow full throughput. Plus, when using the network port, we can get connection status and signal strength on the AT command port, which you can't do when you're using PPP on a lot of devices. Basically, MM does a lot more than just connect, it also delivers status updates, signal strength, SMS, etc. --- start chatscript snippet --- # cease if the modem is not attached to the network yet ABORT"+CGATT: 0" ""AT TIMEOUT12 OKATH OKATE1 OKAT+CGDCONT=1,"IP","\T","",0,0 OKATD*99# TIMEOUT22 CONNECT"" --- end chatscript snippet --- Hope this helps, let me know if more is needed and thanks for the help. So the core problem is this: modem-manager[27390]: [1314304573.585330] [mm-at-serial-port.c:298] debug_log(): (ttyUSB0): --> 'AT$QCPDPP=1,1,"wap123","wap"' modem-manager[27390]: [1314304573.619827] [mm-at-serial-port.c:298] debug_log(): (ttyUSB0):<-- 'ERROR' Grr. You've got the USB Lightning, which appears to use an Icera chipset, not a Qualcomm one: http://sierrawireless.custhelp.com/app/answers/detail/a_id/641/~/can-i-use-a-sierra-wireless-modem-on-linux-machines-%28direct-ip-modems%29%3F So we need to update ModemManager to use "AT%IPDPCFG" in this case instead of AT$QCPDPP like we do for Option NV modems that also use Icera chipsets. Any chance you can check something for me quickly with minicom or screen or such? I'm interested in the response to the following commands: Sure, here they are AT&V AT&V ACTIVE PROFILE E: 1 L: 0 M: 0 Q: 0 V: 1 X: 4 S0: 0 S2: 43 S3: 13 S4: 10 S5: 8 S6: 2 S7: 60 S8: 2 S10: 15 +CRC: 0 +CR: 0 +FCLASS: 0 +IMODE: 0 +CMGF: 0 +CSDH: 0 +ILRR: 0 +CRLP: 61,61,128,6,1,3 +CMEE: 2 +CBST: 116,1,0 +CNMI: 2,1,0,0,0 +CSTA: 129 +CSCS: "IRA" +CSNS: 0 +DS: 3,0,512,20 &C: 1 &D: 2 +CCWE: 0 *TDTX: 0 +CTZU: 0 +CTZR: 0 +CV120: 1,1,1,0,0,0 +CGAUTO: 3 *TGMTPCACT: 0 *TGMTPCA: 1 *THCFG: 0 *TTS61: 1 *TLDCA: 1 *TFFOS: 0 +CHSN: 0,0,0,0 *TLLC: 0 *TESTCSD: 0 *TRLP: 0,0 *TGPPPLOG: 0 *TSIMINS: 0 +CMUX: 0 +CCUG: 0,0,0 +CLIP: 0 +COLP: 0 +CCWA: 0 +CAOC: 1 +CLIR: 0 +CUSD: 0 +CSSU: 0 +CSSI: 0 +CDIP: 0 +VCID: 0 *TSTMODE: 2 +CSCA: "+628110",145 +CSMP: 17,255,0,0 OK AT+CLAC AT+CLAC +CGMI +CGMM +CGMR +GMI +GMM +GMR D DT DP A DL D> H +CHUP O +CMOD +CIND +CMEC +CMER +CACM +CAMM +CCLK $CCLK +CEER +CGSN +CIMI +CKPD +CLAC +CNUM +CPAS +CPBF +CPBR +CPBS +CPBW +CPUC +GCAP +GSN I P T +CGACT +CGANS +CGATT +CGCLASS +CGCMOD +CGDATA +CGDCONT +CGDSCONT +CGEREP +CGEQMIN +CGEQNEG +CGEQREQ +CGPADDR +CGQMIN +CGQREQ +CGREG +CGSMS +CGTFT +COPS +CPOL +COPN +CSQ $CSQ +CREG $CREG +CPLS +CMGD +CMGR +CSCA +CMGS +CMGC +CMSS +CMGL +CMGW +CPMS +CNMA +CMMS +CSCB &C &D &F &V &W +CBST +CCWE +CGAUTO +CHSN +CMEE +CMGF +CNMI +CR +CRC +CRES +CRLP +CSAS +CSCS +CSNS +CSDH +CSTA +CSMP +CSMS +CTZR +CTZU +CV120 +FCLASS +ILRR E L M Q S0 S10 S2 S3 S4 S5 S6 S7 S8 V X Z +CFUN +CMAR +CPIN +CSIM +CRSM +CCHO +CCHC +CGLA +CRLA +CUAD +PACSP H +CAOC +CCFC +CCWA +CCUG +CDIP +CHLD +CLCK +CLCC +CLIP +CLIR +COLP +CPWD +CSSN +CUSD +VCID *TSTCR *TSTEV *TSTGC *TSTMODE *TST
Re: NM 0.9 with Sierra USB 305 modem connection problems
On 08/26/2011 03:27 AM, Dan Williams wrote: On Fri, 2011-08-26 at 02:55 +0700, Arief M Utama wrote: Hi all, I'm using Debian's NM 0.9 with MM 0.5 (from experimental repo), with Sierra Wireless modem USB 305 (USB id: 1199:68a3) mobile broadband connection does not work. When the modem is inserted, is the 'sierra_net' driver loaded? Any chance you can get ModemManager debug logging so we can diagnose? Yep, it is loaded. http://live.gnome.org/NetworkManager/Debugging the instructions under "Debugging NetworkManager 0.8.x 3G connections" still apply to 0.9. FYI I have a 306 that I've tested with so at least we expect it to work. Following that instructions, herewith I attached the log result. Bit more info, I already created a "Telkomsel Flash" connection using nm-connection-editor, connecting by clicking on it from the gnome-shell applet. Tried twice, same result no connection. On first try it shows "you are connected" notification but it's actually not connected (probably a gnome-shell issue). On second try it just went to disconnected message quickly. I left my WiFi connection up during the test. One more thing, I noted from the debug log, so many AT commands was sent to the modem. Wondered about this, as with my ppp chatscripts, basically I only use following AT commands to make it work flawlessly: --- start chatscript snippet --- # cease if the modem is not attached to the network yet ABORT"+CGATT: 0" ""AT TIMEOUT12 OKATH OKATE1 OKAT+CGDCONT=1,"IP","\T","",0,0 OKATD*99# TIMEOUT22 CONNECT"" --- end chatscript snippet --- Hope this helps, let me know if more is needed and thanks for the help. Thanks, Dan All the best. -arief NM-SierraUSB305_debuglog.tar.gz Description: GNU Zip compressed data ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NM 0.9 with Sierra USB 305 modem connection problems
Hi all, I'm using Debian's NM 0.9 with MM 0.5 (from experimental repo), with Sierra Wireless modem USB 305 (USB id: 1199:68a3) mobile broadband connection does not work. Actually since 0.8 it never really worked well, but on 0.8.4 release it was bit better, at least sometimes it managed to connect. Connecting with ppp chatscripts always worked flawlessly though so we can be sure it's not an issue with the modem hardware. Attached is a copy of syslog of a latest session. I'll be happy to help with more debugging. Thank you for helps and pointers. All the best. -arief Aug 26 02:44:11 mawar NetworkManager[1396]:SCPlugin-Ifupdown: devices added (path: /sys/devices/pci:00/:00:1d.7/usb2/2-1/2-1:1.7/net/wwan0, iface: wwan0) Aug 26 02:44:11 mawar NetworkManager[1396]:SCPlugin-Ifupdown: device added (path: /sys/devices/pci:00/:00:1d.7/usb2/2-1/2-1:1.7/net/wwan0, iface: wwan0): no ifupdown configuration found. Aug 26 02:44:11 mawar modem-manager[1420]: (ttyUSB0) opening serial port... Aug 26 02:44:11 mawar modem-manager[1420]: (ttyUSB3) opening serial port... Aug 26 02:44:11 mawar modem-manager[1420]: (ttyUSB2) opening serial port... Aug 26 02:44:11 mawar modem-manager[1420]: (ttyUSB1) opening serial port... Aug 26 02:44:13 mawar modem-manager[1420]: (ttyUSB0) closing serial port... Aug 26 02:44:13 mawar modem-manager[1420]: (ttyUSB0) serial port closed Aug 26 02:44:13 mawar modem-manager[1420]: (ttyUSB0) opening serial port... Aug 26 02:44:13 mawar modem-manager[1420]: (Sierra): GSM modem /sys/devices/pci:00/:00:1d.7/usb2/2-1 claimed port ttyUSB0 Aug 26 02:44:13 mawar modem-manager[1420]: (ttyUSB2) closing serial port... Aug 26 02:44:13 mawar modem-manager[1420]: (ttyUSB2) serial port closed Aug 26 02:44:13 mawar modem-manager[1420]: (Sierra): GSM modem /sys/devices/pci:00/:00:1d.7/usb2/2-1 claimed port ttyUSB2 Aug 26 02:44:13 mawar modem-manager[1420]: (ttyUSB0) closing serial port... Aug 26 02:44:13 mawar modem-manager[1420]: (ttyUSB0) serial port closed Aug 26 02:44:14 mawar modem-manager[1420]: (Sierra): GSM modem /sys/devices/pci:00/:00:1d.7/usb2/2-1 claimed port wwan0 Aug 26 02:44:19 mawar modem-manager[1420]: (ttyUSB3) closing serial port... Aug 26 02:44:19 mawar modem-manager[1420]: (ttyUSB3) serial port closed Aug 26 02:44:24 mawar modem-manager[1420]: (ttyUSB1) closing serial port... Aug 26 02:44:24 mawar modem-manager[1420]: (ttyUSB1) serial port closed Aug 26 02:44:24 mawar modem-manager[1420]: (ttyUSB1) opening serial port... Aug 26 02:44:30 mawar modem-manager[1420]: (ttyUSB1) closing serial port... Aug 26 02:44:30 mawar modem-manager[1420]: (ttyUSB1) serial port closed Aug 26 02:44:30 mawar NetworkManager[1396]: WWAN now disabled by management service Aug 26 02:44:30 mawar NetworkManager[1396]: (wwan0): new GSM/UMTS device (driver: 'sierra' ifindex: 6) Aug 26 02:44:30 mawar NetworkManager[1396]: (wwan0): exported as /org/freedesktop/NetworkManager/Devices/3 Aug 26 02:44:30 mawar NetworkManager[1396]: (wwan0): now managed Aug 26 02:44:30 mawar NetworkManager[1396]: (wwan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Aug 26 02:44:30 mawar NetworkManager[1396]: (wwan0): deactivating device (reason: 2). Aug 26 02:44:30 mawar NetworkManager[1396]: (wwan0): device state change: unavailable -> disconnected (reason 'none') [20 30 0] Aug 26 02:44:34 mawar NetworkManager[1396]: Activation (wwan0) starting connection 'Telkomsel Flash' Aug 26 02:44:34 mawar NetworkManager[1396]: (wwan0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Aug 26 02:44:34 mawar NetworkManager[1396]: Activation (wwan0) Stage 1 of 5 (Device Prepare) scheduled... Aug 26 02:44:34 mawar NetworkManager[1396]: Activation (wwan0) Stage 1 of 5 (Device Prepare) started... Aug 26 02:44:34 mawar NetworkManager[1396]: (wwan0): device state change: prepare -> need-auth (reason 'none') [40 60 0] Aug 26 02:44:34 mawar NetworkManager[1396]: Activation (wwan0) Stage 1 of 5 (Device Prepare) complete. Aug 26 02:44:34 mawar NetworkManager[1396]: Activation (wwan0) Stage 1 of 5 (Device Prepare) scheduled... Aug 26 02:44:34 mawar NetworkManager[1396]: Activation (wwan0) Stage 1 of 5 (Device Prepare) started... Aug 26 02:44:34 mawar NetworkManager[1396]: (wwan0): device state change: need-auth -> prepare (reason 'none') [60 40 0] Aug 26 02:44:34 mawar NetworkManager[1396]: Activation (wwan0) Stage 1 of 5 (Device Prepare) complete. Aug 26 02:44:34 mawar modem-manager[1420]: (ttyUSB0) opening serial port... Aug 26 02:44:34 mawar modem-manager[1420]: Modem /org/freedesktop/ModemManager/Modems/1: state changed (disabled -> enabling) Aug 26 02:44:45 mawar modem-manager[1420]: (ttyUSB2) opening serial port... Aug 26 02:44:45 mawar modem-manager[1420]: Invalid error code: 518 Aug 26 02:44:45 mawar modem-manager[1420]: Modem /org/freedesktop/ModemManager/Modems/1: state changed (e
Re: [SOLVED] nm-applet icon in gnome-shell goes to gnome2/fallback mode
On 08/10/2011 01:24 AM, Arief M Utama wrote: But after restarting my laptop, I found out that nm-applet icons has change back to gnome2-style icons. No more white-icon-with-black-background gnome-shell style. Solved by reinstalling gjs libraries. Must've got overwritten somehow. LoL@me :) Now I do wonder what else got overwritten (and removed) by the install from sources. Guess I should've known better and shouldn't do any autogen --prefix=/usr ever again :) All the best. -arief ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
nm-applet icon in gnome-shell goes to gnome2/fallback mode
Hi all, While trying to debug Debian bug#636137 (or Fedora/Redhat bug#713006) I compiled and installed network-manager from git and also from debian's experimental source. After sort of finding the culprit for the bug (put some notes on both bugtrack), I resort back to the original network-manager* packages from Debian's experimental. But after restarting my laptop, I found out that nm-applet icons has change back to gnome2-style icons. No more white-icon-with-black-background gnome-shell style. Tried many things like reinstalling network-manager*, purging and install, restarting dbus, restarting system along the way, with no luck. The old icon stayed. As I shallowly understood from reading gnome-shell panel.js, panel icons are supposed to be created by gnome-shell, but somehow it just doesn't work now. Appreciate if anyone can give help or pointers of what's going on and how to fix this. Thanks. All the best. -arief ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list