Good morning fellaz, I am trying to set up a vyatta box using the latest version - 6.2. I have followed the instructions given here http://www.vyatta.com/video/getting-started-with-vyatta/getting-started-with... but still cannot get my box to ping other hosts in its subnet, not am I able to ping the vyatta PC. In case you got confused, I have a Windows PC (from which I wrote this message) as 192.168.4.63. I have assigned to eth0 192.168.4.64 and the two computers are not "seeing each other" via ping. I have also enabled ssh and https services as in the video and of course https://vbox-ip doesn't help. So I'm just wondering, does this thing need a cheat-code or something in order to work or what?? Your help will be greatly appreciated. Me.
<top posting> Hi Simon, I have never used vyatta but the concept of routing is the same across the board. If you cannot ping machines on the same subnet then your layer 2 infrastructure is broken or you have typos in your prefix or subnets. Please check carefully. However i have to admit from your description i dont understand your topology or what you are trying to achieve to be of any further assistance. Regards, Mich. On 6/28/11 10:02 AM, Simon Mbuthia wrote:
Good morning fellaz,
I am trying to set up a vyatta box using the latest version - 6.2. I have followed the instructions given here http://www.vyatta.com/video/getting-started-with-vyatta/getting-started-with... but still cannot get my box to ping other hosts in its subnet, not am I able to ping the vyatta PC. In case you got confused, I have a Windows PC (from which I wrote this message) as 192.168.4.63. I have assigned to eth0 192.168.4.64 and the two computers are not "seeing each other" via ping. I have also enabled ssh and https services as in the video and of course https://vbox-ip doesn't help.
So I'm just wondering, does this thing need a cheat-code or something in order to work or what?? Your help will be greatly appreciated.
Me. _______________________________________________ Skunkworks mailing list Skunkworks@lists.my.co.ke http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------ Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
Hi Mich, Thanks for your response. Let me shed some more light. Don't worry about what the vyatta box's purpose for now. All we are interested in is getting it to be accessible across the LAN. I have used two LAN cables which are working fine. The NICs have also been detected successfully (it has two, which I am using interchangeably together with the two ethernet cables. the arp table on vyatta shows my computer's MAC address, which means that it's just "playing hard to get" buy not replying to my ping requests otherwise how would it get my PC's MAC address if it's a layer 2 problem? I have checked and rechecked and Googled but still the cow is refusing. The prefix on both my Windows PC and the vyatta box is /24. It's got to be something that's either missing in the documentation or some kind of bug... On 28/06/2011, Michuki Mwangi <michuki.mwangi@gmail.com> wrote:
<top posting> Hi Simon,
I have never used vyatta but the concept of routing is the same across the board.
If you cannot ping machines on the same subnet then your layer 2 infrastructure is broken or you have typos in your prefix or subnets.
Please check carefully.
However i have to admit from your description i dont understand your topology or what you are trying to achieve to be of any further assistance.
Regards,
Mich.
On 6/28/11 10:02 AM, Simon Mbuthia wrote:
Good morning fellaz,
I am trying to set up a vyatta box using the latest version - 6.2. I have followed the instructions given here http://www.vyatta.com/video/getting-started-with-vyatta/getting-started-with... but still cannot get my box to ping other hosts in its subnet, not am I able to ping the vyatta PC. In case you got confused, I have a Windows PC (from which I wrote this message) as 192.168.4.63. I have assigned to eth0 192.168.4.64 and the two computers are not "seeing each other" via ping. I have also enabled ssh and https services as in the video and of course https://vbox-ip doesn't help.
So I'm just wondering, does this thing need a cheat-code or something in order to work or what?? Your help will be greatly appreciated.
Me. _______________________________________________ Skunkworks mailing list Skunkworks@lists.my.co.ke http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------ Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
Hi Simon, How is your vyatta box setup is it on a VM instance or fully installed on a dedicated box?. If its in a VM instance did you check that it generated its own MAC address. Also if in a VM instance can you check that the host has defined the guest OS to run the Network Interface in bridge mode and not a NAT mode. Regards, Michuki. On 6/28/11 10:34 AM, Simon Mbuthia wrote:
Hi Mich,
Thanks for your response. Let me shed some more light. Don't worry about what the vyatta box's purpose for now. All we are interested in is getting it to be accessible across the LAN. I have used two LAN cables which are working fine. The NICs have also been detected successfully (it has two, which I am using interchangeably together with the two ethernet cables. the arp table on vyatta shows my computer's MAC address, which means that it's just "playing hard to get" buy not replying to my ping requests otherwise how would it get my PC's MAC address if it's a layer 2 problem? I have checked and rechecked and Googled but still the cow is refusing. The prefix on both my Windows PC and the vyatta box is /24.
It's got to be something that's either missing in the documentation or some kind of bug...
On 28/06/2011, Michuki Mwangi <michuki.mwangi@gmail.com> wrote:
<top posting> Hi Simon,
I have never used vyatta but the concept of routing is the same across the board.
If you cannot ping machines on the same subnet then your layer 2 infrastructure is broken or you have typos in your prefix or subnets.
Please check carefully.
However i have to admit from your description i dont understand your topology or what you are trying to achieve to be of any further assistance.
Regards,
Mich.
On 6/28/11 10:02 AM, Simon Mbuthia wrote:
Good morning fellaz,
I am trying to set up a vyatta box using the latest version - 6.2. I have followed the instructions given here http://www.vyatta.com/video/getting-started-with-vyatta/getting-started-with... but still cannot get my box to ping other hosts in its subnet, not am I able to ping the vyatta PC. In case you got confused, I have a Windows PC (from which I wrote this message) as 192.168.4.63. I have assigned to eth0 192.168.4.64 and the two computers are not "seeing each other" via ping. I have also enabled ssh and https services as in the video and of course https://vbox-ip doesn't help.
So I'm just wondering, does this thing need a cheat-code or something in order to work or what?? Your help will be greatly appreciated.
Me. _______________________________________________ Skunkworks mailing list Skunkworks@lists.my.co.ke http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------ Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ Skunkworks mailing list Skunkworks@lists.my.co.ke http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------ Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
Hi Mich, It's on a standalone PC. On 28/06/2011, Michuki Mwangi <michuki.mwangi@gmail.com> wrote:
Hi Simon,
How is your vyatta box setup is it on a VM instance or fully installed on a dedicated box?.
If its in a VM instance did you check that it generated its own MAC address.
Also if in a VM instance can you check that the host has defined the guest OS to run the Network Interface in bridge mode and not a NAT mode.
Regards,
Michuki.
On 6/28/11 10:34 AM, Simon Mbuthia wrote:
Hi Mich,
Thanks for your response. Let me shed some more light. Don't worry about what the vyatta box's purpose for now. All we are interested in is getting it to be accessible across the LAN. I have used two LAN cables which are working fine. The NICs have also been detected successfully (it has two, which I am using interchangeably together with the two ethernet cables. the arp table on vyatta shows my computer's MAC address, which means that it's just "playing hard to get" buy not replying to my ping requests otherwise how would it get my PC's MAC address if it's a layer 2 problem? I have checked and rechecked and Googled but still the cow is refusing. The prefix on both my Windows PC and the vyatta box is /24.
It's got to be something that's either missing in the documentation or some kind of bug...
On 28/06/2011, Michuki Mwangi <michuki.mwangi@gmail.com> wrote:
<top posting> Hi Simon,
I have never used vyatta but the concept of routing is the same across the board.
If you cannot ping machines on the same subnet then your layer 2 infrastructure is broken or you have typos in your prefix or subnets.
Please check carefully.
However i have to admit from your description i dont understand your topology or what you are trying to achieve to be of any further assistance.
Regards,
Mich.
On 6/28/11 10:02 AM, Simon Mbuthia wrote:
Good morning fellaz,
I am trying to set up a vyatta box using the latest version - 6.2. I have followed the instructions given here http://www.vyatta.com/video/getting-started-with-vyatta/getting-started-with... but still cannot get my box to ping other hosts in its subnet, not am I able to ping the vyatta PC. In case you got confused, I have a Windows PC (from which I wrote this message) as 192.168.4.63. I have assigned to eth0 192.168.4.64 and the two computers are not "seeing each other" via ping. I have also enabled ssh and https services as in the video and of course https://vbox-ip doesn't help.
So I'm just wondering, does this thing need a cheat-code or something in order to work or what?? Your help will be greatly appreciated.
Me. _______________________________________________ Skunkworks mailing list Skunkworks@lists.my.co.ke http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------ Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ Skunkworks mailing list Skunkworks@lists.my.co.ke http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------ Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
On 6/28/11 11:21 AM, Simon Mbuthia wrote:
Hi Mich,
It's on a standalone PC.
Then tcpdump is your friend ... Regards, Michuki. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
echo-reply enabled? On 28 June 2011 12:22, Michuki Mwangi <michuki@swiftkenya.com> wrote:
On 6/28/11 11:21 AM, Simon Mbuthia wrote:
Hi Mich,
It's on a standalone PC.
Then tcpdump is your friend ...
Regards,
Michuki.
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
_______________________________________________ Skunkworks mailing list Skunkworks@lists.my.co.ke http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------ Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
participants (4)
-
Michuki Mwangi -
Michuki Mwangi -
Simon Mbuthia -
Thuo Wilson