Date   

Re: ASL-DMR boot will not login to "Master Server"

Tito Lopez - YN1OB
 

I have run into that problem before, I fixed it by typing the Ip address of the master server instead of the name. You will get that number once ping the name as Steve prompted.


On Wed, Nov 4, 2020, 14:23 Steve N4IRS <szingman@...> wrote:
ping 3102.repeater.net what is the result?

Sent by smoke signal (AT&T)



From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Gary <w5bi@...>
Sent: Wednesday, November 4, 2020, 4:42 PM
To: main@DVSwitch.groups.io
Subject: [DVSwitch] ASL-DMR boot will not login to "Master Server"

Attached snippets from MMDVM_Bridge.ini and log file. Boot stalls at Master login. What is awry?

[General]
Callsign=w5bi
Id=316229205
Timeout=180
Duplex=0
.
.
[DMR Network]
Enable=1
Address=3102.repeater.net
Port=62031
Jitter=360
Local=62032
Password=passw0rd
# for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md
# for XLX the syntax is: Options=XLX:4009
# Options=
Slot1=0
Slot2=1
Debug=1
.
.
/var/log/mmdvm
.
.
M: 2020-11-04 21:05:35.728 DMR, Transmitting on 127.0.0.1:31100, and listening on port 31103.  Result = 1
M: 2020-11-04 21:05:35.728 MMDVM_Bridge-20200309_V1.5.1 is running
E: 2020-11-04 21:05:47.369 DMR, Login to the master has failed, retrying network ...
M: 2020-11-04 21:05:47.369 DMR, Closing DMR Network
M: 2020-11-04 21:05:47.369 DMR, Opening DMR Network
E: 2020-11-04 21:05:57.528 DMR, Login to the master has failed, retrying network ...


Re: YSFGateway with FCS bridging

David Young
 

I have been using FCS00479 to test with.


Re: YSFGateway with FCS bridging

Steve N4IRS
 

What FCS room can I point MB at to see the error?

On 11/4/20 5:20 PM, David Young wrote:
Hi Steve,

I downloaded your latest MMDVM_Bridge files off github and replaced the MMDVM_Bridge.amd64 new over to my FCS to DMR bridge.  Also replaced the old with new MMDVM_Bridge.ini and DVSwitch.ini files.  I still receive the Network Watchdog timeout error after each FCS transmission.  Yes, I did rename the MMDVM_Bridge.amd64 to MMDVM_Bridge.
We are using DVSwitch apps to bridge multiple modes over to a HBLink3 virtual server also running on an NFO cloud server.  I before updating to the new MMDVM_Bridge files which seem to have the same Watchdog error I tried various other configuration changes to both YSFGateway.ini and MMDVM_Bridge.ini files with no success, always generating the Network Watchdog error message when transmitting from any FCS room we have bridged to the HBLink3 server.  The best solution I could come up with was bridging the FCS rooms to our XLX server and then bridging the XLX server to DMR using DVSwitch modules.  This cut down my Network Watchdog errors to only approximately 30 percent of the time.  Kind of a round-about way of doing the bridging but still not completely eliminating the errors.  Going to attach a PDF file block diagram of how we are doing our bridging system.  Hope this will help.
--
Dave WB6DTB


Re: #mmdvm_bridge #mmdvm_bridge

swinger72@...
 

Ok yes its true. Anyway i solve the initial issue about mb1 and mb2 crash . 


Re: ASL-DMR boot will not login to "Master Server"

Steve N4IRS
 

ping 3102.repeater.net what is the result?

Sent by smoke signal (AT&T)



From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Gary <w5bi@...>
Sent: Wednesday, November 4, 2020, 4:42 PM
To: main@DVSwitch.groups.io
Subject: [DVSwitch] ASL-DMR boot will not login to "Master Server"

Attached snippets from MMDVM_Bridge.ini and log file. Boot stalls at Master login. What is awry?

