- This topic has 26 replies, 7 voices, and was last updated Mar 31-4:57 pm by seaken64.
-
Posts
-
Anonymous
I don’t mind people using Live USB for whatever reasons it might be, but would only like to remind:
Some of my serious work involves helping some folks with their home computers. … I can look at their hardware without touching their hard drive.
As I already mentioned: “Demonstrating an OS, installing OS or sometimes saving some file from some machine.”
I can keep lessons on my own disk and carry it from house to house.
You can do that on any USB without Live OS too.
It is also convenient to keep a separate drive for privacy and security.
No, it’s not. For security you would never use any kind of (writable media) persistence, but Live OS with NO persistence (== live CD).
To hide your p0rn from your partner (== privacy), any USB without OS install/persistence would also do the job.There are lots of good ways to use this persistence system.
I know one good reason: help capitalism bloosom. Boost sales of USB pen drives. 😉
Maybe of interest for some of you, if you don’t know it already:
https://superuser.com/questions/483496/what-downsides-are-there-to-running-an-os-off-of-a-flash-drive-instead-of-a-hardAlso, you would never use any kind of flash storage (SSD, eMMC, SD, USB …) as a permanent storage (== archiving), but only as a temporary (== data transport) storage. For archiving purposes, HD and archival CD/DVD is still the best we currently have.
However, all this has nothing to do with “See active network connection in LiveUSB” and I’m pulling the line here.
Sorry for the “off-topic” on the one side, but on the other side, it’s good as a reminder as what for USB storage was (not) meant to be.seaken64
Well, I suppose we’ll have to agree to disagree. Porn may be one thing one wants to keep to themselves but that’s not the only reason to keep an OS in your pocket. If I want to use a clients computer and leave no trace and don’t want to expose my data and passwords, etc. Yes, you are technically correct, it’s not really secure. But it does make it easier for me to not leave stuff behind and I can make changes on the fly and update my database all in my portable OS. A regular live USB or DVD is not as easy to use when you want to make running updates.
Making backups and snapshots is needed of course. I cannot claim it is as good as some archival medium. That’s not the point. And I don’t want to use the cloud. I keep the data in my hands instead of some distant server. I do keep my main files on my servers at our company. But when I’m on the road the portable persistent OS makes my job easier.
Seaken64
If you have 1 (one) and only one WiFi card, then it can only be cold ‘wlan0’ and NEVER ‘wlan1’, ‘wlan2’, ‘wlan3’ …
If you have 1 (one) and only one Ethernet card, then it can only be cold ‘eth0’ and NEVER ‘eth1’, ‘eth2’, ‘eth3’ …The ONLY way you might ever in your life see something like ‘eth3’ or ‘wlan4’ is:
You did a custom PC build and you know exactly what you are doing and why or you’re an IT professional working in an computer center.
The only other possible reason is: you have some broken configuration files (who~ or whatever caused it).I have a few computers that have more than one WiFi card and/or more than one Ethernet card.
I don’t think the only way to get something like wlan3 is as you stated. It makes sense to me that if I have only ONE interface card it will get assigned to wlan0 unless I programmed it otherwise.
But just yesterday and today I noticed that I got two assignments for the wireless that were beyond the expected wlan0 or wlan1. I did not program anything. These are regular antiX installs.
One laptop is running LiveUSB and has a built-in wireless adapter that was acting up. I disabled it and plugged in a Belkin USB wifi adapter. It was assigned wlan3. The previous wireless adapter that I turned off was at wlan0.
Today, I used that same Belkin USB wifi adapter in another laptop that also has a built-in wireless adapter. This system is an antiX 17.4 installed to the hard disk. I did not disable the onboard wifi. I just ignored it and plugged in the Belkin USB adapter. That adapter got assigned wlx002275adnnnn (the last four n’s are taking place of the actual digits since I’m not sure if I should expose the actual MAC address). This is the MAC address of the device following the “wlx”. I have seen something similar to this before, prior to me starting this thread.
So, anyway. I don’t thinks it’s as simple as “only way you might ever”. It may be something I am doing but I did not make any changes to the network interface assignments. This is straight antiX config files.
And my query remains the same. Is there any more “dynamic” widget that will show the active network on the screen, regardless of what ID the interface is assigned?
Thank you.
Seaken64
any more “dynamic” widget that will show the active network on the screen, regardless of what ID the interface is assigned?
You can try installing the package “mate-system-monitor”
…or
how do I display wireless info in conky?I’m fairly ignorant regarding wi-fi, but would expect a “MAC address” to be nn:nn:nn… colon-delimited string.
wlx0022… maybe that’s an essid?
/etc/udev/rules.d/70-persistent-net.rules
You can try editing here ~~ delete the wlan1 wlan2 lines if present, and rename the current wlan3 to wlan0.For a liveboot system,
/live/boot-dev/antiX/state/machine/*/files/etc/udev/rules.d/70-persistent-net.rulesThanks Skidoo, I’ll check that out.
And it is the MAC address digits without the separators. I checked the MAC address and it is the same digits. I’m not sure why the wireless ID is assigned in that way. It is usually wlan#. Anyway, I’m ok with that. I can always just look in the terminal with ifconfig. But it would be nice to have a little widget showing activity.
Seaken64
What I stated above is so, like it or not — if you have one and only one wi-fi interface, it’s always gonna be wlan0.
If you have two, they’re gonna be wlan0 and wlan1 and so on — as long as you use the OS in a ‘normal’ way.
The same applies for all other interfaces / network cards.The only way you can get something else is if you mess around with interfaces or use your OS in an ‘abnormal’ way.
One example would be using an OS installed on one computer, on another computer (the same applies for ‘permanence’).
Then the one and only wi-fi interface wlan0 will become wlan1 on the second computer, wlan2 on the third computer and so on.In that case when you’re using your OS in an ‘abnormal’ way, you’ll have to reset those interfaces at some point.
As for:
… it would be nice to have a little widget showing activity.
If I understand properly, a widget is something that’s occupying the space on the screen in exchange for showing some information.
One constantly open Terminal window, showing some information becomes a ‘widget’ too, if it’s in foreground all the time.
Keep your Terminal in foreground, give it semi-transparency and some fancy colors and you’ve got your ‘widget’. 😉So, the solution is pretty easy: nmcli and a constantly open terminal window.
To check Network Manager status:
# nmcli general statusTo check all available interfaces and their status:
# nmcli dev statusTo check the status of wi-fi interface:
# nmcli dev wifiTo list all available wi-fi’s, your adapter can see:
# nmcli dev wifi listTo show all already configured connections:
# nmcli con showTo show a detailed information about your wi-fi:
# nmcli dev showTo disconnect one interface:
# nmcli dev disconnect iface INTERFACE_NAMETo connect one interface:
# nmcli con up id INTERFACE_NAMEIt can do much more, if one could only read (and understand) those bloody man-pages.
http://manpages.ubuntu.com/manpages/cosmic/en/man1/nmcli.1.htmlIf you don’t have nmcli installed yet, or if you’re missing some components, you can do:
# apt-get install network-manager modemmanager mobile-broadband-provider-info network-manager-vpnc network-manager-openvpn network-manager-pptpDepending on what are you intending to do / monitor, there are many other useful utilities like:
bmon
iftop
nethogs
tcptrackntop
(ntop runs in web browser window!)
rokytnji
Just info from a dude who changes wifi hardware on his installs. Every time you change the physical wifi hardware. The kernel picks up the hardware. Assigns the driver if it has it. Firmware also included if there. Then a new wlan interface assigned.
Not improper antix use.
On my panasonic CF -48. I disabled internal wireless g intel card and just used the wireless N pmcia card I had. Being a older antix install.
eth1 was original wireless. eth0 was landline. When card wireless N was used. Assignment went up a notch.
Hence : eth2Helps to know these things when editing Conky.
Edit: Being Saturday morning. I am one of the shameless abnormal AntiX users who swap hard drives also from computer to computer. Never had a problem with ether.
2nd Edit: I once ran a net monitor widget on tint2 panel in Fluxbox . Don’t ask how I did it. I google searched and just did it.
- This reply was modified 4 years, 1 month ago by rokytnji.
- This reply was modified 4 years, 1 month ago by rokytnji.
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsWhat I stated above is so, like it or not — if you have one and only one wi-fi interface, it’s always gonna be wlan0.
If you have two, they’re gonna be wlan0 and wlan1 and so on — as long as you use the OS in a ‘normal’ way.
The same applies for all other interfaces / network cards.The only way you can get something else is if you mess around with interfaces or use your OS in an ‘abnormal’ way.
One example would be using an OS installed on one computer, on another computer (the same applies for ‘permanence’).
Then the one and only wi-fi interface wlan0 will become wlan1 on the second computer, wlan2 on the third computer and so on.In that case when you’re using your OS in an ‘abnormal’ way, you’ll have to reset those interfaces at some point.
Well my knowledge of the inner workings of the network interface ID’s is not good. Perhaps I will study this so satisfy my curiosity. But probably not. All I know is that I am using antiX in no abnormal way. I install antiX to the hard disk and plug in a USB wireless adapter. If that’s abnormal I’m missing something. I would like to know why I am not getting wlan0 or wlan1. But it is not a big deal and is not stopping me from being productive so I will move on.
And thanks for the input on using the terminal. For now, I am satisfied to just use the terminal to double-check that I have a live connection to my Access Point before I try to use the LAN or internet. I miss the little conkey display but oh well.
Seaken64
I would like to know why I am not getting wlan0 or wlan1.
Something, some non-obvious detail, changed across boots and the system preserved the details of the “previously seen” interfaces. I’ve seem eth3 assigned, after having used using same liveboot pendrive on multiple machines.
“If I understand properly”
. . .
“as long as you use the OS in a ‘normal’ way”Due to the overall excellent spelling and grammar in those posts, we may not easily recognize it has been posted by a non-native English writer. Seaken, normal was wrapped in quotes ~~ suggesting that the writer was recommending wide latitude during our reading/interpretation of that word. Although a native might use the phrase “wait a moment, I want to make sure I understand correctly”… properly? It’s essentially a perfect synonym, yet I expect few natives would ever choose that word in this context.
To clarify, both installs from the last two episodes I reported are hard disk installs and are not Live. I don’t see how there could be any association with other machines. The USB wireless adapter was the same used on both machines. But I don’t see how that could apply either.
Like I said, I’m ok with it. It’s just a weird occurance that I don’t really need a solution to. But maybe the developers would be interested in this anomaly.
Seaken64
not liveboot. Understood.
It would be easy to test whether editing /etc/udev/rules.d/70-persistent-net.rules resolves the issue. At this point, have you already done so?not liveboot. Understood.
It would be easy to test whether editing /etc/udev/rules.d/70-persistent-net.rules resolves the issue. At this point, have you already done so?No. I will try that. I’ve been working on this music player on another machine and I’m not done with that project yet. I will follow up with this after I am finished with the other project.
Thank you,
Seaken64
- You must be logged in to reply to this topic.
