Welcome to RVForums.com

  • Register now and join the discussion
  • Friendliest RV Community on the web
  • Modern site for PC's, Phones, Tablets - no 3rd party apps required
  • Ask questions, help others, review campgrounds
  • Get the most out of the RV Lifestyle
  • Invite everyone to RVForums.com and let's have fun
  • Commercial/Vendors welcome

Pepwave MAX-BR1-MK2

Welcome to our community

  • Register now and join the discussion
  • Modern secure site, no 3rd party apps required
  • Invite your friends and let's have fun
  • Commercial/Vendors welcome
  • Friendliest RV community on the web
Tripped across the fix…. Subnet Mask for Management had to be changed. Now I can see it thru the mgmt IP and connect to the Starlink thru the Starlink APP while connected to the Pepwave Acess Point. Bonus!

255.255.255.255 (/32)
Interesting. Typically 255.255.255.0 is used.

Also, I personally set the DNS providers to what I want. I use 1.1.1.1 / 1.0.0.1 (cloudflare) or you can use Google: 8.8.8.8 / 8.8.4.4. I just learned with chatGPT the other day don't mix providers. Use primary and alternate from the same provider. I prefer cloudflare personally.

Which Pepwave did you get?

What was your subnet set to and how did you know what to change it to? Was it something you already had custom that was a conflict?
 
Interesting. Typically 255.255.255.0 is used.

Also, I personally set the DNS providers to what I want. I use 1.1.1.1 / 1.0.0.1 (cloudflare) or you can use Google: 8.8.8.8 / 8.8.4.4. I just learned with chatGPT the other day don't mix providers. Use primary and alternate from the same provider. I prefer cloudflare personally.

Which Pepwave did you get?

What was your subnet set to and how did you know what to change it to? Was it something you already had custom that was a conflict?
If I used the Standard Subnet Mask...all I got was a black page with a Starlink logo IF I used the address contained in the dashboard drop down. By changing the mask.....I can now get a true info page directly from the Starlink using the mgmt address 192.168.100.1

I found a thread on the Peplink forum. And someone mildly, almost unnoticed stated success with the mask change. It is at the end of the drop down. I tried it...and viola. So, it is one of the reasons I wanted to get the Starlink compatibility incorporated in the newer firmware. And I actually get dow load speeds now that are truly indicative of what Starlink should be capable of. Before...If I speed tested directly thru the Starlink router I got good speed...but thru the older pepwave I got speeds way lower than my Mobley. Didn't matter if WAN cable or WAN WiFi. It was SLOooowwww.

I went ahead and did the K version with 65 chip...figured if I ever do find an affordable 5g plan, it will pay dividends later.
 
I went ahead and did the K version with 65 chip
Nice. I have two in the box waiting to be installed and then I'll sell my former 5G units.
 
If I may ask... Why two vs the Dual cellular radio version?
 
My main Pepwave is over the driver's seat and uses a roof mounted cellular antenna with AT&T Mobley and also a AT&T 5G plan I maintain which is 100 GB/mo for $55 if I recall. I use paddle antennas for Wi-Fi that serves inside the coach, so all devices connect to this Wi-Fi. I also have a AP-ONE-AX access point which is in the basement in the bay just forward of the wet bay. This pushes good signal to the patio and aft of the coach - it was an experiment, works well. It is connected and controlled by the forward pepwave via the TP-LINK PoE managed switch.

I have a second pepwave wall mounted in the half bath electrical cabinet to the forward wall. It has a Parsec Husky roof mounted antenna as well but in this case both Wi-Fi and Cellular are connected to the roof mounted antenna. I maintain the Verizon unlimited plan in this unit which is $65/mo and is 5G as well. This is what I use for Wi-Fi inbound, i.e. campground Wi-Fi or house sources. Pepwave's supposedly are not ideal for both receiving Wi-Fi and sending Wi-Fi so I separate them in this way. I also have my starlink ethernet coming up from the basement along that black pvc pipe in the half bath electrical cabinet that connects Starlink directly to the WAN on Pepwave 2. I have an ethernet that goes up along the roof and drops into the driver's overhead cabinet so I can connect Pepwave 2 into WAN of Pepwave 1.

I do use a managed switch in the driver's overhead compartment so Pepwave 2 comes into the managed switch in a 2 port VLAN that outputs to Pepwave 1's WAN port. Pepwave 1 connects to this managed switch on the other ports and outputs to stereo, Apple TV, etc. So those paths are separated via the TP-LINK 8 port managed switch.

A bit complex, but it's not. It's actually a far simpler and more reliable setup that I evolved over the years.

The main reason for two pepwaves is to be able to use two cellular sources at once, i.e. AT&T up front along with Verizon from Pepwave 2. I often use Pepwave's FusionHub (free) to aggregate the sources for a reliable Internet connection, bonding, etc. Works amazing. So I can use AT&T up front and Starlink for example to aggregate the two, whichever are stronger.

A lot of flexibility, obviously I have critical needs for Internet for work, etc. It's more cost effective to buy 2 x Pepwave's for the two cellular radios (4 sim's) vs higher end Pepwave units.
 
cool POWER setup there!!!!
 

Latest posts

Latest resources

Back
Top Bottom