[General]
Callsign=w5bi
Id=316229205
Timeout=180
Duplex=0
.
.
[DMR Network]
Enable=1
Address=3102.repeater.net
Port=62031
Jitter=360
Local=62032
Password=passw0rd
# for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md
# for XLX the syntax is: Options=XLX:4009
# Options=
Slot1=0
Slot2=1
Debug=1
.
.
/var/log/mmdvm
.
.
M: 2020-11-04 21:05:35.728 DMR, Transmitting on 127.0.0.1:31100, and listening on port 31103.  Result = 1
M: 2020-11-04 21:05:35.728 MMDVM_Bridge-20200309_V1.5.1 is running
E: 2020-11-04 21:05:47.369 DMR, Login to the master has failed, retrying network ...
M: 2020-11-04 21:05:47.369 DMR, Closing DMR Network
M: 2020-11-04 21:05:47.369 DMR, Opening DMR Network
E: 2020-11-04 21:05:57.528 DMR, Login to the master has failed, retrying network ...


Re: YSFGateway with FCS bridging

David Young
 

Hi Steve,

I downloaded your latest MMDVM_Bridge files off github and replaced the MMDVM_Bridge.amd64 new over to my FCS to DMR bridge.  Also replaced the old with new MMDVM_Bridge.ini and DVSwitch.ini files.  I still receive the Network Watchdog timeout error after each FCS transmission.  Yes, I did rename the MMDVM_Bridge.amd64 to MMDVM_Bridge.
We are using DVSwitch apps to bridge multiple modes over to a HBLink3 virtual server also running on an NFO cloud server.  I before updating to the new MMDVM_Bridge files which seem to have the same Watchdog error I tried various other configuration changes to both YSFGateway.ini and MMDVM_Bridge.ini files with no success, always generating the Network Watchdog error message when transmitting from any FCS room we have bridged to the HBLink3 server.  The best solution I could come up with was bridging the FCS rooms to our XLX server and then bridging the XLX server to DMR using DVSwitch modules.  This cut down my Network Watchdog errors to only approximately 30 percent of the time.  Kind of a round-about way of doing the bridging but still not completely eliminating the errors.  Going to attach a PDF file block diagram of how we are doing our bridging system.  Hope this will help.
--
Dave WB6DTB


ASL-DMR boot will not login to "Master Server"

Gary
 

Attached snippets from MMDVM_Bridge.ini and log file. Boot stalls at Master login. What is awry?

[General]
Callsign=w5bi
Id=316229205
Timeout=180
Duplex=0
.
.
[DMR Network]
Enable=1
Address=3102.repeater.net
Port=62031
Jitter=360
Local=62032
Password=passw0rd
# for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md
# for XLX the syntax is: Options=XLX:4009
# Options=
Slot1=0
Slot2=1
Debug=1
.
.
/var/log/mmdvm
.
.
M: 2020-11-04 21:05:35.728 DMR, Transmitting on 127.0.0.1:31100, and listening on port 31103.  Result = 1
M: 2020-11-04 21:05:35.728 MMDVM_Bridge-20200309_V1.5.1 is running
E: 2020-11-04 21:05:47.369 DMR, Login to the master has failed, retrying network ...
M: 2020-11-04 21:05:47.369 DMR, Closing DMR Network
M: 2020-11-04 21:05:47.369 DMR, Opening DMR Network
E: 2020-11-04 21:05:57.528 DMR, Login to the master has failed, retrying network ...


Re: YSFGateway with FCS bridging

Steve N4IRS
 

Can you tell me what HBlink you are connecting to so I can try to recreate it?

On 11/4/2020 2:14 PM, David Young wrote:
With the new DVSwitch Server package, is it still required to use YSFGateway when bridging an FCS room to DMR?
Reason I'm asking, when bridging FCS to DMR with the previous DVSwitch, YSFGateway was required but I would get Network Watchdog timeout errors after each FCS transmission. 
--
Dave WB6DTB


Re: YSFGateway with FCS bridging

Steve N4IRS
 

Yes, you need YSFGateway. Let us know if you see the timeout message.

On 11/4/2020 2:14 PM, David Young wrote:
With the new DVSwitch Server package, is it still required to use YSFGateway when bridging an FCS room to DMR?
Reason I'm asking, when bridging FCS to DMR with the previous DVSwitch, YSFGateway was required but I would get Network Watchdog timeout errors after each FCS transmission. 
--
Dave WB6DTB


