Homebrew [Tutorial] Setting up Pegaswitch and Preparing for Homebrew

  • Thread starter Thread starter iAqua
  • Start date Start date
  • Views Views 151,893
  • Replies Replies 368
  • Likes Likes 44
I type the switchdns ip
(primary dns 10.0.2.XX)

I save and don't work :(

--------------------- MERGED ---------------------------

(normaly the switch language is french but for the screenshots I put it in english)
2017111812284100-0C7E8798D2996597BAFD59B427BF6132.jpg


2017111812290700-0C7E8798D2996597BAFD59B427BF6132.jpg


2017111812291000-1AB131B6E6571375B79964211BB3F5AE.jpg
 

Attachments

  • 2017111812284100-0C7E8798D2996597BAFD59B427BF6132.jpg
    2017111812284100-0C7E8798D2996597BAFD59B427BF6132.jpg
    65.8 KB · Views: 252
I type the switchdns ip
(primary dns 10.0.2.XX)

I save and don't work :(

--------------------- MERGED ---------------------------

(normaly the switch language is french but for the screenshots I put it in english)
View attachment 106302

View attachment 106303

View attachment 106304

You are using VirtualBox, I presume. While the VM is closed, click so that your Ubuntu VM is highlighted, click Settings, click Network, use a new network tab to choose Attached to: Bridged Adapter, expand Advanced, and for Adapter Type choose PCnet FAST III

And uncheck Enable Network Adapter for any other network adapters, you just want this one enabled. You can re-enable them later. This ensures Pegaswitch will choose the right one.
 
  • Like
Reactions: Xyphoseos
You are using VirtualBox, I presume. While the VM is closed, click so that your Ubuntu VM is highlighted, click Settings, click Network, use a new network tab to choose Attached to: Bridged Adapter, expand Advanced, and for Adapter Type choose PCnet FAST III

And uncheck Enable Network Adapter for any other network adapters, you just want this one enabled. You can re-enable them later. This ensures Pegaswitch will choose the right one.
I type the new dns in primary dns but it says that incorrect
 
Last edited by machinoman,
Is your host machine connected to the internet? I guess so lol. Duh. ummmm

OK, try changing Bridged Adapter to Host Only Adapter, hit the blue circle next to MAC Address to change the address, and try that.
 
Last edited by machinoman,
Ok chang
Ubuntu isn't connected now :( ?
View attachment 106306
Ok, Bridged Adapter was better it seems. That is um... truly strange... I'm trying to think of what could be wrong. You should typically see an internal IP beginning with 192.168.xxx.xxx or 10.xxx.xxx.xxx occassionally, but never 127.0.0.1, it means the VM is not connected to your network.

Yes you could try replacing PCnet III with Intel Pro/1000 MT Desktop, but that one is less reliable for me sometimes. Worth a try though.
 
Last edited by machinoman,
  • Like
Reactions: Xyphoseos
Ok chang

Ok, Bridged Adapter was better it seems. That is um... truly strange... I'm trying to think of what could be wrong. You should typically see an internal IP beginning with 192.168.xxx.xxx or 10.xxx.xxx.xxx occassionally, but never 127.0.0.1, it means the VM is not connected to your network.

Yes you could try replacing PCnet III with Intel Pro/1000 MT Desktop, but that one is less reliable for me sometimes. Worth a try though.
It's possible but why and how to resolve it ?

--------------------- MERGED ---------------------------

before use the bridged adaptater, I was connected
 
It's possible but why and how to resolve it ?

--------------------- MERGED ---------------------------

before use the bridged adaptater, I was connected

I have another idea if you are down. Leave the Host-Only Adapter enabled, but in tab 3 enable an NAT adapter, like the one you originally had. If a new NAT is recognized perhaps PegaSwitch won't recognize it as the default this time, but even if it does there is a simple parameter to make PegaSwitch choose a specific IP, but let me know if that works.
 
Last edited by machinoman,
  • Like
Reactions: Xyphoseos
I have another idea if you are down. Leave the Host-Only Adapter enabled, but in tab 3 enable an NAT adapter, like the one you originally had. If a new NAT is recognized perhaps PegaSwitch won't recognize it as the default this time, but even if it does there is a simple parameter to make PegaSwitch choose a specific IP, but let me know if that works.
I get another dns ip but nothing change :(
 
I get another dns ip but nothing change :(
Thats ok, as long as its not 127.0.0.1. Now open a terminal and type in

ifconfig

and try opening pegaswitch with either of the two IPs similar to the ones in bold below.

enp0s8 Link encap:Ethernet HWaddr 08:00:27:5c:a6:68
inet addr:192.168.56.102 Bcast:192.168.56.255 Mask:255.255.255.0
inet6 addr: fe80::6d26:7861:8539:fca1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:53 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1559 (1.5 KB) TX bytes:6524 (6.5 KB)
Interrupt:16 Base address:0xd240

enp0s9 Link encap:Ethernet HWaddr 08:00:27:12:13:51
inet addr:10.0.4.15 Bcast:10.0.4.255 Mask:255.255.255.0
inet6 addr: fe80::a1a4:2635:425a:4c0f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:74 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2735 (2.7 KB) TX bytes:8227 (8.2 KB)
Interrupt:17 Base address:0xd260

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:70 errors:0 dropped:0 overruns:0 frame:0
TX packets:70 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6292 (6.2 KB) TX bytes:6292 (6.2 KB)


it will most likely be be like the top one, so for example i would run

pegaswitch --ip 192.168.56.102
 
Last edited by machinoman,
xyphoseos@xyphoseos-VirtualBox:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 08:00:27:e5:e3:d8
inet addr:10.0.4.15 Bcast:10.0.4.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fee5:e3d8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:122 errors:0 dropped:0 overruns:0 frame:0
TX packets:231 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13151 (13.1 KB) TX bytes:30965 (30.9 KB)

eth1 Link encap:Ethernet HWaddr 08:00:27:37:62:1b
inet addr:192.168.56.101 Bcast:192.168.56.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe37:621b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:164 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2858 (2.8 KB) TX bytes:31190 (31.1 KB)
Interrupt:11 Base address:0xd240

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:209 errors:0 dropped:0 overruns:0 frame:0
TX packets:209 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:15043 (15.0 KB) TX bytes:15043 (15.0 KB)

--------------------- MERGED ---------------------------

Capture.PNG
Capture1.PNG
 

Site & Scene News

Popular threads in this forum