Linux Help
-
Linux is really hard uhhhh,..................................................
-
@voipmarkets said:
Linux is really hard uhhhh,..................................................
Not really. However, if you try to think like you do with Windows and use Linux, you will make it hard on yourself. Linux makes SO MUCH MORE sense than Windows. Windows is unstable in many ways because it doesn't do things like Linux. The registry? ICK! It's because Windows wants to be all proprietary, among other things.
-
Besides, @voipmarkets, if you think like that, it's a defeatist attitude. It's not hard. It's another challenge to conquer and overcome. It's another thing to learn. It's another skill to learn. If you claim to be IT, and you don't have at least A LITTLE experience and familiarity with Linux, I don't consider you IT. Learning things like the basics of vi, the essentials of how to navigate a Linux CLI, etc, are essential skills for anyone who claims to work IT.
-
@thanksaj said:
@StrongBad said:
@thanksaj said:
@MattSpeller said:
(also linux noob) Sounds like you're not saving the changes to the file you're editing???
Welcome to ML
Ditto this. If you're using CLI, it'd be
vi networking.confThen, when you're done with the changes, Esc followed by :wq and Enter. It sounds like you're making the changes but they aren't applying.
That's not normally where the configuration is. That's Ubuntu only, non-standard.
I was just using a generic name for the .conf file.
No single networking conf file in the Red Hat, Suse, Fedora world. It's by interface.
-
@voipmarkets said:
Linux is really hard uhhhh,..................................................
Not really, just like anything you have to learn it before using it. Windows is incredibly hard for Linux people who are used to the easy, simple world of configuration text files with all data nice and obvious. Windows is very complex by comparison.
-
@StrongBad said:
@thanksaj said:
@StrongBad said:
@thanksaj said:
@MattSpeller said:
(also linux noob) Sounds like you're not saving the changes to the file you're editing???
Welcome to ML
Ditto this. If you're using CLI, it'd be
vi networking.confThen, when you're done with the changes, Esc followed by :wq and Enter. It sounds like you're making the changes but they aren't applying.
That's not normally where the configuration is. That's Ubuntu only, non-standard.
I was just using a generic name for the .conf file.
No single networking conf file in the Red Hat, Suse, Fedora world. It's by interface.
I am aware of that. I was just using the word networking in place of example.conf or whatever.
-
@StrongBad said:
@voipmarkets said:
Linux is really hard uhhhh,..................................................
Not really, just like anything you have to learn it before using it. Windows is incredibly hard for Linux people who are used to the easy, simple world of configuration text files with all data nice and obvious. Windows is very complex by comparison.
This is so true!
-
Did you change the interface from DHCP to static in the config? Also which GSM gateway, it could also be that changes need to be wrote in some special way as to be stored to non-volatile memory.
-
Also what is happening if you save the file and then restart the network service? does it take or is it still using the old ip?
-
@StrongBad said:
No single networking conf file in the Red Hat, Suse, Fedora world. It's by interface.
And most firewall/gateway devices seem to be.
It's
/etc/sysconfig/network/ifcfg-device where you'd put eth0, eth1 etc (what ever your device is named, ifconfig should help in finding it) in place of device. -
He's trolling. I've spent half an hour trying to work with him. He's just messing with us. I've explained the issues and he is just being ridiculous. This is some proprietary Linux garbage on some hobby system. There is no way for us to help him and he absolutely refuses to listen or let us help him in any way.
-
@thecreativeone91 said:
@StrongBad said:
No single networking conf file in the Red Hat, Suse, Fedora world. It's by interface.
And most firewall/gateway devices seem to be.
It's
/etc/sysconfig/network/ifcfg-device where you'd put eth0, eth1 etc (what ever your device is named, ifconfig should help in finding it) in place of device.No, this isn't a real gateway or anything like that. He's making those terms up. It's a cheap, hobby PBX from some vendor that doesn't even list such a product. The only file on the machine that holds the IP address is some XML file that looks like it is meant to be edited by a web tool. There is no safe way to make changes to it. I explained what to do to fix it with the web interface and he has no interest in actually fixing it.
-
that Y im saying i dont know how to use linux
-
@StrongBad said:
@thecreativeone91 said:
@StrongBad said:
No single networking conf file in the Red Hat, Suse, Fedora world. It's by interface.
And most firewall/gateway devices seem to be.
It's
/etc/sysconfig/network/ifcfg-device where you'd put eth0, eth1 etc (what ever your device is named, ifconfig should help in finding it) in place of device.No, this isn't a real gateway or anything like that. He's making those terms up. It's a cheap, hobby PBX from some vendor that doesn't even list such a product. The only file on the machine that holds the IP address is some XML file that looks like it is meant to be edited by a web tool. There is no safe way to make changes to it. I explained what to do to fix it with the web interface and he has no interest in actually fixing it.
Wow...
Well if you want to try out a real Linux PBX load up freepbx on a Raspberry PI or something.. Would probably do better than a home grade device.
-
@voipmarkets said:
that Y im saying i dont know how to use linux
See, this is what I mean? I explained over and over that Linux wasn't a thing and that his issues have nothing to do with Linux. He knows not to say this, but repeats it over and over anyway.
No matter how many times I explained that what he has is nothing like any normal Linux and none of the config files are there because it is completely proprietary he refuses to tell me what device he has, what OS he is running, how he acquired it and just demands, over and over, to be told the "standard way to do this in Linux."
For thirty minutes I've explained that there is no "standard way to do anything" and that he cant keep asking that. Yet, there he does it again.
The system is proprietary, knowing Linux has nothing to do with it.
-
@thecreativeone91 said:
@StrongBad said:
@thecreativeone91 said:
@StrongBad said:
No single networking conf file in the Red Hat, Suse, Fedora world. It's by interface.
And most firewall/gateway devices seem to be.
It's
/etc/sysconfig/network/ifcfg-device where you'd put eth0, eth1 etc (what ever your device is named, ifconfig should help in finding it) in place of device.No, this isn't a real gateway or anything like that. He's making those terms up. It's a cheap, hobby PBX from some vendor that doesn't even list such a product. The only file on the machine that holds the IP address is some XML file that looks like it is meant to be edited by a web tool. There is no safe way to make changes to it. I explained what to do to fix it with the web interface and he has no interest in actually fixing it.
Wow...
Well if you want to try out a real Linux PBX load up freepbx on a Raspberry PI or something.. Would probably do better than a home grade device.
I mentioned that he needed a business class PBX too. What he is running is some toy that can't be supported.
-
first go learn what is mean voip gateway and what is pbx means...............................ok
you dont know what is networking -
@voipmarkets said:
first go learn what is mean voip gateway and what is pbx means...............................ok
you dont know what is networkingYes, that is the problem.
-
What's the Linux distro in question? We need to know that in order to help.
-
What's the device make and model?