YSFGateway with FCS bridging

David Young
 

With the new DVSwitch Server package, is it still required to use YSFGateway when bridging an FCS room to DMR?
Reason I'm asking, when bridging FCS to DMR with the previous DVSwitch, YSFGateway was required but I would get Network Watchdog timeout errors after each FCS transmission. 
--
Dave WB6DTB


Re: Setting the IP address on the Pi

Mike KB8JNM
 

Have you ever tried to restart the network.service after boot ?

On 11/4/2020 12:49 PM, Bob Brown wrote:
The same for as well this is the first time I have had an eth0 not be an eth0

but it is what worked for me YMMV 

now this is an older pi2 or 3 I believe it was in the junque box

I was just trying this out to see how it worked. and testing the ease of set up instructions.

I say so far it was easy, except for the static IP part.

I will play with it some more tonight I may even try a different pi to see if it is common with a fresh image


Sm0ke


--
Thanks in Advance

   Bob, WØNQX

   Kansas City Metro Area
   
   http://drsm0ke.net
   
Quis custodiet ipsos custodes?

"Some of my finest hours have been spent on my back veranda, smoking hemp and observing as far as my eye can see." Thomas Jefferson
--
--


On Wed, Nov 4, 2020 at 11:22 AM Steve N4IRS <szingman@...> wrote:
hmmm, for me it's eth0.

On 11/4/2020 12:16 PM, Bob Brown wrote:
I burned from the pi image on the web site in your original email announcement.


I used Balena-etcher for the write to card.




--
Thanks in Advance

   Bob, WØNQX

   Kansas City Metro Area
   
   http://drsm0ke.net
   
Quis custodiet ipsos custodes?

"Some of my finest hours have been spent on my back veranda, smoking hemp and observing as far as my eye can see." Thomas Jefferson
--
--


On Wed, Nov 4, 2020 at 11:06 AM Steve N4IRS <szingman@...> wrote:
Bob,
Is this the DVSwitch Server image or did you do a pat-get install
dvswitch-server on a running system?

On 11/4/2020 11:34 AM, Bob Brown wrote:
> Update, with the help of Steve - N4IRS
>
> Mornin' Steve, and all other ships at sea...
>
> Well, I have had my Coffee and I made a few changes as suggested.
>
> 1. Here is what I did on the cmdline.txt file in the /boot/ directory
>
> ~~~~~~~~~~~~~~
> console=serial0,115200 console=tty1 root=PARTUUID=ba1c0260-02 rootfstype=ext4
> elevator=deadline fsck.repair=yes rootwait ipv6.disable=1
> ~~~~~~~~~~~~~~
>
> It worked to disable the IPv6, I tried this first to see what happens, it disabled the IPv6 but the 169.xxx.xxx.xxx dhcp address stayed.
>
> So I did the next step as the 2nd suggestion.
>
> 2. The is funny on this pi, the naming scheme "eth0" is not what it is called on this pi it is some long string of characters:  "enxb827eb692453"
>
> I did an "ifconfig" first to get the name of the eth0 interface.
>
> I then copied that string "enxb827eb692453"
> Replacing the "eth0" with the string "enxb827eb692453"
>
> This I put at the end of the "/etc/dhcpcd.conf" file
>
> ~~~~~~~~~~~~~~~~
> interface enxb827eb692453
> static ip_address=10.20.20.10/24
> static routers=10.20.20.254
> static domain_name_servers=4.4.4.4 8.8.8.8
> ~~~~~~~~~~~~~~~~~
>
> I did this editing with "sudo nano" then saved of course in both files...
> Using nano by itself would not allow a save, I had to use sudo.
>
> Then Rebooted and checked for IP change, It worked! :)
>
> The end result was a static IPv4 address and no IPv6.
>
> All for now
>
> Many thanks to all that wrote back.
>
> I hope this helps someone else.
>
> Bob, W0NQX
> aka DrSm0ke
>
>
>
>
>
>
>
>
>
>








Re: Setting the IP address on the Pi

Steve N4IRS
 

