TODO list for each hardware target can be found as sticky topic in the corresponding forum
saving changes on ip02 Hello,
|
|
|
Administrator has disabled public posting |
Re: saving changes on ip02Only files in /persistent will keep their changes. Most of these are symlinked from /, particularly the files in /etc/asterisk, which you are probably interested in. I plan on making this more transparent so that just about any file can be changed. |
|
|
Administrator has disabled public posting |
Re: saving changes on ip02 Why is impossible to change default root password for ssh access ?
|
|
|
Administrator has disabled public posting |
Re: saving changes on ip02 It seems to be true that /etc/passwd remains unchanged. I changed it when I built the firmware image so I haven't had this problem but I suspect the reason is that the passwd command performs security checks, which could include making sure that /etc/passwd is not a symlink. This problem should also go away with my planned changes.
|
|
|
Administrator has disabled public posting |
Re: saving changes on ip02 I didn't go through entire procedure of building my own firmware. I tried that ,downloaded svn source code but miserably failed at "make uBoot" step from README file. I just completed step 1 (read README file). It says "No rule to make target" like I am doing it wrongly or from wrong directory(root of downloaded files I also tried from uBoot folder with same effect) and README does not say where to do it just do "make uBoot". I am green in this so I failed to prceed and never reached step "make menuconfig".
|
|
|
Administrator has disabled public posting |
Re: saving changes on ip02 Hi uros09,
|
|
|
Administrator has disabled public posting |
Re: saving changes on ip02 Ok
|
|
|
Administrator has disabled public posting |
Re: saving changes on ip02 I also had strange situation when I come back from work I found out device unreachable for ssh access (refusing connections before asking for password with some message about identity), and port 1 and port 2 leads not turned on and GUI unreachable too. The day before I changed just extensions.conf and commented out 2 lines (where it includes other files for which I think are calling some commands which overwrite changes and add some unwanted dialplan and configuration). After reboot I could login via ssh and saw no dahdi device has been found.I accessed GUI (after I removed ; from those 2 lines) and it shows no FXO port, no analog hardware... My /etc/dahdi/system.conf lost fxo and fxs lines.
|
|
|
Administrator has disabled public posting |
Re: saving changes on ip02 ok I think I managed to put device under control by disabling asterisk manager interface,http-static, commenting extensions.conf first line where it includes extensions_custom.conf, completly disabling ssh from outside of my local network enabling it just from LAN, disabling remote managment of my router.
|
|
|
Administrator has disabled public posting |
Re: saving changes on ip02 It works fine. I enabled GUI and configured it and everything is fine. I can see callerid for incomming calls. Thing I can't find in GUI wchich could be useful is
|
|
|
Administrator has disabled public posting |
- Index
- » Developers
- » IP0x
- » saving changes on ip02
Most Active Users
Board Info
- Board Stats: Total Users: 2587 Total Topics: 299 Total Polls: 1 Total Posts: 1727 Dormant
- User Info: Newest User : user2553 Members Online: 0 Guests Online: 223
- Online There are no members online
- Topic
- New
- Locked
- Sticky
- Active
- New/Active
- New/Locked
- New Sticky
- Locked/Active
- Active/Sticky
- Sticky/Locked
- Sticky/Active/Locked