The "feature" is called Predictable Network Interface Names. It is supposed to make sure the name is the same across reboots, after other network interfaces are added. What I don't yet understand is why it triggers for Bob and not anyone else (so far)
I love my job, I love my job...

On 11/4/2020 12:49 PM, Bob Brown wrote:
The same for as well this is the first time I have had an eth0 not be an eth0

but it is what worked for me YMMV 

now this is an older pi2 or 3 I believe it was in the junque box

I was just trying this out to see how it worked. and testing the ease of set up instructions.

I say so far it was easy, except for the static IP part.

I will play with it some more tonight I may even try a different pi to see if it is common with a fresh image


Sm0ke


--
Thanks in Advance

   Bob, WØNQX

   Kansas City Metro Area
   
   http://drsm0ke.net
   
Quis custodiet ipsos custodes?

"Some of my finest hours have been spent on my back veranda, smoking hemp and observing as far as my eye can see." Thomas Jefferson
--
--


On Wed, Nov 4, 2020 at 11:22 AM Steve N4IRS <szingman@...> wrote:
hmmm, for me it's eth0.

On 11/4/2020 12:16 PM, Bob Brown wrote:
I burned from the pi image on the web site in your original email announcement.


I used Balena-etcher for the write to card.




--
Thanks in Advance

   Bob, WØNQX

   Kansas City Metro Area
   
   http://drsm0ke.net
   
Quis custodiet ipsos custodes?

"Some of my finest hours have been spent on my back veranda, smoking hemp and observing as far as my eye can see." Thomas Jefferson
--
--


On Wed, Nov 4, 2020 at 11:06 AM Steve N4IRS <szingman@...> wrote:
Bob,
Is this the DVSwitch Server image or did you do a pat-get install
dvswitch-server on a running system?

On 11/4/2020 11:34 AM, Bob Brown wrote:
> Update, with the help of Steve - N4IRS
>
> Mornin' Steve, and all other ships at sea...
>
> Well, I have had my Coffee and I made a few changes as suggested.
>
> 1. Here is what I did on the cmdline.txt file in the /boot/ directory
>
> ~~~~~~~~~~~~~~
> console=serial0,115200 console=tty1 root=PARTUUID=ba1c0260-02 rootfstype=ext4
> elevator=deadline fsck.repair=yes rootwait ipv6.disable=1
> ~~~~~~~~~~~~~~
>
> It worked to disable the IPv6, I tried this first to see what happens, it disabled the IPv6 but the 169.xxx.xxx.xxx dhcp address stayed.
>
> So I did the next step as the 2nd suggestion.
>
> 2. The is funny on this pi, the naming scheme "eth0" is not what it is called on this pi it is some long string of characters:  "enxb827eb692453"
>
> I did an "ifconfig" first to get the name of the eth0 interface.
>
> I then copied that string "enxb827eb692453"
> Replacing the "eth0" with the string "enxb827eb692453"
>
> This I put at the end of the "/etc/dhcpcd.conf" file
>
> ~~~~~~~~~~~~~~~~
> interface enxb827eb692453
> static ip_address=10.20.20.10/24
> static routers=10.20.20.254
> static domain_name_servers=4.4.4.4 8.8.8.8
> ~~~~~~~~~~~~~~~~~
>
> I did this editing with "sudo nano" then saved of course in both files...
> Using nano by itself would not allow a save, I had to use sudo.
>
> Then Rebooted and checked for IP change, It worked! :)
>
> The end result was a static IPv4 address and no IPv6.
>
> All for now
>
> Many thanks to all that wrote back.
>
> I hope this helps someone else.
>
> Bob, W0NQX
> aka DrSm0ke
>
>
>
>
>
>
>
>
>
>









Re: Setting the IP address on the Pi

Bob Brown
 

The same for as well this is the first time I have had an eth0 not be an eth0

but it is what worked for me YMMV 

now this is an older pi2 or 3 I believe it was in the junque box

I was just trying this out to see how it worked. and testing the ease of set up instructions.

I say so far it was easy, except for the static IP part.

I will play with it some more tonight I may even try a different pi to see if it is common with a fresh image


Sm0ke


--
Thanks in Advance

   Bob, WØNQX

   Kansas City Metro Area
   
Quis custodiet ipsos custodes?

"Some of my finest hours have been spent on my back veranda, smoking hemp and observing as far as my eye can see." Thomas Jefferson
--
--


On Wed, Nov 4, 2020 at 11:22 AM Steve N4IRS <szingman@...> wrote:
hmmm, for me it's eth0.

On 11/4/2020 12:16 PM, Bob Brown wrote:
I burned from the pi image on the web site in your original email announcement.


I used Balena-etcher for the write to card.




--
Thanks in Advance

   Bob, WØNQX

   Kansas City Metro Area
   
   http://drsm0ke.net
   
Quis custodiet ipsos custodes?

"Some of my finest hours have been spent on my back veranda, smoking hemp and observing as far as my eye can see." Thomas Jefferson
--
--


On Wed, Nov 4, 2020 at 11:06 AM Steve N4IRS <szingman@...> wrote:
Bob,
Is this the DVSwitch Server image or did you do a pat-get install
dvswitch-server on a running system?

On 11/4/2020 11:34 AM, Bob Brown wrote:
> Update, with the help of Steve - N4IRS
>
> Mornin' Steve, and all other ships at sea...
>
> Well, I have had my Coffee and I made a few changes as suggested.
>
> 1. Here is what I did on the cmdline.txt file in the /boot/ directory
>
> ~~~~~~~~~~~~~~
> console=serial0,115200 console=tty1 root=PARTUUID=ba1c0260-02 rootfstype=ext4
> elevator=deadline fsck.repair=yes rootwait ipv6.disable=1
> ~~~~~~~~~~~~~~
>
> It worked to disable the IPv6, I tried this first to see what happens, it disabled the IPv6 but the 169.xxx.xxx.xxx dhcp address stayed.
>
> So I did the next step as the 2nd suggestion.
>
> 2. The is funny on this pi, the naming scheme "eth0" is not what it is called on this pi it is some long string of characters:  "enxb827eb692453"
>
> I did an "ifconfig" first to get the name of the eth0 interface.
>
> I then copied that string "enxb827eb692453"
> Replacing the "eth0" with the string "enxb827eb692453"
>
> This I put at the end of the "/etc/dhcpcd.conf" file
>
> ~~~~~~~~~~~~~~~~
> interface enxb827eb692453
> static ip_address=10.20.20.10/24
> static routers=10.20.20.254
> static domain_name_servers=4.4.4.4 8.8.8.8
> ~~~~~~~~~~~~~~~~~
>
> I did this editing with "sudo nano" then saved of course in both files...
> Using nano by itself would not allow a save, I had to use sudo.
>
> Then Rebooted and checked for IP change, It worked! :)
>
> The end result was a static IPv4 address and no IPv6.
>
> All for now
>
> Many thanks to all that wrote back.
>
> I hope this helps someone else.
>
> Bob, W0NQX
> aka DrSm0ke
>
>
>
>
>
>
>
>
>
>








recommendation for purchase of NWDigital Thumb DV

thlongan@...
 

I would like to get started and setup a DVSwitch Server. I would like recommendations for the purchase of Digital Thumb DV. 
Thanks for your help.


Re: Setting the IP address on the Pi

Steve N4IRS
 

Mike,
I don't remember a issue with loading the network from boot, but I'm old and forget things. ;)

Most of the support programs (gateways etc) do get unhappy if they can't connect to the internet on startup. I built a service that holds off starting any of those services until the cost can connect to the internet.

Steve

On 11/4/2020 12:27 PM, Mike KB8JNM wrote:
I do not know if it is relevent or not.

I remember a issue with a needed delay on boot in networking preventing loading network properly on boot.

I tried a quick search to find it, but with to many results for me to look through in a available amount of time.

But perhaps my mention of it will jar someones memory of it.

On 11/4/2020 11:34 AM, Bob Brown wrote:
Update, with the help of Steve - N4IRS

Mornin' Steve, and all other ships at sea...

Well, I have had my Coffee and I made a few changes as suggested.

1. Here is what I did on the cmdline.txt file in the /boot/ directory

~~~~~~~~~~~~~~
console=serial0,115200 console=tty1 root=PARTUUID=ba1c0260-02 rootfstype=ext4
elevator=deadline fsck.repair=yes rootwait ipv6.disable=1
~~~~~~~~~~~~~~

It worked to disable the IPv6, I tried this first to see what happens, it disabled the IPv6 but the 169.xxx.xxx.xxx dhcp address stayed.

So I did the next step as the 2nd suggestion.

2. The is funny on this pi, the naming scheme "eth0" is not what it is called on this pi it is some long string of characters: "enxb827eb692453"

I did an "ifconfig" first to get the name of the eth0 interface.

I then copied that string "enxb827eb692453"
Replacing the "eth0" with the string "enxb827eb692453"

This I put at the end of the "/etc/dhcpcd.conf" file

~~~~~~~~~~~~~~~~
interface enxb827eb692453
static ip_address=10.20.20.10/24
static routers=10.20.20.254
static domain_name_servers=4.4.4.4 8.8.8.8
~~~~~~~~~~~~~~~~~

I did this editing with "sudo nano" then saved of course in both files...
Using nano by itself would not allow a save, I had to use sudo.

Then Rebooted and checked for IP change, It worked! :)

The end result was a static IPv4 address and no IPv6.

All for now

Many thanks to all that wrote back.

I hope this helps someone else.

Bob, W0NQX
aka DrSm0ke












Re: Setting the IP address on the Pi

Mike KB8JNM
 

I do not know if it is relevent or not.

I remember a issue with a needed delay on boot in networking preventing loading network properly on boot.

I tried a quick search to find it, but with to many results for me to look through in a available amount of time.

But perhaps my mention of it will jar someones memory of it.

On 11/4/2020 11:34 AM, Bob Brown wrote:
Update, with the help of Steve - N4IRS

Mornin' Steve, and all other ships at sea...

Well, I have had my Coffee and I made a few changes as suggested.

1. Here is what I did on the cmdline.txt file in the /boot/ directory

~~~~~~~~~~~~~~
console=serial0,115200 console=tty1 root=PARTUUID=ba1c0260-02 rootfstype=ext4
elevator=deadline fsck.repair=yes rootwait ipv6.disable=1
~~~~~~~~~~~~~~

It worked to disable the IPv6, I tried this first to see what happens, it disabled the IPv6 but the 169.xxx.xxx.xxx dhcp address stayed.

So I did the next step as the 2nd suggestion.

2. The is funny on this pi, the naming scheme "eth0" is not what it is called on this pi it is some long string of characters:  "enxb827eb692453"

I did an "ifconfig" first to get the name of the eth0 interface.

I then copied that string "enxb827eb692453"
Replacing the "eth0" with the string "enxb827eb692453"

This I put at the end of the "/etc/dhcpcd.conf" file

~~~~~~~~~~~~~~~~
interface enxb827eb692453
static ip_address=10.20.20.10/24
static routers=10.20.20.254
static domain_name_servers=4.4.4.4 8.8.8.8
~~~~~~~~~~~~~~~~~

I did this editing with "sudo nano" then saved of course in both files...
Using nano by itself would not allow a save, I had to use sudo.

Then Rebooted and checked for IP change, It worked! :)

The end result was a static IPv4 address and no IPv6.

All for now

Many thanks to all that wrote back.

I hope this helps someone else.

Bob, W0NQX
aka DrSm0ke









Re: Setting the IP address on the Pi

Steve N4IRS
 

hmmm, for me it's eth0.

On 11/4/2020 12:16 PM, Bob Brown wrote:
I burned from the pi image on the web site in your original email announcement.


I used Balena-etcher for the write to card.




--
Thanks in Advance

   Bob, WØNQX

   Kansas City Metro Area
   
   http://drsm0ke.net
   
Quis custodiet ipsos custodes?

"Some of my finest hours have been spent on my back veranda, smoking hemp and observing as far as my eye can see." Thomas Jefferson
--
--


On Wed, Nov 4, 2020 at 11:06 AM Steve N4IRS <szingman@...> wrote:
Bob,
Is this the DVSwitch Server image or did you do a pat-get install
dvswitch-server on a running system?

On 11/4/2020 11:34 AM, Bob Brown wrote:
> Update, with the help of Steve - N4IRS
>
> Mornin' Steve, and all other ships at sea...
>
> Well, I have had my Coffee and I made a few changes as suggested.
>
> 1. Here is what I did on the cmdline.txt file in the /boot/ directory
>
> ~~~~~~~~~~~~~~
> console=serial0,115200 console=tty1 root=PARTUUID=ba1c0260-02 rootfstype=ext4
> elevator=deadline fsck.repair=yes rootwait ipv6.disable=1
> ~~~~~~~~~~~~~~
>
> It worked to disable the IPv6, I tried this first to see what happens, it disabled the IPv6 but the 169.xxx.xxx.xxx dhcp address stayed.
>
> So I did the next step as the 2nd suggestion.
>
> 2. The is funny on this pi, the naming scheme "eth0" is not what it is called on this pi it is some long string of characters:  "enxb827eb692453"
>
> I did an "ifconfig" first to get the name of the eth0 interface.
>
> I then copied that string "enxb827eb692453"
> Replacing the "eth0" with the string "enxb827eb692453"
>
> This I put at the end of the "/etc/dhcpcd.conf" file
>
> ~~~~~~~~~~~~~~~~
> interface enxb827eb692453
> static ip_address=10.20.20.10/24
> static routers=10.20.20.254
> static domain_name_servers=4.4.4.4 8.8.8.8
> ~~~~~~~~~~~~~~~~~
>
> I did this editing with "sudo nano" then saved of course in both files...
> Using nano by itself would not allow a save, I had to use sudo.
>
> Then Rebooted and checked for IP change, It worked! :)
>
> The end result was a static IPv4 address and no IPv6.
>
> All for now
>
> Many thanks to all that wrote back.
>
> I hope this helps someone else.
>
> Bob, W0NQX
> aka DrSm0ke
>
>
>
>
>
>
>
>
>
>








Re: Setting the IP address on the Pi

Bob Brown
 

I burned from the pi image on the web site in your original email announcement.


I used Balena-etcher for the write to card.




--
Thanks in Advance

   Bob, WØNQX

   Kansas City Metro Area
   
Quis custodiet ipsos custodes?

"Some of my finest hours have been spent on my back veranda, smoking hemp and observing as far as my eye can see." Thomas Jefferson
--
--


On Wed, Nov 4, 2020 at 11:06 AM Steve N4IRS <szingman@...> wrote:
Bob,
Is this the DVSwitch Server image or did you do a pat-get install
dvswitch-server on a running system?

On 11/4/2020 11:34 AM, Bob Brown wrote:
> Update, with the help of Steve - N4IRS
>
> Mornin' Steve, and all other ships at sea...
>
> Well, I have had my Coffee and I made a few changes as suggested.
>
> 1. Here is what I did on the cmdline.txt file in the /boot/ directory
>
> ~~~~~~~~~~~~~~
> console=serial0,115200 console=tty1 root=PARTUUID=ba1c0260-02 rootfstype=ext4
> elevator=deadline fsck.repair=yes rootwait ipv6.disable=1
> ~~~~~~~~~~~~~~
>
> It worked to disable the IPv6, I tried this first to see what happens, it disabled the IPv6 but the 169.xxx.xxx.xxx dhcp address stayed.
>
> So I did the next step as the 2nd suggestion.
>
> 2. The is funny on this pi, the naming scheme "eth0" is not what it is called on this pi it is some long string of characters:  "enxb827eb692453"
>
> I did an "ifconfig" first to get the name of the eth0 interface.
>
> I then copied that string "enxb827eb692453"
> Replacing the "eth0" with the string "enxb827eb692453"
>
> This I put at the end of the "/etc/dhcpcd.conf" file
>
> ~~~~~~~~~~~~~~~~
> interface enxb827eb692453
> static ip_address=10.20.20.10/24
> static routers=10.20.20.254
> static domain_name_servers=4.4.4.4 8.8.8.8
> ~~~~~~~~~~~~~~~~~
>
> I did this editing with "sudo nano" then saved of course in both files...
> Using nano by itself would not allow a save, I had to use sudo.
>
> Then Rebooted and checked for IP change, It worked! :)
>
> The end result was a static IPv4 address and no IPv6.
>
> All for now
>
> Many thanks to all that wrote back.
>
> I hope this helps someone else.
>
> Bob, W0NQX
> aka DrSm0ke
>
>
>
>
>
>
>
>
>
>







Re: Setting the IP address on the Pi

Steve N4IRS
 

Bob,
Is this the DVSwitch Server image or did you do a pat-get install dvswitch-server on a running system?

On 11/4/2020 11:34 AM, Bob Brown wrote:
Update, with the help of Steve - N4IRS

Mornin' Steve, and all other ships at sea...

Well, I have had my Coffee and I made a few changes as suggested.

1. Here is what I did on the cmdline.txt file in the /boot/ directory

~~~~~~~~~~~~~~
console=serial0,115200 console=tty1 root=PARTUUID=ba1c0260-02 rootfstype=ext4
elevator=deadline fsck.repair=yes rootwait ipv6.disable=1
~~~~~~~~~~~~~~

It worked to disable the IPv6, I tried this first to see what happens, it disabled the IPv6 but the 169.xxx.xxx.xxx dhcp address stayed.

So I did the next step as the 2nd suggestion.

2. The is funny on this pi, the naming scheme "eth0" is not what it is called on this pi it is some long string of characters:  "enxb827eb692453"

I did an "ifconfig" first to get the name of the eth0 interface.

I then copied that string "enxb827eb692453"
Replacing the "eth0" with the string "enxb827eb692453"

This I put at the end of the "/etc/dhcpcd.conf" file

~~~~~~~~~~~~~~~~
interface enxb827eb692453
static ip_address=10.20.20.10/24
static routers=10.20.20.254
static domain_name_servers=4.4.4.4 8.8.8.8
~~~~~~~~~~~~~~~~~

I did this editing with "sudo nano" then saved of course in both files...
Using nano by itself would not allow a save, I had to use sudo.

Then Rebooted and checked for IP change, It worked! :)

The end result was a static IPv4 address and no IPv6.

All for now

Many thanks to all that wrote back.

I hope this helps someone else.

Bob, W0NQX
aka DrSm0ke









Re: Setting the IP address on the Pi

Bob Brown
 

Update, with the help of Steve - N4IRS

Mornin' Steve, and all other ships at sea...

Well, I have had my Coffee and I made a few changes as suggested.

1. Here is what I did on the cmdline.txt file in the /boot/ directory

~~~~~~~~~~~~~~
console=serial0,115200 console=tty1 root=PARTUUID=ba1c0260-02 rootfstype=ext4 
elevator=deadline fsck.repair=yes rootwait ipv6.disable=1
~~~~~~~~~~~~~~

It worked to disable the IPv6, I tried this first to see what happens, it disabled the IPv6 but the 169.xxx.xxx.xxx dhcp address stayed. 

So I did the next step as the 2nd suggestion.

2. The is funny on this pi, the naming scheme "eth0" is not what it is called on this pi it is some long string of characters:  "enxb827eb692453" 

I did an "ifconfig" first to get the name of the eth0 interface.

I then copied that string "enxb827eb692453" 
Replacing the "eth0" with the string "enxb827eb692453"

This I put at the end of the "/etc/dhcpcd.conf" file

~~~~~~~~~~~~~~~~ 
interface enxb827eb692453
static ip_address=10.20.20.10/24
static routers=10.20.20.254
static domain_name_servers=4.4.4.4 8.8.8.8
~~~~~~~~~~~~~~~~~

I did this editing with "sudo nano" then saved of course in both files... 
Using nano by itself would not allow a save, I had to use sudo.

Then Rebooted and checked for IP change, It worked! :)

The end result was a static IPv4 address and no IPv6.

All for now

Many thanks to all that wrote back.

I hope this helps someone else.

Bob, W0NQX
aka DrSm0ke

1701 - 1720 of 9087